• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 51
  • 32
  • 28
  • 13
  • 3
  • 1
  • 1
  • 1
  • 1
  • 1
  • 1
  • Tagged with
  • 139
  • 139
  • 66
  • 54
  • 35
  • 34
  • 34
  • 32
  • 32
  • 32
  • 29
  • 29
  • 26
  • 20
  • 20
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.

Agile Practices in Commercial SaaS Teams : A case study on the adoption of agile practices in non-software teams

Petersen, Bruno January 2020 (has links)
Agile software development methods have seen great success in software teams. Research on the topic of adopting agile methods in development teams is extensive. In the literature key enabling factors are identified and numerous benefits of agile ways of working are named. Less attention has been payed to the non-software functions in software development organizations, though. Moreover, little is known about how well the enabling factors and benefits for software teams translate to other teams in the organization. The goal of this study is to evaluate what benefits agile methods provide to non-software teams, whether the enabling factors are similar and what the challenges and drawbacks for adopting agile methods in commercial teams are. Using the case of the Swedish Software-as-a-Service company Funnel, which introduced agile practices into their commercial teams, these questions are tackled. The study finds that knowledge transfer and governance are core areas that need to be engaged in during the adoption process. With decisions being made more autonomously ensuring the exchange of relevant information is crucial. The autonomy creates new demands for the governance structure, making a guiding vision and clear strategic direction crucial for individuals to remain capable of acting. An additional focus is laid on the interplay of organizational values and agile methods. The study concludes that the introduction of agile methods to commercial teams is beneficial for the organization and helps teams solve more complex problems. It further argues that the distinction drawn between agile practices and agile enablers is misleading because of the reciprocal dependence. Finally, it is argued, that the distinction of benefits and drawbacks arising from agile methods favors agile adoption as an end in itself. The actual benefit of adopting agile practices may lie with how it makes an organization practice change, engage proactively with organizational challenges and, as a consequence, develop a greater exaptive potential.

Nástroj pro podporu agilního vývoje softwaru / Agile Development Software Support Tool

Veverka, Pavel January 2014 (has links)
Purpose of this thesis is to design system to support agile software development in virtual teams. Agile development methodology and some available tools to support it are listed here in this thesis, in order to use the system in a wide range of devices, theoretical analysis of multi-platform application development options are listed. The following sections describe the design and implementation witch using web technologies. At the end the system is demonstrated on model situation and extension its designed.

Využití metod projektového řízení pro vytvoření mobilní aplikace / The use of Methods of the Project Management in the Creation of Mobile Applications

Runets, Ivan January 2016 (has links)
Diplomová práce se zabývá problémy řízení projektů pro vytvoření mobilní aplikace a jejich řešením pomocí agilních metod řízení projektů. V práci je analyzován současný stav projektu a jednotlivé přístupy. Práce se zaměřuje na výběr metody a navrhuje její aplikování na projekt.

Výběr a implementace nástroje pro podporu řízení / Výběr a implementace nástroje pro podporu řízení

Moudrá, Libuše January 2018 (has links)
The content of this diploma thesis is an analysis of the current state of management of international projects in a multinational IT company, which should lead to the selection and implementation of an appropriate project management tool supporting planning and project management using agile methods Scrum and Kanban. The focus of this thesis is the actual implementation of the selected tool and its setting.

Lean Startup as a Tool for Digital Business Model Innovation : Enablers and Barriers for Established Companies

