To see the other types of publications on this topic, follow the link: Agile system development methodology.
Dissertations / Theses on the topic 'Agile system development methodology'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Agile system development methodology.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Tabrez, Shams, and Islam Jan. "Documentation and Agile Methodology." Thesis, Uppsala universitet, Institutionen för informatik och media, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-212653.
Full textAbstract:
Computer science in general and software engineering in specific is changing very fast. Software engineers are constantly using more innovative and more efficient ways to develop new software than in the past. This continuous evolution of software development methodologies has a great impact on both the software developed and the environment that the developers work-in. Agile software development methodologies are used to overcome many issues in the software development processes. One of the issues which still exists and needs to be addressed is the preparation of proper documentation along with the software. The work presented in this dissertation focuses on software documentation. The work starts by a thorough literature review which focuses on different aspects of software documentation and different agile methodologies. The thesis focuses on finding out the challenges that the developers faces during their development process. Two major questions addressed in the thesis. First one is to find the motivation to document in agile envirionment, whih is based on the hypothesis that there do exist a motivation. The second question is that how should documentation be produced such that we could avoid maximum possible potential problems. These questions are addressed with the help of different perspectives of the stockholders (i.e. developers and users) and the existing methods for documentation. A questionnaire was developed based on the nine categories of documentation, like user documents and system documents etc.. It included different questions related to the types of documents created in software development processes, the software development stage at which the documents are created and the importance of the documents. Questions from this questionnaire are then posted on agile specific discussion forums. Where many experienced and fresh practitioners participated in the discussion. We had a detailed discussion on every component of documentation and problems were identified by the practitioners. The questionnaire was also sent to different companies practicing agile methodology. we received about 14 responses as it was detailed questionnaire with about 34 questions. The responses of the discussion forum and survey are then analyzed and conclusions were drawn. The conclusions include that all the participants consider software documentation very important to the success of a software development project. the question of motivation is answered from the literature and opinions we received from experienced practitioners. While seven factor are identified that affect your documentation, to help solve the question of how should documentation be done.
2
Grey, Johannes. "The development of a hybrid agile project management methodology / Grey, J." Thesis, North-West University, 2011. http://hdl.handle.net/10394/7004.
Full textAbstract:
The aim of this study is to investigate whether a combination of agile system development methodologies (ASDMs) and project management methodologies (PMMs) can be used to develop a hybrid APMM that will have the ability to deliver information technology (IT) projects successfully in a constantly changing business and project environment.
To achieve this objective, a literature review was conducted on the relatively well–established ASDMs by firstly defining a SDM and an ASDM. Each ASDM and its effectiveness are described, after which ASDMs in general are evaluated by considering their area of application, advantages and disadvantages. A comparison is then done of the seven different ASDMs using the four elements of an SDM (Huisman & Iivari, 2006:32) to emphasise some of the main similarities and differences amongst the different ASDMs. The seven ASDMs investigated in this study are Dynamic System Development Methodology, Scrum, Extreme Programming, Feature Driven
Development, Crystal ASDMs ? Crystal Clear and Crystal Orange in particular, Adaptive Software
Development and Lean Development.
A literature review was also conducted on two structured and relatively well–established PMMs,
PMBOK and PRINCE2, and a relatively new PMM called Agile Project Management. Each PMM is
evaluated by considering their area of application, advantages, disadvantages and integration with
other methodologies, after which a comparison is made of the different PMMs.
The research was conducted by following a mixed methods research plan, which included the
mixed methods research paradigm (combination of the interpretive research paradigm and the
positivistic research paradigm), research methods (design science, case study and survey),
quantitative and qualitative data–collection techniques (interviews and questionnaires), and dataanalysis
techniques (cross–case and statistical).
The reasons that projects fail and critical project success factors were studied and summarised to
form the critical project success criteria, which were used to create the agile project success criteria. The ASDM best practice and PMM best practice frameworks were created by identifying
whether a certain ASDM or PMM would satisfy a specific agile project success factor (APSF) of the
agile project success criteria. The findings of each APSF in the respective frameworks were used
as a foundation to develop a hybrid APMM (ver. 0) that would address the agile project success
criteria. The hybrid APMM (ver. 0) was developed interpretively using design science (research
approach) and constructivism by combining the strengths, addressing the weaknesses and bridging
the gaps identified in the frameworks.
The hybrid APMM (ver. 0) was then evaluated and improved by conducting an interpretive case
study, which entailed interviewing participants from large and small organisations. Once the
qualitative data collected had been analysed using cross–case analysis, the findings were
incorporated in order to create an improved hybrid APMM (ver. 1).
The hybrid APMM (ver. 1) too was evaluated and improved by conducting a survey, which entailed
administering questionnaires to various respondents in order to collect quantitative and qualitative
data. The findings of the statistical analysis of the data were also used to improve the hybrid APMM
(ver. 1), resulting in the final hybrid APMM (ver. 2).
This study demonstrates that a combination of ASDMs and PMMs can be used to develop a hybrid
APMM with the ability to deliver IT projects in a constantly changing project and business
environment.Thesis (Ph.D. (Computer Science))--North-West University, Potchefstroom Campus, 2012.
3
Schtein, Igor A. "Management Strategies for Adopting Agile Methods of Software Development in Distributed Teams." ScholarWorks, 2018. https://scholarworks.waldenu.edu/dissertations/5417.
Full textAbstract:
Between 2003 and 2015, more than 61% of U.S. software development teams failed to satisfy project requirements, budgets, or timelines. Failed projects cost the software industry an estimated 60 billion dollars. Lost opportunities and misused resources are often the result of software development leaders failing to implement appropriate methods for managing software projects. The purpose of this qualitative multiple case study was to explore strategies software development managers use in adopting Agile methodology in the context of distributed teams. The tenets of Agile approach are individual interaction over tools, working software over documentation, and collaboration over a contract. The conceptual framework for the study was adapting Agile development methodologies. The targeted population was software development managers of U.S.-based companies located in Northern California who had successfully adopted Agile methods for distributed teams. Data were collected through face-to-face interviews with 5 managers and a review of project-tracking documentation and tools. Data analysis included inductive coding of transcribed interviews and evaluation of secondary data to identify themes through methodological triangulation. Findings indicated that coaching and training of teams, incremental implementation of Agile processes, and proactive management of communication effectiveness are effective strategies for adopting Agile methodology in the context of distributed teams. Improving the efficacy of Agile adoption may translate to increased financial stability for software engineers across the world as well as accelerate the successful development of information systems, thereby enriching human lives.
4
Ispir, Mustafa. "Test Driven Development Of Embedded Systems." Master's thesis, METU, 2004. http://etd.lib.metu.edu.tr/upload/12605630/index.pdf.
Full textAbstract:
In this thesis, the Test Driven Development method (TDD) is studied for use in developing embedded software. The required framework is written for the development environment Rhapsody.
Integration of TDD into a classical development cycle, without necessitating a transition to agile methodologies of software development and required unit test framework to apply TDD to an object oriented embedded software development project with a specific development environment and specific project conditions are done in this thesis. A software tool for unit testing is developed specifically for this purpose, both to support the proposed approach and to illustrate its application.
The results show that RhapUnit supplies the required testing functionality for developing embedded software in Rhapsody with TDD. Also, development of RhapUnit is a successful example of the application of TDD.
5
Knublauch, Holger [Verfasser]. "An agile development methodology for knowledge-based systems including a Java framework for knowledge modeling and appropriate tool support / Holger Knublauch." Ulm : Universität Ulm. Fakultät für Informatik, 2002. http://d-nb.info/1015324703/34.
Full text
6
Rangevik, Alexander. "Software Development across Time Zones : A Study of Globally Distributed Software Development in Small Enterprises." Thesis, Uppsala universitet, Informationssystem, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-203325.
Full textAbstract:
Globally distributed software development has become an important topic for small and medium enterprises. However, the distinct requirements of small and medium enterprises (SMEs) are still not fullyunderstood. To contribute to this growing discussion, I will present an ethnographical field study of a Swedish software company engaged in a distributed development practice with its American branch. By applying a theoretical view based on communication, coordination and control over time, space and socio/cultural difference, I show to what extent a distributed software development model affects SMEs. Whereproblems related to formal and informal communication, knowledge sharing, articulation work and programming methodologies are discussed. My findings suggest that organizational adjustments are needed for SMEs in order to take advantage of distributed software development (DSD), that specialized tools supporting coordination and articulation work is not so common in practice and that certain adjustment to agile methodologies could be made in order to better support DSD.
7
Krajíček, Michal. "Systém pro podporu komunikace agilního řízení projektů." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2013. http://www.nusl.cz/ntk/nusl-412884.
Full textAbstract:
The thesis deals with problems of agile methodologies in the settings of virtual teams. It begins with the description of virtual teams and their models and deals with both theoretical and practical aspects of mutual communication of their team members. The thesis follows with general characteristics of agile approach and their demonstration on representative methodologies. One of them (methodology Scrum) is described in detail in the next chapter and linked with possibilities of its deployment within virtual teams. Practical part of the thesis deals with the design and implementation of a software application that is focused on effective communication support of virtual teams that utilize Scrum. Deployment of this application is discussed within a case study of a real project which team faced problems of agile software development in the settings of virtual team on a daily basis.
8
Hollar, Ashby Brooks. "Cowboy : an agile programming methodology for a solo programmer /." VCU Scholars Compass, 2006. http://hdl.handle.net/10156/1400.
Full text
9
Šilinskaitė, Viktorija. "Agile požiūrio taikymas internetinių svetainių kūrime." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2008. http://vddb.library.lt/obj/LT-eLABa-0001:E.02~2008~D_20080128_140321-87884.
Full textAbstract:
Greitas internetinių svetainių skaičiaus padidėjimas per paskutinius keletą metų rodo informacijos, pasiekiamos internetu, svarbą. Daug įmonių kuria internetines svetaines, bet jie susiduria su problemomis, susijusiomis su reikalavimų pasikeitimais kūrimo eigoje. Šiame darbe nagrinėjama Agile požiūrio pritaikymo galimybės internetinėms svetainėms kurti. Darbe atlikta jau esamų metodų analizė, kuri parodė, kad internetinių svetainių kūrimui nėra visiškai tinkamo metodo, todėl darbo uždavinys - sukurti metodą, paremtą Scrum ir FDD savybėmis internetinių svetainių kūrimui.A fast increase in the number of web sites the last years, shows the importance of information existing in web sites giving the possibility for users to have access to it. Many companies create websites, but they face problems related with requirements changing until the developing process completes. In this work you will find analysis of software development methods. Agile approach allows changing requirements even in last phase of the developing process. Creating a web site does not follow one single path and there is no ideal method creating a web site. In this dissertation will be analyzed a method for web sites development based on Agile approach.
10
King, Gary R. "Using the agile development methodology and applying best practice project management processes." Thesis, Monterey, California: Naval Postgraduate School, 2014. http://hdl.handle.net/10945/44596.
Full textAbstract:
Approved for public release; distribution is unlimitedThere are many SOFtware development life-cycle models. Each one has its own advantages and disadvantages, forcing program management to select carefully before embarking on a full-scale development effort. A popular choice today is the Agile development model, due to its more informal processes and ability to adapt easily to changes. However, one of these positive elements is also one of its negative aspects. These less formal processes can lead developers to use the Agile model as authorization to avoid any process efforts, leading to a difficult project management problem. This thesis explores the manner by which the Agile development model may be executed in a disciplined manner. The thesis also describes the application of various techniques to create a robust development environment while still maintaining the value the methodology brings. In addition, it also highlights the importance of selecting each practice carefully and applying that practice uniquely to each project to ensure maximum performance.
11
Shahriyari, Salman. "Distributed Agile Development; Suitability, Challenges and Practices." Thesis, Högskolan i Borås, Institutionen Handels- och IT-högskolan, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:hb:diva-17340.
Full textAbstract:
Uncertainty in software development and business environment and the need to increase thespeed of development have driven organizations to search for methods that are responsive toboth change and speed. Providing iterative development, agile development involvescustomers and users through different phases of development, and delivers frequent releasesof software to customer while receives the corresponding feedback. Using this approach, agiledevelopment thus aims at addressing mentioned issues of speed and uncertainty whiledeveloping only what customer needs from the beginning of the project. On the other hand,distributed software development is used in many organizations to reach global talent andglobal market. The problems associated with distributed software development such as lack ofenough communication and team coherency, have forced project managers to combine it withagile to mitigate these social problems. This study focuses on distributed agile development,its suitability for a typical project and its challenges and deficiencies. Text analysis andinterviews using qualitative methods are used in this scientific research work. From thetheoretical view point, different text covering agile methodology, distributed development andcombination of them were considered. This study covered two parts: first, an evaluation ofagile and distributed development opportunities and problems to help determine whether ornot distributed development is suitable for a project and second, considering the challengesonce starting to use this method and practices required to regard them. For the empirical part,the focus was put on Volvo IT employees by having seven interviews with members who arecurrently active in distributed agile development. These interviews were used to compare andverify the finding of the theoretical part. The results of the study were categorized into twosections. In the first part, important elements required to verify the suitability of using thismethod are provided. The recommended factors for this evaluation are cost, productivity,customer, team structure, etc. In the second part, the challenges of using distributed agiledevelopment were categorized into four parts: (a) challenges of selected agile method, whichthe focus in this study is Scrum, (b) challenges with time-zone differences, (c) communicationchallenges and (d) finally team building challenges. The required practices to address thesechallenges were also provided.Program: Masterutbildning i Informatik
12
Cao, Lan. "Modeling Dynamics in Agile Software Development." Digital Archive @ GSU, 2005. http://digitalarchive.gsu.edu/cis_diss/4.
Full textAbstract:
Agile software development challenges the traditional way of software development and project management. In rapidly changing environments, changing requirements and tight schedule constraints require software developers to take a different approach toward the process of software development. However, beyond a few case studies, surveys and studies focused on specific practices such as pair programming, the effectiveness and applicability of agile methods have not been established adequately. The objective of my research is to improve the understanding of and gain insights into these issues. For this purpose, I develop a system dynamic simulation model that considers the complex interdependencies among the variety of practices used in agile development. The model is developed on the basis of an extensive review of the literature as well as quantitative and qualitative data collected from real projects in seven organizations. The development of the model was guided by dynamic hypotheses on customer involvement, refactoring and quality of design. The model was refined and validated using data from independent projects. The model helps in answering important questions on the impact of customer behavior, cost of making changes and economics of pair programming. Experimentation with the model suggests that the cost of change is not constant; instead, its value changes cyclically and increases towards the later phase of development. Also, the results of simulation show that with no pair programming, fewer tasks are delivered and it costs more to deliver a task when compared to development with pair programming. Further, customer behavior has a major impact on project performance. The quality of customer feedback is found to be very critical to the successful of an agile software development project. The primary contribution of this research is the simulation model of agile software development that can be used a tool to examine the impact of agile practices and management policies on critical project variables including project scope, schedule, and cost. This research provides a mechanism to study agile development as a dynamic system of practices rather than using a static view and in isolation. The results from this study are expected to be of significant interest to practitioners of agile methods by providing them a simulation environment to examine the impact of their practices, procedures and management policies.
13
Murray, Collin (Collin J. ). "Lean and agile software development : a case study." Thesis, Massachusetts Institute of Technology, 2008. http://hdl.handle.net/1721.1/43176.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 2008."February 2008."
Includes bibliographical references (p. 89-90).
This paper looks at agile and lean development transitions for organizations that formerly used the waterfall style of development. There has been lots written about the positive aspects of agile software development and the anticipated benefits are widely touted. Through my research I became aware of significant obstacles that organizations can encounter when adopting an agile development method. The obstacles seem to be more applicable to organizations that use the waterfall development method and are compounded when legacy products exist. The intent of this thesis is to identify positive and challenging aspects for organizations that undertake a transition from waterfall development to agile development.
by Collin Murray.
S.M.
14
Redfearn, Brady Edwin. "User Experience Engineering Adoption and Practice: A Longitudinal Case Study." BYU ScholarsArchive, 2013. https://scholarsarchive.byu.edu/etd/3762.
Full textAbstract:
User Experience Engineering (UxE) incorporates subject areas like usability, HCI, interaction experience, interaction design, "human factors", ergonomics", cognitive psychology", behavioral psychology and psychometrics", systems engineering", [and] "computer science," (Hartson, 1998). It has been suggested that UxE will be the main success factor in organizations as we enter the "loyalty decade" of software development, where the repeat usage of a product by a single customer will be the metric of product success (Alghamdi, 2010; Law & van Schaik, 2010, p. 313; Nielsen, 2008; Van Schaik & Ling, 2011). What is relatively unknown in the current academic literature is whether existing UxE methodologies are effective or not when placed in a longitudinal research context (Law & van Schaik, 2010). There is room for the exploration of the effects of long-term UxE practices in a real-world case study scenario. The problem, addressed in this study, is that a lack of the application of UxE-related processes and practices with an industrial partner had resulted in customer dissatisfaction and a loss of market share. A three-year case study was performed during which 10 UxE-related metrics were gathered and analyzed to measure the improvements in the design of the customer's experience that long-term UxE practices could bring to a small corporate enterprise. The changes that occurred from the corporate and customer's point of view were analyzed as the customer's experience evolved throughout this long-term UxE study. Finally, an analysis of the problems and issues that arose in the implementation of UxE principles during the application of long-term UxE processes was performed. First-hand training between the research team and company employees proved essential to the success of this project. Although a long-term UxE process was difficult to implement within the existing development practices of the industrial partner, a dramatic increase in customer satisfaction and customer engagement with the company system was found. UxE processes led to increased sales rates and decreased development costs in the long-term. All 10 metrics gathered throughout this study showed measurable improvements after long-term UxE processes and practices were adopted by the industrial partner.
15
Chen, Xi. "Component-based control system development for agile manufacturing machine systems." Thesis, De Montfort University, 2003. http://hdl.handle.net/2086/13263.
Full textAbstract:
It is now a common sense that manufactures including machine suppliers and system integrators of the 21 st century will need to compete on global marketplaces, which are frequently shifting and fragmenting, with new technologies continuously emerging. Future production machines and manufacturing systems need to offer the "agility" required in providing responsiveness to product changes and the ability to reconfigure. The primary aim for this research is to advance studies in machine control system design, in the context of the European project VIR-ENG - "Integrated Design, Simulation and Distributed Control of Agile Modular Machinery".
16
Andersson, Tim, Gustav Arnesson, Pontus Brengdahl, Anna Ekelund, Claes Kallström, Kalle Olsson, Julia Thudén, and Erik Wallvik. "Experiences from the Development of a Webshop Using Scrum Methodology." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-107109.
Full textAbstract:
This is a report concerning the software development project Eldflugan, a system developed by eight students at Linköping University. It addresses experience from developing a web-based e-commerce using Scrum, an agile development method, which was used throughout the project. The teams work, how Scrum was applied with both advantages and disadvantages is being lifted. Different development environments have been used due to separate issues and opportunities, which is described. The database management systems, MySQL, and the local version, SQLite, are discussed as well as AJAX and PJAX, tools for giving the users a better and faster experience. To prepare Eldflugan for entering the e-commerce market, a marketing plan including environmental scanning, a SWOT analysis and a STP, has been made. Ethical aspects such as legal, use and handling of personal information and how it is communicated are also being addressed. Finally the report discusses product weaknesses, future opportunities, implementation difficulties and how those could have been prevented. It was found that Scrum is best used when it is utilized fully and a risk analysis can prevent unexpected problems to surface.
17
Mok, Goh Kaih. "A System Development Methodology for Embedded Applications." Thesis, Cranfield University, 2009. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.515144.
Full text
18
Al-Azawi, Rula K. "Agent Oriented Software Engineering (AOSE) approach to game development methodology." Thesis, De Montfort University, 2015. http://hdl.handle.net/2086/11120.
Full textAbstract:
This thesis investigates existing game development methodologies, through the process of researching game and system development models. The results indicate that these methodologies are engineered to solve specific problems, and most are suitable only for specific game genres. Different approaches to building games have been proposed in recent years. However, most of these methodologies focus on the design and implementation phase. This research aims to enhance game development methodologies by proposing a novel game development methodology, with the ability to function in generic game genres, thereby guiding game developers and designers from the start of the game development phase to the end of the implementation and testing phase. On a positive note, aligning development practice with universal standards makes it far easier to incorporate extra team members at short notice. This increased the confidence when working in the same environment as super developers. In the gaming industry, most game development proceeds directly from game design to the implementation phase, and the researcher observes that this is the only industry in which this occurs. It is a consequence of the game industry’s failure to integrate with modern development techniques. The ultimate aim of this research to apply a new game development methodology using most game elements to enhance success. This development model will align with different game genres, and resolve the gap between industry and research area, so that game developers can focus on the important business of creating games. The primary aim of Agent Oriented Agile Base (AOAB) game development methodology is to present game development techniques in sequential steps to facilitate game creation and close the gap in the existing game development methodologies. Agent technology is used in complex domains such as e-commerce, health, manufacturing, games, etc. In this thesis we are interested in the game domain, which comprises a unique set of characteristics such as automata, collaboration etc. Our AOAB will be based on a predictive approach after adaptation of MaSE methodology, and an adaptive approach using Agile methodology. To ensure proof of concept, AOAB game development methodology will be evaluated against industry principles, providing an industry case study to create a driving test game, which was the problem motivating this research. Furthermore, we conducted two workshops to introduce our methodology to both academic and industry participants. Finally, we prepared an academic experiment to use AOAB in the academic sector. We have analyzed the feedbacks and comments and concluded the strengths and weakness of the AOAB methodology. The research achievements are summarized and proposals for future work outlined.
19
Wahl, Emil. "Reflecting and adjusting in large-scale Agile software development : A case study." Thesis, Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-19676.
Full textAbstract:
Background. Agile software development has seen increased use in large-scale projects in recent times. Many larger corporations transition from using a traditional plan-driven approach for developing software to applying the Agile methodology within its processes. Large-scale Agile projects are inherently difficult to implement as there are many challenges associated with it. Many Agile frameworks have been developed to make it easier to apply the Agile methodology on a large-scale. The Agile principle of reflecting and adjusting at regular intervals can be used for developing these frameworks and allows practitioners to find ways to mitigate the challenges that large-scale Agile projects face. Objectives. This thesis aims to explore how a large-scale Agile project applies the Agile principle of reflecting and adjusting its work process, both at the overall and team level. The objectives of the thesis are to find out how the case organization regularly reflects on its work process and how it enables adjustments through the distribution of roles that can enforce changes. An additional objective is to find out what the perceived challenges are that are associated with performing regular reflections and adjustments in a large-scale Agile context. Methods. A field study is conducted at a large-scale Agile project. The field study includes direct observations of day-to-day work and scheduled meetings, interviewing project participants, and reading company documentation. The collected data is thematically analyzed to identify how the case organization reflects and adjust its work process and what the perceived challenges are. Results. Three different events are identified at the case organization to apply the Agile principle of reflecting and adjusting: reference groups to reflect on larger matters affecting much of the project, retrospective meetings to some extent to reflect within the different teams, and day-to-day reflections. All the identified roles can influence change for most parts of the process, but can only enforce change on their part of the process. Six themes are identified as perceived challenges associated with the Agile principle of reflecting and adjusting: Deadlines and time limits, multiple tasks within the teams, disinterest or misunderstanding the Agile principles, different levels of Agile, and established process and complacency. Conclusions. The case organization applies several different reflective events that address some of the challenges that are associated with large-scale Agile projects. The case organization has many other challenges relating to these events and they are all associated with other challenges previously discovered in related works.Bakgrund. Agil mjukvaruutveckling har sett en ökad användning i storskaliga projekt under den senaste tiden. Många större företag övergår från att använda en traditionell plandriven strategi för att utveckla programvara till att tillämpa den Agila metodiken i sina processer. Det finns många utmaningar när man använder den Agila metodiken i ett storskaligt projekt. Agila projekt på stor skala är svårt att genomföra, och många Agila ramverk har utvecklats för att göra det lättare att tillämpa den Agila metodiken på stor skala. Den Agila principen att reflektera och justera med jämna mellanrum kan användas för att utveckla dessa ramverk och gör det möjligt för utövare att hitta sätt att tackla de utmaningar som storskaliga Agila projekt står inför. Syfte. Denna avhandling undersöker hur ett storskaligt Agilt projekt tillämpar den Agila principen att reflektera och justera sin arbetsprocess, både på en övergripande nivå och teamnivå. Målet med avhandlingen är att ta reda på hur organisationen regelbundet reflekterar över sin arbetsprocess och hur den möjliggör justeringar genom fördelning av roller som kan verkställa förändringarna. Ett ytterligare mål är att ta reda på vilka upplevda utmaningar som är förknippade med att utföra regelbundna reflektioner och justeringar i ett storskaligt Agilt sammanhang. Metod. En fältstudie genomförs på ett storskaligt Agilt projekt. Fältstudien inkluderar direkta observationer av det dagliga arbetet och schemalagda möten, intervjuer med projektdeltagare, och läsa företagetsdokumentation. Den insamlade datan analyseras tematiskt för att identifiera hur organisationen reflekterar och justerar sin arbetsprocess och de upplevda utmaningarna som relaterar till det. Resultat. Organisationen använder sig av tre olika sätt för att tillämpa den Agila principen för reflektion och justering: referensgrupper för att reflektera över större frågor som påverkar stora delar av projektet, retrospektiva möten i viss mån för att reflektera i de olika teamen, och dagliga reflektioner. Alla identifierade roller kan influera förändring på processen, men kan bara verkställa förändringar på sin del av processen. Sex teman identifieras som upplevda utmaningar förknippade med den Agila principen att reflektera och justera: Tidsfrister och tidsgränser, flera uppgifter inom teamen, ointresse eller missförståelse av de Agila principerna, olika nivåer av Agile, och etablerad process och självgodhet. Slutsatser. Organisationen tillämpar flera olika funktioner för reflektion som hanterar några av de utmaningar som är förknippade med storskaliga Agila projekt. Organisationen har många andra utmaningar relaterade till dessa funktioner och de är alla förknippade med andra utmaningar som tidigare upptäckts i relaterade arbeten.
20
Wufka, Michael. "Domain understanding in agile information system development : the role of conceptual modeling." Thesis, University of British Columbia, 2013. http://hdl.handle.net/2429/45542.
Full textAbstract:
Agile development methods such as Extreme Programming or Scrum typically do not prescribe specific conceptual modeling practices. In fact, the agile paradigm generally discourages extensive use of documentation and models that are not directly related to or used to generate code. However, anecdotal empirical evidence suggests that conceptual modeling might be beneficial in agile software development, and that a wide range of conceptual modeling methods might be used by agile practitioners.
This work studies the relationship between conceptual modeling and agile development in three parts. Firstly, based on the existing literature, it examines theoretically which role conceptual modeling might play in agile development. In order to do this, it defines an operationalizable conceptualization of agility that is independent of specific development methods. In a second step, the role that conceptual modeling practices play in current information system (IS) development is studied in a survey of practitioners. This survey also serves to validate a measurement instrument based on the conceptualization of agility. Finally, the impact of conceptual modeling on agile development is studied in detail in an exploratory lab experiment.
The survey finds that developers who are more agile tend to use a wider range of conceptual modeling practices than less agile developers, and that they face fewer difficulties with domain understanding. The proposed measurement instrument of agility correlates well with self-reported agility, which provides some evidence for its validity and reliability. The results of the experiment indicate that the use of conceptual modeling does not reduce agility, but that it might in fact increase it. It finds that subjects use conceptual models to improve their understanding of the domain in a number of different ways.
These different uses, an interesting result by themselves, are a potential starting point for future research, which could focus on a subset of them. Additional important results of this work include a validated measurement instrument of agility that is based on a development method independent conceptualization of agility, and an improved understanding of the use of conceptual modeling in current agile development practice.
21
Magnusson, Evelina, and Moa Westlund. "Measuring Performance in Large Scale Agile Software Development Projects." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-300388.
Full textAbstract:
The increased usage and need for software as part of products has challenged traditional project management, nevertheless for hardware heavy organisations that are used to rely on the linear prediction and tracking of project outcomes. The developments in projects with embedded systems have countless dependencies and almost impossible to predict. Literature shows that software development projects have problems meeting the initial goals of budget, time, and scope. This is discovered too late due to insufficient methods of tracking progress. The purpose of this thesis was to investigate how large agile software development projects can continuously be followed to evaluate their performance and meet initial customer agreements fixed in time, budget, and scope. The thesis was conducted at Saab, active in the defense and security industry. This qualitative exploratory study was conducted with semistructured interviews and focus group discussions at the case company Saab, benchmark interviews with two additional companies, and an extensive literature study. The issues with the existing tracking approach were explored to determine how progress tracking may be created to continuously measure progress and indicate if project goals will be accomplished or not. The more general challenges in software development were also investigated to provide knowledge about areas in need of additional metrics which could indicate the problem and mitigate it. One industry-specific challenge is the security aspect that is unavoidable and requires a lot of documentation that holds up the development activities. Other detected challenges were difficulties in understanding requirements that lead to faulty estimations and work in the wrong direction, undiscovered dependencies that lead to a lot of rework and waiting for additional parts, insufficient testing environments that lead to late feedback, and holds up the development. It was also visible that the projects were conducted with different management approaches and no best-proven practice existed for tracking performance. From an analysis of the empirical data and existing literature, a suggestion of method tracking design was developed for large agile software projects with fixed contracts. The models were proposed to allow flexibility, enable control, and provide a holistic view. As Saab intends to introduce Earned Value Management in their software projects, this method was complemented with COMOD, TRL, IRL, and SRL to provide these three characteristics. Transparency and visibility of both products and processes are also found to be key to project success, thus additional metrics to increase visibility in projects are suggested to enable efficient project leading.Den ökade användningen och behovet av mjukvara har utmanat traditionell projektledning, speciellt för hårdvaruorganisationer som är vana att kunna förlita sig på den linjära utvecklingen av ett projek. Utvecklingen av projekt som inkluderar inbyggda system med otaliga beroenden är nästan omöjliga att förutsäga. Litteratur visar att mjukvaruutvecklingsprojekt har problem att nå de ursprungliga målen för budget, tid och omfattning. Detta upptäcks för sent på grund av otillräckliga metoder för att mäta framsteg i projekt. Detta examensarbete genomfördes som en fallstudie på Saab, aktiv inom försvar- och säkerhetssektorn. Syftet med denna avhandling har varit att utvärdera hur projektledning för stora agila mjukvaruutvecklingsprojekt kontinuerligt kan följa utvecklingen för att möta de ursprungliga kundavtalen som är fastställda i tid, budget och omfattning. Denna kvalitativa undersökningsstudie genomfördes med semistrukturerade intervjuer och fokusgrupp intervjuer på företaget Saab, benchmarking intervjuer med ytterligare två företag och en omfattande litteraturstudie. För att utvärdera hur en metod för utvärdering av projektstatus ska utformas för att i tid ange om projektmålen inte kommer att uppnås, undersöktes utmaningarna med mjukvaruutveckling och därifrån har möjliga mätvärden och metoder för att mildra eller upptäcka dessa problem utvärderats. Några av de upptäckta problemen verkar överlappa flera industrier medan andra verkar vara mer specifika för just militär- och försvarsindustrin. En branschspecifik utmaning är säkerhetsaspekten som är oundviklig och kräver mycket dokumentation som stannar upp utvecklingsaktiviteterna. Andra upptäckta utmaningar var svårigheter att förstå krav som leder till felaktiga uppskattningar och arbete i fel riktning, oupptäckta beroenden som leder till mycket omarbetning och väntande på ytterligare delar, otillräckliga testmiljöer som leder till sen feedback och håller upp utvecklingen. Stora skillnader i de metoder som idag tillämpas från projektledning i dessa projekt var synligt under projektet, vilket indikerar på att det idag inte finns någon accepteras bästa metod i uppföjlning. Från analys av samlad empirisk data samt befintlig litteratur utvecklades ett förslag på hur en metod för uppföljning av stora agila mjukvaruprojekt skulle kunna se ut. Design på föreslagen modell skulle möjliggöra flexibilitet och kontroll samt förmedla ett helhetsperpektiv. Eftersom Saab avser att introducera Earned Value Management i sina mjukvaruprojekt kompletterades denna metod med COMOD, TRL, IRL och SRL för att få dessa tre egenskaper. Öppenhet och synlighet för både produkt och process visar sig också vara nyckeln till framgång i projektutveckling, vilket är möjligt med ytterligare mått för att öka synligheten i projektet.
22
Martin, Michael J. (Michael John) 1962. "Methodology for architecture development for product design." Thesis, Massachusetts Institute of Technology, 2000. http://hdl.handle.net/1721.1/29888.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, System Design & Management Program, 2000.Includes bibliographical references (p. 101-104).
An integrative methodology for architecture development in a product development environment is described. The methodology combines the use of the design structure matrix technique with constraint-based modeling to create a process that satisfies the following requirements: 1. Provide a means for modeling the system that provides the capability to gain feedback on proposed decisions. This promotes rapidly system learning. 2. Provide a definition of the linkage between product requirements and design parameters. 3. Provide documentation that makes the architecture explicit and enables others to have access to the architectural knowledge. 4. Increase confidence in the proposed system so that product design can proceed with a minimum of risk. The application of the methodology in the context of the development of the xerographic module architecture for color printing system is described. The project was a clean sheet design using a new color architecture and implementing seven new technologies. A significant result is that once the architecture was accepted and placed under change control, the architecture has not changed in four years. Traditionally, similar projects have had to make significant changes as the design matured. Based on the case study, there is anecdotal evidence to support the hypothesis that the methodology can be successfully used to develop complex systems. It is shown that the methodology is closely aligned to the product development process. During the pre-concept and concept phases, the models were used to develop the system architecture. During the detailed design phase, the models can be used to maintain the integrity of the architecture as the design and technologies mature. Finally, in order for the methodology to be successfully applied it must have the full support of program management and the design and technology organizations.
by Michael J. Martin.
S.M.
23
Leech, David J. "The Naturalized Knowledge System, a methodology for community development." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 2000. http://www.collectionscanada.ca/obj/s4/f2/dsk2/ftp03/MQ57128.pdf.
Full text
24
Wang, Yang [Verfasser], and Stefan [Akademischer Betreuer] Wagner. "System-theoretic safety analysis in agile software development / Yang Wang ; Betreuer: Stefan Wagner." Stuttgart : Universitätsbibliothek der Universität Stuttgart, 2018. http://d-nb.info/1172288437/34.
Full text
25
Johansson, Felix, and Samir Uppugunduri. "Measuring in an Agile System Development Process : A Case Study in Health IT." Thesis, Luleå tekniska universitet, Institutionen för ekonomi, teknik och samhälle, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:ltu:diva-63841.
Full textAbstract:
The basic aim for any software development organization is to maximize value creation for any given investment. To amplify and speed up value creation efforts, Agile Software Development has gained much popularity during the last decade as a response to a volatile and disruptive market. In an Agile environment, the team focuses on lightweight working practices, constant deliveries and customer collaboration rather than heavy documentation and inflexible processes. However, the Agile way of working has complicated how an organization can control and evaluate the process; allowing organizations to believe that all Agile processes is the ideal process. This master thesis was conducted as a case study at Sectra ImIT, an Agile Health IT company working with Imaging and IT solutions that is currently in an early phase of introducing metrics in the System Development process. The purpose of this thesis was to investigate and suggest how the organization could use metrics to control and evaluate value creation in the System Development process. It also aimed to provide strategic recommendations to such an organization how they could continue their work with implementing and using metrics. The descriptive and exploratory purpose of this study was realized through unstructured and semistructured interviews with people involved in the process as well as observations. One of the major findings in this thesis is related to a missing feedback loop from defects occurring at customer site to the internal System Development process. Therefore, this study developed and implemented a concept to generate this feedback. The concept builds on defect information that can be used both to generate feedback and statistics for evaluation. The second major finding in this study is related to the identification of barriers to why the organization is not using metrics in teams to control and evaluate the process. Based on these findings, the authors presented several recommendations that should be considered to create a culture where teams are using metrics to learn more about the process. The first recommendation is that the organization should set guidelines among teams of what should, and is desired to be evaluated with focus on information need. Secondly, metrics need to be higher prioritized through directives from management granting team’s resources to manage metrics, which at the same time provides incentives that the organization believe metrics could improve their work. Thirdly, based on the company context, teams should identify metrics based on an information need derived from their prioritizations, changes, decisions and what is currently left unanswered. Finally, metrics should primarily be used to provide means for discussion and provide feedback with focus on trends rather than absolute numbers.Det huvudsakliga målet för ett godtyckligt företag inom mjukvaruutveckling är att maximera det värde som skapas i varje enskild investering. För att förstärka och snabba upp värdeskapande har Agil mjukvaruutveckling växt i popularitet som en respons mot volatila och osäkra marknader. I en Agil miljö fokuserar grupper på ”lättviktade” arbetsmetoder, kontinuerliga leveranser och kundsamarbeten över det tidigare arbetssättet som bestod av mycket dokumentation och inflexibla processer. Samtidigt har det Agila arbetssättet gjort det svårt för organisationer att kontrollera och utvärdera processen, vilket har resulterat i att organisationer antar att deras Agila process är ideal och välfungerande med avsaknad av belägg för det. Detta examensarbete genomfördes som en fallstudie på Sectra ImIT, ett Agilt företag inom medicinsk teknik med fokus på bildhanteringssystem och IT lösningar. Företaget är i en tidig fas av att undersöka och introducera mätetal i systemutvecklingsprocessen, där syftet med examensarbetet var att utvärdera och föreslå hur organisationen kunde använda mätetal för att kontrollera och utvärdera värdeskapande i processen. Därtill ämnade studien även att ge strategiska förslag på hur företaget i framtiden kan arbeta med att implementera och använda sig av mätetal. Det deskriptiva och explorativa syftet realiserades genom ostrukturerade och semi-strukturerade intervjuer samt observationer med människor som dagligen arbetade inom processen. En iakttagelse var kopplad till avsaknaden av återkoppling mellan de defekter som uppkommer ute hos kund tillbaka till systemutvecklingsprocessen. Detta resulterade i ett koncept som utvecklades och implementerades av författarna med syfte att skapa återkoppling och möjlighet till statistisk utvärdering av processen som helhet. Den andra iakttagelsen berörde ett antal anledningar till varför organisationen inte använder mätetal i teams för att kontrollera och utvärdera processen. Baserat på en analys av dessa presenterar författarna flertalet rekommendationer som företaget borde ta hänsyn till för att skapa en kultur som främjar användandet av mätetal för att skapa ytterligare förståelse för processen. Den första rekommendationen är att organisationen bör diskutera riktlinjer gemensamt för teams gällande vad som anses önskvärt att utvärdera, med fokus på informationsbehov. Därtill bör organisationen uppmana teams till att allokera mer resurser på mätetal, vilket samtidigt ger incitament att det är något företaget tror kan hjälpa teams att bli bättre. Utifrån företagets kontext bör teams själva tillåtas att identifiera mätetal baserat på deras informationsbehov som ett resultat av exempelvis prioriteringar, förändringar, beslut och vad som för tillfället är obesvarat. Slutligen ska mätetal användas i huvudsak som en grund för diskussion och feedback med fokus på trender snarare än att uppnå specifika mål.
26
Wolter, Liam. "The Feeling and Perception of Using Analog and Digital Task Management Tools within Agile Development." Thesis, Malmö universitet, Fakulteten för teknik och samhälle (TS), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:mau:diva-20220.
Full textAbstract:
The field of software development has rapidly been changing due to changes in work requirements and expectations of stakeholders. As a result, there has been a widespread adoption of agile methodology within the software industry, as it allows for a constant stream of deliveries and project adjustments. Agile methodology allows project teams to pick and adjust appropriate agile practices as they see fit, meaning that situations differ in various ways. With respect to the young age of agile methodology and the various approaches has created gaps that could affect project efficiency and quality. Specifically, one of these unperfected areas is the task management tools, that has had a hard time being established in the digital space. This can be illustrated by the popular use analog tools such as post-it notes and whiteboards. Likewise, analog and digital task management tools have varying advantages and disadvantages that forces project teams to work in certain ways. For example, analog tools are easily adjusted and digital tool are instead more structured. Typically, this creates restrictions to the physical work space for employees and obstacles of project progression communication to external parties. Towards addressing the issue, a set of seven task board requirements are established as the foundation for the solution, which are based on the theoretical and practical findings. The solution is a digitalized whiteboard with syncing and cross platform abilities.
27
Yeung, Chung Kei. "Ontological model for information systems development methodology." HKBU Institutional Repository, 2006. http://repository.hkbu.edu.hk/etd_ra/702.
Full text
28
Garcia, Erik Roberto. "Resource dependencies in parallel development of military systems : a comparison of waterfall and agile development methodologies." Thesis, Massachusetts Institute of Technology, 2014. http://hdl.handle.net/1721.1/105297.
Full textAbstract:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, 2014.DVD-ROM contains supplemental models: four .mdl files and two .vdf files.
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 63-64).
The United States Department of Defense has been plagued with failing programs that are over budget, behind schedule, and exhibit poor performance during testing. Once a program has cost, schedule, or capability issues, follow-on development efforts adopt the underlying issues only to reinforce poor performance. To address these issues that lead to firefighting, one option is to use an Agile software development process to introduce capabilities earlier in the development process for effective testing. Two System Dynamics models compare Agile with the traditional Waterfall development approach to determine: if Agile development reduces the conflict between cost, schedule, and capability constraints; if Agile development reduces firefighting; and will Agile development impact other development tasks. Based on the simulation of each model, Agile did improve the dynamics of parallel development cycles by maximizing the productivity of the entire development team. Under the same System and Software Engineering team size and development release schedule, Agile development increases the quantity of requirements introduced within a development cycle. However, Agile development emphasized less on maturing new technologies leading to considerably less innovative builds. Thesis Supervisor:
by Erik Roberto Garcia.
S.M. in Engineering and Management
29
Hellström, Douglas. "Uncertainty management – How to handle project uncertainty : A case study at Rimaster Development." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-299782.
Full textAbstract:
We know that it is difficult to forecast the future, and the same applies to project management. There are a lot of occurrences that are both predictable and not possible throughout the course of a project. The management of uncertainty is a management method that helps to forecast and adjust to future occurrences. In this context, frameworks and tools have been created to help project managers genuinely understand a project's potential. The study was conducted as a case study at Rimaster Development in Söderhamn and aimed at discovering sources of uncertainty within their project development that affect project performance. The study is built on both quantitative and qualitative data gathering from a workshop, survey, meetings, and interviews from ten different projects of Rimaster. The study had five respondents who contributed with two projects, each of which they had been a part of previously, one classified as uncertain and one as more certain. The data were analyzed with the statistics tool SPSS, where variables were computed based on the empirical findings in the uncertainty survey. The result was then presented through uncertainty attribute matrices to identify how each project performed in relation to customer satisfaction as well as time plan and budget. Here, dependent variables were tested, such as if the uncertainty score (the higher value, the more uncertain is the project) influenced project performance. From the data, two categories of projects could be developed: Higher performing projects and lower performing projects. To this, significant analysis of the performance groups was performed to find parameters that were significantly different between the categories. To capture more data to the thesis, each project was then evaluated through an individual project analysis which consisted of analyzing the data from the survey more closely for each project. The findings from this were then supported with qualitative interviews. The findings in the study suggest that there is a relationship between project uncertainty and lower-performing projects in relationship to time plan and budget. Further, sixteen uncertainty parameters showed to have a significant value in the comparison between higher and lower performing projects. Based upon the data and the analysis of the study, managerial recommendations have been provided to Rimaster on tools and development processes that may assist the organization's uncertainty management and increase their project performance.Det är allmänt känt att det är omöjligt att tydligt förutsäga framtiden och detsamma gäller projektledning. Det finns många händelser som är både oförutsägbara och riskfyllda under ett projektets gång, där osäkerhetshanteringen är en hanteringsmetod som hjälper till att prognostisera och anpassa sig till framtida händelser. Tidigare forskning inom osäkerhetshantering har utvecklat ramar och verktyg för att hjälpa projektledare att verkligen förstå ett projekts potential. Studien genomfördes som en fallstudie vid Rimaster Development i Söderhamn och syftade till att upptäcka källor till osäkerhet inom deras utvecklingsavdelning som påverkar projektets prestanda. Studien bygger på både kvantitativ och kvalitativ datainsamling från en workshop, enkätundersökning, möten och intervjuer från tio olika projekt från Rimaster. Studien enkätundersökning hade fem svarande som bidrog med två projekt som de tidigare hade varit en del av, ett klassificerat som osäkert och ett som mer säkert. Data erhållen from enkäten analyserades med statistikverktyget SPSS där variabler beräknades baserat på empiriska resultat i osäkerhetsundersökningen. Resultatet presenterades sedan genom osäkerhetsattributmatriser för att identifiera hur varje projekt presterade i förhållande till kundnöjdhet samt tidsplan och budget. Här testades beroende variabler som om den osäkerhetspoängen varde projekt erhöll (ju högre värde, desto mer osäkert är projektet) hade en effekt på projektets prestanda. Från analysen kunde två kategorier av projekt utvecklas: projekt med högre prestanda och projekt med lägre prestanda. Utöver detta genomfördes en signifikansanalys av prestationsgrupperna för att hitta parametrar som var signifikanta olika mellan kategorierna. För att samla ytterliga data till avhandlingen utvärderades varje projekt genom en individuell projektanalys som bestod av att analysera data från undersökningen närmare för varje projekt. Resultaten från detta styrktes sedan med kvalitativa intervjuer. Resultaten i studien antyder att det finns ett samband mellan projektosäkerhet och projekt med lägre resultat i förhållande till tidsplan och budget. Vidare visade sig sexton osäkerhetsparametrar ha ett signifikant värde i jämförelsen mellan projekt med högre och lägre resultat. Baserat på analyseringen av den data studien samlat in så har rekommendationer överlämnats till Rimaster om verktyg och utvecklingsprocesser som kan hjälpa organisationens osäkerhetshantering och därmed öka deras projektprestanda.
30
Erharuyi, Edison. "Combining eXtreme Programming with ISO 9000:2000 to Improve Nigerian Software Development Processes." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5616.
Full textAbstract:
The aim of this research work is to study how eXtreme programming could be combined with ISO 9000:2000 standards to improve Nigerian software development processes. The combination of these models will enable organizations take advantage of models strengths and compensate for their weaknesses in enhancing continuous software process improvement and rapidly responding customer’s changing needs. This was achieved by adopting a model in balancing ISO and eXtreme programming in software projects. This allows organization to determine whether to choose a pure method (eXtreme programming or ISO) or mixed methods (eXtreme programming and ISO) that will be most successful in executing software projects. Also developed was another strategy in modifying eXtreme programming practices to reflect ISO 9001:2000 standard requirements.The aim of this research work is to study how eXtreme programming could be combined with ISO 9000:2000 standards to improve Nigerian software development processes
C/o Patrick O. Nordkapsgatan 8,Kista, 164 36, Stockholm Tel:+46-704214035, e- mail address: edisonerhas@yahoo.com
31
Nasehi, Arezo. "A Quantitative Study on Critical Success Factors in Agile Software Development Projects; Case Study IT Company." Thesis, Högskolan i Borås, Institutionen Handels- och IT-högskolan, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:hb:diva-17234.
Full textAbstract:
While software play integral role in every aspect of the modern world, software development process still faces many problems. During development process in an organization, effective methodology has a crucial role in order to become accomplished. Agile approach is new methodologies which have been introduced recently as a new approach for developing software to increase productivity and efficacy of software development process compare to traditional methodologies. Whereas, accomplishment of this methodology is still anecdotal and deeper investigation in this area is scant in academic circles. The purposes of this research is to influence success of agile software development in subject factor of organization, people, process, technical and project dimensions under terms of quality, scope, timeless and cost. This study has conducted a survey in order to investigate important success factors of agile software development process using quantitative approach. Preliminary After sufficient literature an explanation and list of potential factors for agile methodology based on previous studies were introduced. Afterward, factor and reliability analysis were conducted to mix this primal list into a finalized list of potential critical success factors in four mentioned dimensions. For each agile success factors term of quality, scope, time, and cost has been investigated. In order to collect required data a questionnaire was conducted among employees in a famous software development company who are mostly working based on agile methodology. This survey will make the personnel’s feedback and analysis their ideas about the variety of factors of agile methodologies which they are usually implemented in software development projects. Dependent sample tests, independent test related to the gender and multiple regression techniques as in full regression model and the last one is an optimized regression model which is done via the stepwise screening procedure. Final result of this study proved and rejected selected hypotheses. These hypotheses were about relationship between factor in four dimensions and quality, scope, time, and cost by using agile process. This questionnaire and analysis of this case study has proved some of authors’ hypothesis like the fact that by using agile methodology organization dimension is related directly to quality of product instead of reduction of total cost or using team management techniques can affect timeless factor instead of cost reduction. Finally, researcher makes more suggestions in order to make success factors more effective and increase productivity during the development process and to have more accomplishment in agile base projects.Program: Masterutbildning i Informatik
32
Scott, B. G. O. "A methodology for formal system development using process algebraic techniques." Thesis, University of Oxford, 1994. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.294356.
Full text
33
Wowczuk, Zenovy S. "Design validation methodology development for an aircraft sensor deployment system." Morgantown, W. Va. : [West Virginia University Libraries], 2008. http://hdl.handle.net/10450/5657.
Full textAbstract:
Thesis (Ph. D.)--West Virginia University, 2008.Title from document title page. Document formatted into pages; contains xv, 294 p. : ill. (some col.). Includes abstract. Includes bibliographical references.
34
Yunten, Tamer. "Supervisory methodology and notation (SUPERMAN) for human-computer system development." Diss., Virginia Polytechnic Institute and State University, 1985. http://hdl.handle.net/10919/49969.
Full textAbstract:
The underlying goal of SUPERvisory Methodology And Notation (SUPERMAN) is to enhance productive operation of human-computer system developers by providing easy-to-use concepts and automated tools for developing high-quality (e.g., human-engineered, cost-effective, easy-to-maintain) target systems. The supervisory concept of the methodology integrates functions of many modeling techniques, and allows complete representation of the designer's conceptualization of a system's operation. The methodology views humans as functional elements of a system in addition to computer elements. Parts of software which implement human-computer interaction are separated from the rest of software. A single, unified system representation is used throughout a system lifecycle. The concepts of the methodology are notationally built into a graphical programming language. The use of this language in developing a system leads to a natural and orderly application of the methodology.Ph. D.
incomplete_metadata
35
Wagener, Ruhan Pieter. "Investigating critical success factors in agile systems development projects / Ruhan Wagener." Thesis, North-West University, 2012. http://hdl.handle.net/10394/9251.
Full textAbstract:
This study investigates the critical success factors involved in agile systems development projects. Various systems development methodologies and project management methodologies are presented with their underlying principles, strengths and weaknesses. Thereafter the critical success factors adopted from the work of Chow and Cao (2007) are presented.
A positivistic research paradigm was chosen for data collection and analysis. The survey method was chosen for data collection. A questionnaire was sent to multiple respondents in a predominantly agile work environment, which resulted in a total of 129 respondents in various business sectors.
The results were analysed by implementing multiple correlation and regression statistics as well as descriptive statistics. The results show that there are in fact 16 critical success factors that have a direct impact on the success of agile systems development projects. Agile systems development methodologies have been increasing in use during the last 3 years, and most organisations are implementing some form of project management methodology. The first recommendation is based on the findings that strong customer involvement and the appropriate management of the agile process with a satisfactory amount of documentation resulted in greater process success. Therefore, organisations should encourage these critical success factors when implementing an ASDM as this has a positive effect on the project outcome.
The appropriate management of the agile process with a satisfactory amount of documentation, the application of good design practices and technical knowledge to a project, and a cooperative organizational culture instead of hierarchical are three of the key critical success factors that were positively related to the success of the product. By focussing on these critical success factors, the success of the entire project can be predicted.Thesis (MCom (Computer Science & Information Systems))--North-West University, Potchefstroom Campus, 2013.
36
Mthupha, Bokang. "A framework for the development and measurement of agile enterprise architecture." Thesis, Rhodes University, 2012. http://hdl.handle.net/10962/d1002777.
Full textAbstract:
Enterprise architecture is the high-level design of the entire business, facilitated by enterprise architects. "Agile enterprise architecture" is the term used in enterprise architecture to describe an architecture that caters for future unknowns, enabling change to occur rapidly without undue resource utilization, yet in a controlled manner and with minimal adverse impact. Some enterprise architects still use outdated, rigid approaches to enterprise architecture which are incompatible with today‟s business environment. In addition, there is limited research into methods that can be applied to measure the agility of enterprise architecture. The current environment is such that there is a need for a more agile approach to developing and measuring enterprise architecture. This work will lead to the creation of a Framework for The Development and Measurement of Agile Enterprise Architecture. In support of the main goal of the development of the framework, a literature review will be conducted focusing on the necessary sub-goals of the research. The first sub-goal of the literature review is to develop a comprehensive definition for enterprise architecture (referred to as EA), as well as discover how it is currently practiced. Thereafter, the literature review will investigate a comprehensive definition for agility and research why it is emerging as a critical topic. The next chapter of the literature review will research how agility fits within the context of EA, uncovering a comprehensive definition for agile EA and the best practices in agile EA development. The final chapter of the literature review will investigate suitable measurement techniques that can be used to assess the level of agility of EA. On completion of the literature review, a preliminary framework will be created using the most important contributions from the literature. An empirical study will be conducted to explore the definitions for EA, agility, agile EA, the methods to measure the agility of EA and the concepts for the development of agile EA summarised in the preliminary framework. Data analysis follows an interpretive and qualitative approach based on four case studies through interviews with systems experts in four South African organizations in one province. Each interviewee was interviewed once. The initial interview with a Principal Consultant on Enterprise Strategy Consulting at organisation # 1 formed the basis of an exploratory study; the results of which were used to refine the research instrument and preliminary framework. Thereafter, a more rigorous empirical study focused on interviews with the Chief Architect, Senior Manager in Advisory Services and an Enterprise Architect at organizations 2, 3 and 4 respectively was conducted. The research follows an inductive approach to capture the interpretive experiences of participants and develop theoretical propositions from them. Following the exploratory pilot study it became necessary to make changes to the preliminary framework and initial survey instrument created. Thereafter, the empirical study consisting of the remaining three cases was conducted to test the important aspects of the framework and literature definitions. The analysis of the results of the empirical study prompted further changes to the theoretical framework and definitions created. The interviews conducted with each of the organizations confirmed the factors for agile EA development as well as the effectiveness of the definitions created in the literature review. The research uncovered that the need for a more agile approach to developing EA and a way to measure the level of agility of EA has become more and more significant in organizations. This begins with a better understanding of EA, agility, how agility fits within the context of EA, as well as appropriate methods to measure agility.
37
Naseem, Junaid, and Wasim Tahir. "Study and analysis of the challenges and guidelines of transitioning from waterfall development model to Scrum." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2679.
Full textAbstract:
Software engineering practices have experienced significant changes over the period of past two decades. Keeping in view the competitive market trends, now is the high time for many organizations to shift from traditional waterfall models to more agile technologies like Scrum [22][23]. A change of this magnitude is often not easy to undertake. The reason that both software engineering techniques are different in many respects, organizations require considerable amount of analysis of the whole transitioning process and possible scenarios that may occur along the way. Small and medium organizations are normally very skeptical to the change of this magnitude. The scale of change is not limited to only software processes, in fact, difficult part is to deal with old attitudes and thinking processes and mold them for the new agile based Scrum development. The process of change therefore need to be understood in the first place and then carefully forwarded to the implementation phase.
38
Azizi, Nima, and Mohammed Aysar Taqi. "Applying Agile methodologies within the context of traditional project governance : - A study of the Volvo Group experience." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH. Forskningsmiljö Informationsteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-27632.
Full textAbstract:
The nature of software development has changed in last decade. Waterfall or traditional command and control methods have been replaced by Agile methodologies. Agile came as a “solution” to the disadvantages of the waterfall methodology, but using Agile has its own challenges. Due to the attractive characteristics of Agile such as flexibility and short time-to-market, Agile development has been increasingly popular and the number of organisations which have started to move to Agile is growing every day. Implementing new methodologies in any organisation is always a big challenge, especially for large-scale organisations due to their complexity, many different interacting interfaces, strong organisational culture, etc. The nature of these challenges and obstacles changes from different perspectives within an organisation, and each of these perspectives needs to be studied and investigated to ensure a successful transition from traditional approaches to Agile. In this thesis we focus on the project manager and project governance perspectives. We aim to define the success and failure factors that play a key role in moving from traditional approaches to Agile approaches in large-scale organisations. To address these challenges we conducted literature reviews on the latest research in implementing Agile methodologies. To collect our data we used a combination of qualitative and quantitative research methods. We explored both IT project manager and Chief project manager opinions and experiences of the organisations by conducting interviews and questionnaires in our research. The results reveals the difficulty to find proper product owners in the Agile projects. It is challenging to set a product owner who has Agile knowledge and is expert in the project domain. Specialized training and coaching for product owners is mentioned as one of the solutions that could be provided for this challenge. “Distributed teams”, “Lack of focus on the business side” and “Weak coaching and support” are some of the other critical areas which have been presented by the participants in the interviews and survey in this study. The main conclusion is that in order to have a successful transition to Agile approaches, the Agile mind-set should be set in all different part in an organizations, not only the development side and also that everyone have to understand “Why” Agile is beneficial. Also the communication of lessons learnt and feedback should be strong and effective in order to avoid repetition of the same mistakes. In addition, specialized training and coaching for different roles within the period of the development is necessary to ensure the successful adoption of Agile.Synen på mjukvaruutveckling har förändrats under det senaste decenniet; Vattenfalls- eller traditionella kommando- och styrmetoder har ersatts av Agila metoder. Agila utvecklingsmetoder kom som en "lösning" till nackdelarna med vattenfalls metodiken, men användning av Agila metoder har sina egna utmaningar. På grund av Agila metoders attraktiva egenskaper såsom flexibilitet och kort tid till marknaden, har denna typ av utveckling blivit alltmer populärt och antalet organisationer som har börjat flytta till Agila metoder växer varje dag. Att genomföra nya metoder i en organisation är alltid en stor utmaning. Särskilt för stora organisationer på grund av deras komplexitet, med tanke på många olika samverkande gränssnitt, stark organisationskultur, etc. Karaktären på dessa utmaningar och hinder ändras från olika perspektiv inom en organisation, och vart och ett av dessa perspektiv behöver studeras och undersökas för att säkerställa en framgångsrik övergång från traditionella metoder till Agila metoder. I denna avhandling fokuserar vi på projektledare och projektförvaltningsperspektiv. Vi strävar efter att definiera framgångs- och misslyckande faktorer som spelar en nyckelroll i att flytta från traditionella metoder till Agila metoder i storskaliga organisationer. För att möta dessa utmaningar genomfört vi dessutom en litteraturstudie av den senaste forskningen om införande av Agila metoder. För att samla våra data vi använt en kombination av kvalitativa och kvantitativa forskningsmetoder. Vi utforskade både projektledare för IT och chefs-projektledare sidor av organisationer genom intervjuer och enkäter i vår forskning. Resultaten visar den kritiska roll produktägare utgör i Agila projekt. Det är en utmaning att tillsätta en korrekt produktägaren som har Agile kunskap och är expert i projektet domänen. Specialiserad utbildning och coaching för produktägare nämns som en av de möjliga lösningar som finns för denna utmaning. "distribuerade team", "brist på fokus på affärssidan" och "Svag coachning och support" är några av de andra viktiga områden som har lagts fram av deltagarna i intervjuerna och undersökning i denna studie. Den viktigaste slutsatsen är att för att få en lyckad övergång till Agila metoder bör Agilt tänkande tillämpas i alla delar i en organisations, inte bara utvecklingssidan, utan alla måste förstå "varför" Agila metoder är fördelaktigt. Även överföring av lärdomar och återkoppling bör vara stark och effektiv för att undvika återkommande samma misstag. Dessutom, specialiserad utbildning och coaching för olika roller och inom den tidsfrist för utvecklingen är nödvändig för att säkerställa ett framgångsrikt antagande av Agila arbetsmetoder.
39
Koo, Hsuehyung Benjamin 1967. "Improving product development capability maturity through object process methodology." Thesis, Massachusetts Institute of Technology, 2001. http://hdl.handle.net/1721.1/91772.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, System Design & Management Program, 2001."September 2001."
Includes bibliographical references (leaf 62).
by Hsuehyung Benjamin Koo.
S.M.
40
Grey, Johannes. "An investigation of the suitability of agile system development methodologies for the development of data warehouses / J. Grey." Thesis, North-West University, 2006. http://hdl.handle.net/10394/1596.
Full text
41
Saadatmand, Fatemeh. "Which agile methodology suits you? By applying the results on a multi-disciplinary project in a small company." Thesis, Högskolan i Borås, Institutionen Handels- och IT-högskolan, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:hb:diva-17166.
Full textAbstract:
Choosing the Software Development Methodology is the very first step of any project; thus,has been a hot topic among, both, practitioners and academic people. After using plandrivensoftware development methodologies software development researchers came up withthe idea of agile software development methodologies as a masterpiece. Although, failurestories of some teams brought about fading the idea that agile methodologies are thebest recipe for any kind of development project. Considering the lack of studies in helpingpractitioners to select the most appropriate agile software methodology, this study aims atprovide the software development manager with a thorough knowledge of agile methodologiesand the criteria that should be considered, while selecting one of them. A case study is used asan empirical support.Program: Magisterutbildning i informatik
42
Al-Harbi, Fahhad. "Development of a methodology and an expert system for disaster recovery." Thesis, University of Newcastle Upon Tyne, 1997. http://hdl.handle.net/10443/2077.
Full textAbstract:
The number of organisations that rely on computerised systems to perform their day-today operations and to help them in making decisions has grown rapidly over the last few years and continues to expand. On the other hand, the destruction or loss of these systems can be a nightmare and, in many cases, may leed to an end of providing services or trading for the organisation. Thus, the growing dependence on computer systems and the fear of being out of business have increased management awareness and understanding of the importance of plans to prevent or recover from a computer failure. Although senior management and IT directors have begun to appreciate the need for Disaster Recovery Plans (DRPs), they often raise common questions, such as. How long the organisation can tolerate the failure of its computer systems? Are we spending too much or too little on a recovery strategy? What type of recovery strategy is most appropriate for our IT centre? To look more closely at the effects of disasters on organisations and the importance of adopting DRPs, the researcher carried out a case study involving III organisations in Kuwait to examine their DRPs before and after the Iraqi Invasion in 1990 and to identify major problems facing IT managers on disaster recovery issues The literature review and the case study show that there is a lack of a comprehensive methodology and of a computerised intelligent system to guide organisations in selecting the most appropriate recovery strategy for their computer centres. Therefore, this research has developed a methodology and delivered an expert system that would assist IT directors to obtain answers to the above-mentioned questions and perform fast recovery from any type of computer disaster. The methodology consists of five phases that provide a step-by-step approach to ensure that the entire recovery strategy selection process is covered. The phases are: Threats Assessment, Business Impact Assessment, Recovery Strategy Analysis, Cost Analysis, and Recommendations.
43
Ng, Quinton 1977. "The development of a resource allocation methodology to support system design." Thesis, Massachusetts Institute of Technology, 2002. http://hdl.handle.net/1721.1/89910.
Full text
44
Fartash, Homa. "Development of System-Based Methodology to Support Ramp Metering Deployment Decisions." FIU Digital Commons, 2017. https://digitalcommons.fiu.edu/etd/3648.
Full textAbstract:
Ramp metering is an effective management strategy, which helps to keep traffic density below the critical value, preventing breakdowns and thus maintaining the full capacity of the freeway. Warrants for ramp metering installation have been developed by a number of states around the nation. These warrants are generally simple and are based on the traffic, geometry, and safety conditions in the immediate vicinity of each ramp (local conditions). However, advanced applications of ramp metering utilize system-based metering algorithms that involve metering a number of on-ramps to address system bottleneck locations. These algorithms have been proven to perform better compared to local ramp metering algorithms. This has created a disconnection between existing agency metering warrants to install the meters and the subsequent management and operations of the ramp metering. Moreover, the existing local warrants only consider recurrent conditions to justify ramp metering installation with no consideration of the benefits of metering during non-recurrent events such as incidents and adverse weather.
This dissertation proposed a methodology to identify the ramps to meter based on system-wide recurrent and non-recurrent traffic conditions. The methodology incorporates the stochastic nature of the demand and capacity and the impacts of incidents and weather using Monte Carlo simulation and a ramp selection procedure based on a linear programming formulation. The results of the Monte Carlo simulation are demand and capacity values that are used as inputs to the linear programming formulation to identify the ramps to be metered for each of the Monte Carlo experiments. This method allows the identification of the minimum number of ramps that need to be metered to keep the flows below capacities on the freeway mainline segment, while keeping the on-ramp queues from spilling back to the upstream arterial street segments. The methodology can be used in conjunction with the existing local warrants to identify the ramps that need to be metered. In addition, it can be used in benefit-cost analyses of ramp metering deployments and associated decisions, such as which ramps to meter and when to activate in real-time. The methodology is extended to address incidents and rainfall events, which result in non-recurrent congestion. For this purpose, the impacts of non-recurrent events on capacity and demand distributions are incorporated in the methodology.
45
Griffin, Audrey S. "Examining the Decision Process and Outcomes of System Development Methodology Adoption." Kent State University / OhioLINK, 2008. http://rave.ohiolink.edu/etdc/view?acc_num=kent1209338387.
Full text
46
Ahn, Seung B. "Methodology for evaluating transportation-induced regional development." Diss., This resource online, 1996. http://scholar.lib.vt.edu/theses/available/etd-06062008-144948/.
Full text
47
Cornejo, Gómez César Alberto. "Methodology for the development of hydroelectric power plants." Thesis, Massachusetts Institute of Technology, 2016. http://hdl.handle.net/1721.1/107592.
Full textAbstract:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, School of Engineering, System Design and Management Program, Engineering and Management Program, 2016.Cataloged from PDF version of thesis.
Includes bibliographical references (pages 73-75).
Hydropower has sufficient resources available and is actively promoted by Governments as part of their energy matrix, but its development is constrained by the difficulty of addressing location particularities, including technical features such as geology or hydrology, and institutional features such as social acceptance, environmental constraints and the regulatory framework. Project results emerge from the interactions of these Inherent Features and the Project Architecture and do not always meet stakeholders' expectations, leading to deficient project results and lost value. This thesis proposes a methodology for prototyping projects to reflect these particularities and inform project shaping and decision-making early in the process. The proposed methodology was built on three systems engineering and project complexity frameworks, and lessons learned from four case studies. Its contribution to hydropower development is related to (i) the incorporation of systems evolution over time on the development process, (ii) the identification and management of relationships among the various decomposed elements of the development, (iii) the identification of emergent properties from the interactions among all features, (iv) a prototype for developers to optimize or search for project architectures that meet stakeholders objectives while complying with restrictions, (v) the delivery of unbiased information for decision-makers, (vi) the opportunity of stakeholders to participate in the project shaping in a continuous fashion, and (vii) the delivery of a tool for the implementation team to evaluate and challenge changes to the project during construction. The usage of this methodology does not guarantee the avoidance of errors or unforeseen project outcomes, but it does reduce the chance for unknown risks emerging from the interactions of the evaluated features.
by César Alberto Cornejo Gómez.
S.M. in Engineering and Management
48
Tebaldi, Enrico. "SIMAID : a rapid development methodology for the design of acyclic, bufferless, multi-process and mixed model agile production facilities for spaceframe vehicles." Thesis, University of Warwick, 2001. http://wrap.warwick.ac.uk/3069/.
Full textAbstract:
The facility layout problem (FL) is a non-linear, NP-complete problem whose complexity is derived from the vast solution space generated by multiple variables and interdependent factors. For reconfigurable, agile facilities the problem is compounded by parallelism (simultaneity of operations) and scheduling issues. Previous work has either concentrated on conventional (linear or branched) facility layout design, or has not considered the issues of agile, reconfigurable facilities and scheduling. This work is the first comprehensive methodology incorporating the design and scheduling of parallel cellular facilities for the purpose of easy and rapid reconfiguration in the increasingly demanding world of agile manufacturing. A novel three-stage algorithm is described for the design of acyclic (asynchronous), bufferless, parallel, multi-process and mixed-model production facilities for spaceframe-based vehicles. Data input begins with vehicle part processing and volume requirements from multiple models and includes time, budget and space constraints. The algorithm consists of a powerful combination of a guided cell formation stage, iterative solution improvement searches and design stage scheduling. The improvement iterations utilise a modified (rules-based) Tabu search applied to a constant-flow group technology, while the design stage scheduling is done by the use of genetic algorithms. The objective-based solution optimisation direction is not random but guided, based on measurement criteria from simulation. The end product is the selection and graphic presentation of the best solution out of a database of feasible ones. The case is presented in the form of an executable program and three real world industrial examples are included. The results provide evidence that good solutions can be found to this new type and size of heavily constrained problem within a reasonable amount of time.
49
Bucher, Nico [Verfasser], and Jens [Akademischer Betreuer] Eickhoff. "Merging spacecraft software development and system tests : an agile verification approach / Nico Bucher ; Betreuer: Jens Eickhoff." Stuttgart : Universitätsbibliothek der Universität Stuttgart, 2021. http://d-nb.info/1228861692/34.
Full text
50
Dyrhage, Max. "Incorporating a tag management system in an agile web development process to become more data-driven." Thesis, KTH, Skolan för datavetenskap och kommunikation (CSC), 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-240395.
Full textAbstract:
Web analytics are used to track and examine user behavior on websites and web applications. In order to take data driven decisions companies and organizations working with the web look to web analytics to understand their users. A piece of Javascript code that collect user behavior and information is often referred to as a tag, which can be managed through a tag management system. Tag management systems can provide structure to how a website’s users’ behaviors are being measured. This study examines how a tag management system can enable web analytics of user data to be incorporated in an agile web development process at the Swedish company Dailybitsof. With a literature study, case study and interviews with professionals on the subject, a set of recommendations to enable web analytics is presented. This study suggests that a tag management system can enable web analytics to be incorporated into an agile web development process if it is implemented in combination with changes to the agile process.Webbanalys används för att spåra och undersöka användarbeteende på hemsidor och webbapplikationer. För att ta datadrivna beslut, använder sig företag och organisationer av webbanalys för att förstå sina användare. Några rader Javascript-kod kan användas för att samla upp användarbeteende och kallas ibland för ett tag. Dessa tags kan behandlas i ett så kallad tag management-system. Tag management-system kan ge struktur över hur användarbeteendet på en hemsida spåras och analyseras. Den har uppsatsen undersöker hur ett tag management-system kan möjliggöra att data från webbanalys blir använt i en agil webbutvecklingsprocess hos det svenska företaget Dailybitsof. Med en litteraturstudie, fallstudie och intervjuer med professionella inom ämnet presenteras rekommendationer för att att möjliggöra webbanalys. Uppsatsen föreslår att ett tag management-system kan möjliggöra användandet av webbanalys i en agil webbutvecklingsprocess om det implementeras i kombination med ändringar av den agila processen.