Beisheim, Maja, Langner, Charline January 2021 (has links)
Background: The rapidly changing world of digital technologies forces many companies to undertake a digital shift by transforming existing business models into digital business models to achieve sustainable value creation and value capture. Especially, for established companies, that have been successful leaders before the dot-com bubble (1995-2000) and whose business models have been threatened by the emergence of digital technologies, there is a need for a digital shift. We refer to this digitization of business models as digital business model innovation. However, often adoption and implementation of digital technologies require tremendous changes and thus, can be challenging for established companies. Therefore, agile methods and business experimentation have become important strategic elements and are used to generate and test novel business models in a fast manner. We introduce lean startup as an agile method for digital business model innovation, which has proven to be successful in digital entrepreneurship. Thus, it requires further empirical investigation on how to use lean startup in established companies for successful digital business model innovation. Purpose: The purpose of our study is to identify enablers and barriers of lean startup as a tool for digital BMI in established companies. Thus, we propose a framework showing how established companies can be successful in digital business model innovation by using lean startup. Method: We conducted exploratory, qualitative research based on grounded theory following an abductive approach. Using a non-probability, purposive sampling strategy, we gathered our empirical data through ten semi-structured interviews with experts in lean startup and digital business model innovation, working in or with established companies, shifting their business model towards a digital business model. By using grounded analysis, we gained an in-depth understanding of how lean startup is used in practice as well as occurring barriers and enablers for established companies. Conclusion: We emphasize that successful use of lean startup for digital business model innovation is based on an effective (1) lean startup management, appropriate (2) organizational structures, fitting (3) culture, and dedicated (4) corporate governance, which all require and are based on solid (5) methodical competence of the entire organization. Furthermore, (6) external influences such as market conditions, role of competition, or governance rules indirectly affect using lean startup as a tool for digital business model innovation.

Management method for Change Management in ERP systems

Ewerstein, Anders, Jansson, Markus January 2014 (has links)
Målet med detta arbete är att förbättra Spotifys processer när de gör förändringar internt som påverkar deras finansiella system. Arbetet har genomförts genom att kartlägga de team hos Spotify som skapar, påverkar och använder data i det finansiella systemet. Vidare har de olika teamens arbetssätt jämförts och skillnader i hur de arbetar identifierats. Baserat på de identifierade skillnaderna påvisas vilka utmaningar som finns när Spotify genomför förändringar där flera team är involverade. Kartläggningen visar att det finns både olika arbetssätt och grundinställning hos de olika teamen som skapar utmaningar i förändringsarbetet, speciellt i tvärfunktionella projekt. Slutsatser från resultatet presenteras i form av några olika förslag vilka kan hjälpa till att förbättra förändringsarbetet vid tvärfunktionella projekt hos Spotify. Skapa en koordinatorroll som fungerar som en gemensam kontakt för alla ärenden som genererar förändringar i det finansiella systemet. Genom den nya rollen tydliggör man informationsflödet. Skapa ett nytt team som ansvarar för alla förändringar som påverkar det finansiella systemet. Ett nytt team minskar beroenden mellan de olika teamen. Använda sig av tvärfunktionella projektledare som får dedikerade resurser att driva projekt där flera team är inblandade. Projektledaren kan då äga och ta ansvar för hela processen. Förändra så att alla inblandade team mäts på värdeskapandet för hela kedjan istället för att bedömas när de levererat sin del. Anordna en kortare workshop (1-5 dagar) med deltagare från de team som behöver interagera med varandra vid en förändring. Det blir ett effektivt sätt att minimera ledtiden mellan teamen. Skapa serviceavtal mellan de olika teamen, så att varje team effektivare kan planera sina resurser och veta vilka förutsättningar som gäller. / The objective of this thesis is to help Spotify to improve their internal change management process in their financial system. The work was done by charting the internal teams that create, influence and use data in the company’s financial system. Furthermore, the working methods of the different teams were compared and differences in how they work were identified. Our findings show that there are both different working processes and attitudes between the teams. This creates challenges in the change management process, especially in cross-functional projects. Conclusions from the results are presented as suggestions. These may help to improve the change management process in cross-functional projects at Spotify: Implement a coordinator role, which works as a single point of contact for everything that is related to changes in the financial system. The new role helps to improve the distribution of information. Create a new team that is responsible for all changes that affect the financial system. A new team reduces dependencies betweenthe different teams. Introduce cross-functional project managers who receive dedicated resources to implement projects where multiple teams are involved. The project manager can then take full responsibility for the entire process. Make sure the effectiveness/productivity of all involved teams is measured by the value created for the whole value chain rather than when their respective part has been delivered. Have a workshop (1-5 days) in which participants from the teams that needs to integrate components work together. This will be an effective way to minimize the waiting time between the teams. Create a service level agreement between the different teams, so that each team can efficiently plan their resources and know what to expect from other teams.

A systematic framework of recovering process patterns from project enactment data as inputs to software process improvement

Huo, Ming, Computer Science & Engineering, Faculty of Engineering, UNSW January 2009 (has links)
The study of the software development process is a relatively new research area but it is growing rapidly. This development process, also called 'the software life cycle' or 'the software process', is the methodology used throughout the industry for the planning, design, implementation, testing and maintenance that takes place during the creation of a software product. Over the years a variety of different process models have been developed. From the numerous process models now available, project managers need validation of the choice he/she has made for a software development model that he/she believes will provide the best results. Yet the quality software so sought after by software project managers can be enhanced by improving the development process through which it is delivered. Well tested, reliable evidence is needed to assist these project managers in choosing and planning a superior software process as well as for improving the adopted software process. While some guidelines for software process validation and improvement have been provided, such as CMMI, quantitative evidence is, in fact, scarce. The quantitative evidence sometimes may not be able to be obtained from high level processes that refer to a planned process model, such as a waterfall model. Furthermore, there has been little analysis of low level processes. These low level processes refer to the actions of how a development team follow a high level software process model to develop a software product. We describe these low level processes as project enactment. Normally there is a gap between the high level software process and the project enactment. In order to improve this software development process, this gap needs to be identified, measured and analyzed. In this dissertation, we propose an approach that examines the deviation between a planned process model and the project enactment of that plan. We measure the discrepancy from two aspects: consistency and inconsistency. The analytical results of the proposed approach, which include both qualitative and quantitative data, provide powerful and precise evidence for tailoring, planning and selecting any software process model. The entire approach is composed of four major phases: 1) re-presentation of the planned process model, 2) pre-processing the low level process data, 3) process mining, and 4) analysis and comparison of the recovered process model and planned process model. We evaluate the proposed approach in three case studies: a small, a medium, and a large-sized project obtained from an industrial software development organization. The appropriate data on low level processes is collected and our approach is then applied to these projects individually. From each case study we then performed a detailed analysis of the inconsistencies that had surfaced as well as the consistencies between the plan and the enactment models. An analysis of the inconsistencies revealed that several 'agile' practices were introduced during the project's development even though the planned process model was initially based on 'ISO-12207' instead of the 'agile' method. In addition, our analysis identifies the patterns in the process that are frequently repeated. The outcome of the case studies shows that our approach is applicable to a range of software projects. The conclusions derived from these case studies confirmed that our approach could be used to enhance the entire software development process, including tailoring and assessment.

The Agile method Scrum in development of safety critical applications : A case study about challenges and opportunities for developers and verifiers / Den Agila metoden Scrum vid utveckling av säkerhetskritiska applikationer : En fallstudie om utmaningar och möjligheter för utvecklare och verifierare

Hiltunen, Kim January 2018 (has links)
When it comes to using agile methods in safety critical application development, there is a limited amount of empirical findings. To learn more about how people in this field perceives the use of working with these methods, it is of interest to take part of their experiences and opinions. The purpose of this thesis is to discover advantages, disadvantages and improvement factors of working with the agile method Scrum in combination with safety critical application development. The study was limited to the roles of developers and verifiers working in two anonymized companies in the defence and railway industry. A qualitative approach was used which included a multiple case study where each of the involved company were considered a case. Empirical data was collected through semi structured interviews with the employees from the two companies. The collected data was categorized, coded and analyzed using comparative analysis. The data was coded based on one of the seven areas documentation, organization, communication, education, development, verification and planning. The interviewed developers and verifiers pointed out various advantages, disadvantages and improvement factors within the areas mentioned above. The majority of the opinions among the interviewees varied. However, some common aspects were pointed out. The most frequently mentioned factor to improve for the developers was in the communication area, while the verifiers raised educational aspects as the most common factor to improve. The findings from this study can be used to point out sections that the investigated companies should consider when using the agile method Scrum in combination with safety critical application development. The thesis also provides empirical evidence of how people in the in-spected companies consider difficulties and opportunities in their work. / När det kommer till användadet av agila metoder vid säkerhetskritisk applikationsutveckling finns det begränsat med empiriska fynd. För att få veta mer om hur personer som arbetar inom detta område uppfattar användandet av dessa metoder, är det av intresse att ta del av deras erfarenheter och åsikter. Syftet med denna uppsats är att identifiera fördelar, nackdelar och förbättringsmöjligheter när det kommer till att arbeta agilt med Scrum vid säkerhetskritisk applikationsutveckling. Studien inkluderade rollerna utvecklare och verifierare som arbetade i två anonymiserade företag inom försvarsrespektive järnvägsindustrin. En kvalitativ metod användes vilket inkluderade en fallstudie, där de involverade företagen behandlades som varsitt fall. Empirisk data samlades in genom semistrukturerade intervjuer med anställda från de två företagen. All insamlad data kategoriserades, kodades och analyserade med hjälp av komparativ analys. Kodningen utfördes baserat på de sju olika områdena dokumentation, organisation, kommunikation, utbildning, utveckling, verifikation och planering. De intervjuade utvecklarna och verifierarena pekade ut diverse fördelar, nackdelar och förbättringsfaktorer inom områdena som nämndes ovan. Majoriteten av åsikterna varierade, däremot kunde några gemensamma åsikter påvisas. Den mest förekommande förbättringsfaktorn bland utvecklarna var inom kommunikationsområdet, medan verifierarna tog upp utbildningsrelaterade aspekter som den vanligaste förbättringsfaktorn. Resultaten från denna studie kan användas för att peka ut delar som de undersökta företagen bör beakta vid användning av den agila metoden Scrum i kombination med säkerhetskritisk applikationsutveckling. Uppsatsen tillhandahåller empiriska bevis på hur personer som arbetar på de granskade företagen ser på svårigheter och möjligheterinom sitt arbete.

Aplikace moderních prvků v klasickém projektovém řízení / Application of modern elements in classical project management

Országh, Martin January 2013 (has links)
This thesis deals with project management and with different ways in which can be cur-rently approached. Beside the conventional, classical approach based on processes, modern approaches based on the theory of constraints and agile principles are discussed. Based on analysis, the main objective of the thesis is firstly to find weaknesses in the classical project management and strong key elements of modern approaches and after that to make suggestions to enhance the classical approach with the selected strong elements of modern approaches.

Communication through boundary objects in distributed agile teams : An integration of user-centered design and agile development

Persson, Johan January 2014 (has links)
The use of agile methods continues to increase within software development but the agile processes do not contain the necessary steps to account for the user and realize the usability of the system. It seems it is therefore necessary to integrate the UCD methodology and agile methodology. What this integration should look like is not always apparent as the integration needs to be adapted to the specific context in each organization. Accompanied by a pre-study which identified difficulties with the integration, the current study examines how UCD specialists experience the communication through boundary objects in distributed agile teams. Furthermore the study examines how the understanding of the user is communicated to the developers in the agile teams and the potential of doing so with a design rationale. A case study was therefore performed with interviews of six UCD specialists to try to answers these questions. A content analysis was performed in relation to each research question and identified a number of themes relating to the experiences concerning; (1) communication through boundary objects, (2) how an understanding of the user is communicated, and (3) opinions of using design rationale for this purpose. Some of the conclusions drawn are that boundary objects only aim at communicating the interaction with the system, that they should be viewed as communication aids as they are not stand-alone and making them comprehensive would be even more time consuming. Furthermore, personas are not deemed fitting for communicating the understanding of the user to developers. This should instead be done by allowing developers to participate in user research.

Page generated in 0.0792 seconds