Relevant bibliographies by topics / Agile iterative development

Journal articles
Dissertations / Theses
Books
Book chapters
Conference papers

Academic literature on the topic 'Agile iterative development'

Author: Grafiati

Published: 11 December 2022

Last updated: 26 January 2023

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Agile iterative development.'

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.

Journal articles on the topic "Agile iterative development"

van Oorschot, Kim E., Kishore Sengupta, and Luk N. Van Wassenhove. "Under Pressure." Project Management Journal 49, no. 6 (October 15, 2018): 78–102. http://dx.doi.org/10.1177/8756972818802714.

Full text

Abstract:

The iterative cycles used in agile software development create a series of deadlines for project teams. We investigate the optimal iteration length under behavioral conditions for agile software projects. Based on system dynamics simulation, we argue that both very long (as in sequential development) and very short (monthly) iterative cycles create huge and disruptive fluctuations in schedule pressure experienced by the team. These lead to poor performance in terms of quality, as well as costs and time compared with optimal iterative cycles of two to three months. The monthly cycles used in many agile practices might be too short to ensure optimal performance.

APA, Harvard, Vancouver, ISO, and other styles

Salo, Outi, and Pekka Abrahamsson. "An iterative improvement process for agile software development." Software Process: Improvement and Practice 12, no. 1 (January 2007): 81–100. http://dx.doi.org/10.1002/spip.305.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Bonner, Nancy A., Nisha Kulangara, Sridhar Nerur, and James T. C. Teng. "An Empirical Investigation of the Perceived Benefits of Agile Methodologies Using an Innovation-Theoretical model." Journal of Database Management 27, no. 3 (July 2016): 38–63. http://dx.doi.org/10.4018/jdm.2016070103.

Full text

Abstract:

There is little doubt that agile software development (ASD) methods have gained widespread acceptance in industry. Despite the attention these methods have received, there is little empirical affirmation of the benefits that accrue to those who use agile methodologies. Grounded in the conceptual foundations of innovation diffusion and agile philosophy of development, the authors' study validates a model to assess the perceived advantage of an iterative approach to software development. Consistent with their predictions, the results suggest that evolutionary development - the cornerstone of agile development – is perceived to be less complex and more compatible with the work habits of developers. Further, the findings support the hitherto unsubstantiated claim that iterative development yields benefits to software developers. However, process flexibility, yet another important characteristic of agile development, had no significant impact on complexity, compatibility, and relative advantage. The implications of the study for academics and practitioners, and directions for future research are discussed.

APA, Harvard, Vancouver, ISO, and other styles

Caballero, Leydi, Ana M. Moreno, and Ahmed Seffah. "How Agile Developers Integrate User-Centered Design Into Their Processes: A Literature Review." International Journal of Software Engineering and Knowledge Engineering 26, no. 08 (October 2016): 1175–201. http://dx.doi.org/10.1142/s0218194016500418.

Full text

Abstract:

The lack of user engagement, the absence of user feedback, incomplete and continuously changing user requirements are among the critical concerns that cause projects to fail. User-centered design (UCD) and agile software development are two iterative approaches that have been proposed to overcome such concerns. UCD is a design process focusing on user research, user interface design and usability evaluation. Introduced by software engineering practitioners, agile refers to a number of iterative and incremental software development practices that emphasize people’s needs, communication between developers and stakeholders and the ability to adapt to change. In both the agile and UCD communities, however, a full understanding of user requirements is often seen as incompatible with early and quick development iterations. We performed a literature review aiming to identify how agile teams have integrated UCD tools into their agile software development process to a better understanding of the user requirements without losing sight of the agile values and principles. UCD tools adaptations and minimal-up-front design applied in agile development are among the approaches discovered in this study. The findings could lead to a comprehensive user-centric software engineering that will overcome inherent problems faced by agile teams to understand user needs, priorities and goals.

APA, Harvard, Vancouver, ISO, and other styles

Riesener, Michael, Christian Doelle, Stefan Perau, Philipp Lossie, and Guenther Schuh. "Methodology for iterative system modeling in agile product development." Procedia CIRP 100 (2021): 439–44. http://dx.doi.org/10.1016/j.procir.2021.05.101.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Rahman, Nayem, Dale Rutz, and Shameem Akhter. "Agile Development in Data Warehousing." International Journal of Business Intelligence Research 2, no. 3 (July 2011): 64–77. http://dx.doi.org/10.4018/jbir.2011070105.

Full text

Abstract:

Traditional data warehouse projects follow a waterfall development model in which the project goes through distinct phases such as requirements gathering, design, development, testing, deployment, and stabilization. However, both business requirements and technology are complex in nature and the waterfall model can take six to nine months to fully implement a solution; by then business as well as technology has often changed considerably. The result is disappointed stakeholders and frustrated development teams. Agile development implements projects in an iterative fashion. Also known as the sixty percent solution, the agile approach seeks to deliver more than half of the user requirements in the initial release, with refinements coming in a series of subsequent releases which are scheduled at regular intervals. An agile data warehousing approach greatly increases the likelihood of successful implementation on time and within budget. This article discusses agile development methodologies in data warehousing and business intelligence, implications of the agile methodology, managing changes in data warehouses given frequent change in business intelligence (BI) requirements, and demonstrates the impact of agility on the business.

APA, Harvard, Vancouver, ISO, and other styles

Rindell, Kalle, Sami Hyrynsalmi, and Ville Leppänen. "Fitting Security into Agile Software Development." International Journal of Systems and Software Security and Protection 9, no. 1 (January 2018): 47–70. http://dx.doi.org/10.4018/ijsssp.2018010103.

Full text

Abstract:

Security objectives in software development are increasingly convergent with the business objectives, as requirements for privacy and the cost of security incidents call for more dependable software products. The development of secure software is accomplished by augmenting the software development process with specific security engineering activities. Security engineering, in contrast to the iterative and incremental software development processes, is characterized by sequential life cycle models: the security objectives are thus to be achieved by conflicting approaches. In this study, to identify the incompatibilities between the approaches, the security engineering activities from Microsoft SDL, the ISO Common Criteria and OWASP SAMM security engineering models are mapped into common agile software development processes, practices and artifacts.

APA, Harvard, Vancouver, ISO, and other styles

Puik, Erik, and Dareks Ceglarek. "Application of Axiomatic Design for Agile Product Development." MATEC Web of Conferences 223 (2018): 01004. http://dx.doi.org/10.1051/matecconf/201822301004.

Full text

Abstract:

Agile, and iterative, development methods for new product development are gaining in popularity under product engineers; where it initially was just applied for software development, now larger adoption takes place for product development in general. The design rules of agile development are somewhat conflicting with the guidelines of Axiomatic Design. In this paper, it is investigated why this is the case, what can be done about it, and how can the strengths of agile development be combined with Axiomatic Design to optimise methods for product design. It is shown that the methods are indeed advising on different and conflicting strategies, however, by attenuating the agile design rules in the early stage of design, and doing the same for AD in the later stage of design, best of both worlds can be combined.

APA, Harvard, Vancouver, ISO, and other styles

Zakrzewski, Pawel, Janusz Narkiewicz, and Darren Brenchley. "Safety Critical Software Development Methodologies in Avionics." Transactions on Aerospace Research 2020, no. 2 (June 1, 2020): 59–71. http://dx.doi.org/10.2478/tar-2020-0011.

Full text

Abstract:

AbstractThis article summarizes avionics safety-critical software development methodologies and implications of the DO-178C standard from an Agile application perspective. We explain the safety-critical software categorization. It also outlines the main differences and advantages of different approaches to the development process, from Waterfall through the V-model to Iterative and Incremental. Agile principles are explained as well as a Scrum – which is a popular framework in the non-safety-critical software industry. The application of Agile, for safety-critical software considerations, is based on the practical knowledge of the authors, and looks at the potential solution from a DO-178C standard, size of the project, scalability, and organizational culture points of view. Definition of the Agile type of framework, consistent with the certification process and existing standards, has been highlighted as a potential game-changer for the avionics industry.

APA, Harvard, Vancouver, ISO, and other styles

McLellan, Jamie, William A. Young, Elizabeth C. Levin, and Lester W. Johnson. "Developing Innovative Integrated Business Solutions Using a Scrum Project Management Methodology." Businesses 1, no. 2 (July 27, 2021): 91–101. http://dx.doi.org/10.3390/businesses1020007.

Full text

Abstract:

Innovative manufacturers have used Integrated Business Solutions (IBSs) as a means to co-create products and services to solve diverse business problems and more effectively compete in their field of endeavour. However, the efficacy and benefits of IBSs have been diminished due to the rigid method in which project management has been applied. This paper provides a conceptual approach for manufacturers to create new revenue sources in collaboration with their customers by adopting an agile project methodology that accommodates the interactive and iterative nature of IBS development. The research findings highlight the lack of success in IBSs using traditional project management as the delivery method. It provides an alternative solution in the use of an agile project management approach with its customer-centred and iterative mindset. This paper provides a conceptual model of the agile method known as Scrum and describes how it better aligns with innovative IBS development. Though both IBSs and agile have been around for several decades, their development is still in a state of infancy. This research adds to the body of literature on the application of agile in IBSs and presents an argument for converting its conceptual model into a practice delivery.

APA, Harvard, Vancouver, ISO, and other styles

More sources

Dissertations / Theses on the topic "Agile iterative development"

Erickson, Alyssa Jean. "Agile Development in Instructional Design: A Case Study at BYU Independent Study." BYU ScholarsArchive, 2018. https://scholarsarchive.byu.edu/etd/6780.

Full text

Abstract:

Agile development is a software development methodology that originated in 2001 (Beck, et al.). It has since gained wide recognition and use in the software industry, and is characterized by iterative development cycles. Organizations outside of the software industry are also finding ways to adapt Agile development to their contexts. BYU Independent Study (BYUIS) is an online education program at Brigham Young University that provides online courses at the high school and university levels. In April 2016, BYUIS implemented the Agile development process to the design and development of online courses. This thesis is a case study that looks specifically at the adoption of Agile at BYUIS, from its implementation in April 2016 to the time of this study in summer of 2017. The question this qualitative study seeks to answer is as follows: how and why did the adoption of the Agile development methodology to instructional design practices at BYUIS reflect or differ from the 12 principles of Agile development? To answer this research question, the researcher used multiple data sources: semi-structured interviews with three administrators, two production team managers, and three instructional designers; surveys for BYUIS student employees (i.e., scrum team members) after each week of observation; and field note observations of three Agile scrum teams for two weeks each. The data from each of these sources was analyzed through a descriptive coding process and then organized into a thematic network analysis. The Results section analyzes evidence from the interviews, surveys, and observations that reflect or differ from each of the 12 principles of Agile. The Discussion addresses three main issues of implementing Agile at BYUIS: how to accommodate for part-time schedules, the complexity of working on different projects, and how to facilitate communication in scrum teams if co-location is not possible. It also looks at how these three issues could be manifest in other organizations and introduces potential solutions. The researcher then presents suggestions for future research on Agile in instructional design or other contexts.

APA, Harvard, Vancouver, ISO, and other styles

Chipunza, Enciliah. "Quality management challenges in iterative software product development of a selected software development organisation in Cape Town, South Africa." Thesis, Cape Peninsula University of Technology, 2018. http://hdl.handle.net/20.500.11838/2779.

Full text

Abstract:

Thesis (MTech (Business Information Systems))--Cape Peninsula University of Technology, 2018.
Many software organisations using iterative software development approach use practices that relate to quality management. However, the quality management process has been inadequate. Despite many research studies conducted on quality management in iterative software product development none have adequately addressed the challenges and mitigation techniques to have an adequate process that leads to a quality software product. The objective of this study was to determine factors that affect the quality management process in iterative software development. The research followed a qualitative approach, a case of software organisation SasTech in Cape Town, South Africa. 22 interviews were conducted on three roles actively involved in the software product development process. These are product management, quality assurance and software developers. Themes were drawn from results and were tabulated. The duality of technology theory was used as a theoretical lens to data analysis. Several factors were identified to influence the software quality management process. These include planning, documentation, process ownership, technologies, testing, timelines and management support. Through the general proposed framework, facilities (human resources and technologies), interpretive schemes (architecture) and norms (practices) of software quality management can be institutionalised leading to adequate and effective quality management in iterative development for SasTech as well as other organisations in the same industry.

APA, Harvard, Vancouver, ISO, and other styles

Mirisaee, Seyed Hadi. "Human-centred methods for design of mobile social technologies : a case study of agile ridesharing." Thesis, Queensland University of Technology, 2014. https://eprints.qut.edu.au/72909/2/Seyed_Hadi_Mirisaee_Thesis.pdf.

Full text

Abstract:

Social contexts are possible information sources that can foster connections between mobile application users, but they are also minefields of privacy concerns and have great potential for misinterpretation. This research establishes a framework for guiding the design of context-aware mobile social applications from a socio-technical perspective. Agile ridesharing was chosen as the test domain for the research because its success relies upon effectively connecting people through mobile technologies.

APA, Harvard, Vancouver, ISO, and other styles

Chidyiwa, Octavia. "An investigation of the best-practices for implementing an Ecommerce software engineering project comparing two common methodologies, viz. Agile and Traditional." University of the Western Cape, 2020. http://hdl.handle.net/11394/7925.

Full text

Abstract:

Masters of Science
In a world where technology is advancing at a very rapid pace, global competition has significantly increased, and this is putting pressure on software companies to produce quality software. It has therefore become critically important to manage well the implementation of software engineering projects by employing effective methods that ensure the best product is produced. The most popular software project implementation methodologies are the Traditional methods and Agile methods. This research explored these two methodologies by comparing the strength and weakness of both approaches. The research was conducted using a constructionist epistemology with a critical inquiry using the grounded theory methodology, applying both quantitative and qualitative methods to the case studies. Findings were collected through participant observation using a designed questionnaire targeting a selected sample of the study population. This sample of the population consisted of Ecommerce organizations in the Western Cape province of South Africa to establish which of the Traditional or Agile methods would best lead to the successful implementation of Ecommerce software engineering projects. The research results showed that the Agile methodology was the preferred and recommended approach. Very few participants of the research supported the Traditional approach to still be considered and used for projects with well-known end goals. An Ecommerce website prototype for a local Cape Town business was constructed as following the Agile approach to measure and validate the findings of the research. The prototype was built successfully from conception to the final delivery product and on time confirming the Agile approach as best for Ecommerce software development. In conclusion, the Agile methodology is the choice approach based on reviewed literature, the research results, and the prototype construction. These results will help in critical decision making regarding an appropriate development methodology to follow for the Ecommerce industry in the Western Cape.

APA, Harvard, Vancouver, ISO, and other styles

Rytíř, Vladimír. "Rational Unified Process jako metodika vývoje softwaru." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2008. http://www.nusl.cz/ntk/nusl-235958.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Omair, Muhammad. "Challenges in understanding software requirements in agile based offshore development." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3740.

Full text

Abstract:

Agile based development seems to become a favorable model for offshore development. It allows both on and offshore team to work in small iterations minimizing the effect of change in software requirements and at the same time developing regular communication between them. However different factors such as physical distance and lack of communication between on and offshore team becomes a hurdle between them leading to misunderstandings about software requirements. This research work gives an insight about these challenges from the software industry by presenting and discussing the responses of four software companies located in different countries, collected through an online questionnaire. The authors found that lack of communication between on and offshore site is seen as a major challenge for better understanding of software requirements. Shorter iterations at the offshore site require more communication with the onshore site. The language problem seems to exist only when both on and offshore site who are non-English speakers communicate in English. Regular long distance meetings would help in better understanding of software requirements. Previous domain and product knowledge is helpful in better understanding of software requirements. This research work would allow different stakeholders within agile based on/offshore setting to better understand these challenges and deal accordingly with them.

APA, Harvard, Vancouver, ISO, and other styles

Archontakis, Ioannis Stylianos. "Agile development in the video game industry : Examining the effects of iteration and methods of limiting it." Thesis, Umeå universitet, Företagsekonomi, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-156211.

Full text

Abstract:

This research is examining one of the most dominant managerial methods used in development in the video game industry, Agile development. More particularly, the thesis examines a certain attribute of Agile development, that of iteration. The thesis will set to examine how iteration affects several layers of development during the production of a video game and whether it can be replaced by other managerial technics.As a result, the purpose of this thesis is to raise a different viewpoint against the Agile’s iteration. Furthermore, this thesis aims to contribute to the academic research by concentrating on the video game industry, an industry that is often neglected by the academia.The theoretical framework and literature review concentrate on concepts of Agile development, overworking, development cycle in video games, definitions of project success and project failures and creative process in video game development.The thesis deploys qualitative methodology to address and research its data. The collected data belongs to two categories, data stemming from interviews conducted by the thesis’s author and data stemming from journalistic magazines.The results of both type of data are compared and act supplementary to each other, then they are analyzed to answer the research questions asked by this thesis. The results showcase that iteration has negative effects to video game developers in both a macroscale (company’s resources, annual revenue) and in a microscale (overworking, health issues) level. The results also highlight that Agile is an all-time favorite development methodology of developers in the video game industry.In conclusion, the thesis supports the notion that iteration should be suppressed and proposes a number of solutions for that matter. The suggestions are essentially encouragement towards developers: to seek higher interactivity with customers throughout the duration of all the development stages of a video game, to show more trust to established gameplay mechanics and to place more reliance on a franchise’s profit power and benefits. These measures can be used in a preventive manner in order to limit the appearance of iteration and as a result, to limit its’ negative effects.

APA, Harvard, Vancouver, ISO, and other styles

Wilmsen, Miriam, Markus Spadinger, Albert Albers, Cong Minh Nguyen, and Jonas Heimicke. "Iterationsarten und deren Auslöser in der Frühen Phase der PGE – Produktgenerationsentwicklung." Thelem Universitätsverlag & Buchhandlung GmbH & Co. KG, 2019. https://tud.qucosa.de/id/qucosa%3A36960.

Full text

Abstract:

Insbesondere die frühen Phasen in Prozessen der Mechatroniksystementwicklung sind durch ein hohes Maß an Unsicherheit gekennzeichnet. Zu diesem Zeitpunkt des Produktentstehungsprozesses liegen lediglich vage und unscharfe Anforderungen an das Produkt vor, welche es zu konkretisieren gilt. Aktuelle Herausforderungen der Produktentwicklung haben einen verstärkenden Effekt auf die Unsicherheiten in frühen Entwicklungsphasen. Diesen begegnen Unternehmen aus dem Bereich der Mechatroniksystementwicklung zunehmend mit der Implementierung agiler Entwicklungsansätze in ihre etablierten Prozesse. Neben der frühen und kontinuierlichen Kundeneinbindung, der klare Ausrichtung der Prozesse auf die Wertsteigerung der Produkte aus Kundensicht, flachen und offenen Hierarchien und dem stetigen Aufbau und Weiterentwicklung von Prototypen verleihen meist geplante Iterationen den jeweiligen Projekten das Adjektiv „agil“. Die Vielfalt der in der Literatur beschriebenen und meist generisch formulierten Arten von Iterationen (geplant oder ungeplant, korrekturbezogen oder progressiv) ist jedoch sehr groß. Zudem werden Iterationen in der Praxis meist intuitiv und unbewusst durchgeführt, was zum einen dazu führt, dass das jeweilige Entwicklungsvorgehen nicht situationsoptimal ausgeführt wird oder gar hinsichtlich der Ergebnissynthese und –Analyse redundante Tätigkeiten erfolgen. Aus diesem Grund verfolgt das vorliegenden Forschungsvorhaben die Zielsetzung, einen Beitrag zur Unterstützung der Produktentwickler in frühen Entwicklungsphasen bei der Identifikation notwendiger Iterationen zu leisten. Durch eine Berücksichtigung dieser in der kurz- und mittelfristigen Projektplanung kann somit die Prozessunsicherheit reduziert werden.

APA, Harvard, Vancouver, ISO, and other styles

Sabar, Suneel. "Software Process Improvement and Lifecycle Models in Automotive Industry." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-69640.

Full text

Abstract:

The quality of a product depends on the quality of the underlying process is a well known fact. Software development organizations have been struggling to decrease their cost, increase their ROI, reduce time-to-market, and enhance the quality of their products. This all depends upon the improvement in the processes they are following inside their organizations. A number of software process improvement models exist in market, e.g., CMMI, SPICE and Automotive SPICE. But before an organization can improve its development and management processes, it is very important to know whether it is following the right processes. There exist a number of software development process models, mainly categorized into Traditional and Agile, which provide the step-by-step guidance to develop and manage the software projects.The current thesis presents a study of software process improvement models in automotive industry, their weaknesses and strengths and presents a comparison of how do they relate to each other. This thesis also explores some software development models which are more famous in automotive industry, and the applicability of process improvement models in conjunction with the Agile software development models. A case study was performed at an automotive software supplier organization to investigate the experience of combining Agile practices with organization’s company-tailored software development model that was incorporating Automotive SPICE standards.

APA, Harvard, Vancouver, ISO, and other styles

Ruprecht, Marek. "Agilní modelováni při vývoji software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2011. http://www.nusl.cz/ntk/nusl-412841.

Full text

Abstract:

The thesis is focused on software development process and its products from initial designs through the way of implementation until final delivery to customer. The thesis brings up some basic facts about software engineering with further detailed description of one of its parts, the modern models of software life cycles with focus on the agile life cycle because of its significant benefits and effective implementation. This model is represented by Agile Model Driven Development which has been submitted not only theoretically but in practice. Finally, there is also a short description of Unified Modeling Language which is used as a modeling language.

APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "Agile iterative development"

Larman, Craig. Agile and iterative development: A manager's guide. Boston: Addison-Wesley, 2004.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

Larman, Craig. Agile and Iterative Development: A Manager's Guide. Addison-Wesley Professional, 2003.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

Larman, Craig. Agile and Iterative Development: A Manager's Guide. Addison-Wesley Professional, 2003.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

Agile & iterative develpment: a manager´s guide. Addison Wesley, 2003.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

Larman, Craig. Software Engineering Distilled with Agile Iterative Development. Pearson Education, Limited, 2019.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

Landry, Nat. Iterative and Agile Implementation Methodologies in Business Intelligence Software Development. Lulu Press, Inc., 2011.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

Commercial Vehicles 2021. VDI Verlag, 2021. http://dx.doi.org/10.51202/9783181023808.

Full text

Abstract:

Contents Ways to achieve Zero Emission ZF E-Mobility products and software for commercial vehicles ..... 1 Thermoelectric generators for heavy-duty vehicles as an economical waste heat recovery system ..... 17 Hybridization of heavy duty trucks – Market analysis and technology for high voltage as well as low voltage solutions ..... 33 Development processes and methods Lightweight construction and cost reduction – a lean, agile MSCDPS® product development process ..... 43 eDrive & Fuel Cell powertrain systems engineering for commercial vehicles ..... 55 Fatigue development of a 10x10 commercial vehicle frame using dynamic and/or strength simulation, virtual iteration and component testing together with measurement data acquisition ..... 73 Data-driven selection of vehicle variants for the E/E integration test – Increasing variants and complex technology versus test coverage ..... 81 Hydrogen propulsion High performance and efficiency hydrogen engine using westport fuel systems’ Commercially available HPDI fuel system ..... 97 E/E architecture and operating strategy for fuel-cell trucks – Challenges...

APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Agile iterative development"

Mnkandla, Ernest. "A Thinking Framework for the Adaptation of Iterative Incremental Development Methodologies." In Extreme Programming and Agile Processes in Software Engineering, 315–16. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/11499053_64.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Das, Rayaguru Akshaya Kumar, and A. B. Khan. "A Study of Agile Iterative Development Methodology on Web Application Quality." In Digital Democracy – IT for Change, 19–26. Singapore: Springer Singapore, 2021. http://dx.doi.org/10.1007/978-981-16-2723-1_3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Berntzen, Marthe, Viktoria Stray, and Nils Brede Moe. "Coordination Strategies: Managing Inter-team Coordination Challenges in Large-Scale Agile." In Lecture Notes in Business Information Processing, 140–56. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-78098-2_9.

Full text

Abstract:

AbstractInter-team coordination in large-scale software development can be challenging when relying on agile development methods that emphasize iterative and frequent delivery in autonomous teams. Previous research has introduced the concept of coordination strategies, which refer to a set of coordination mechanisms to manage dependencies. We report on a case study in a large-scale agile development program with 16 development teams. Through interviews, meeting observations, and supplemental document analyses, we explore the challenges to inter-team coordination and how dependencies are managed. We found four coordination strategies: 1) aligning autonomous teams, 2) maintaining overview in the large-scale setting, 3) managing prioritizations, and 4) managing architecture and technical dependencies. This study extends previous research on coordination strategies within teams to the inter-team level. We propose that large-scale organizations can use coordination strategies to understand how they coordinate across teams and manage their unique coordination situation.

APA, Harvard, Vancouver, ISO, and other styles

Furterer, Sandra L. "Lean, Iterative, and Agile Life Cycles that Can Be Used to Streamline System Design and Development Timelines." In Systems Engineering, 337–52. Boca Raton: CRC Press, 2021. http://dx.doi.org/10.1201/9781003081258-16.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Looks, Hanna, Jannik Fangmann, Jörg Thomaschewski, María-José Escalona, and Eva-Maria Schön. "Towards a Standardized Questionnaire for Measuring Agility at Team Level." In Lecture Notes in Business Information Processing, 71–85. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-78098-2_5.

Full text

Abstract:

AbstractContext: Twenty years after the publication of the agile manifesto, agility is becoming more and more popular in different contexts. Agile values are changing the way people work together and influence people’s mindset as well as the culture of organizations. Many organizations have understood that continuous improvement is based on measurement.Objective: The objective of this paper is to present how agility can be measured at the team level. For this reason, we will introduce our questionnaire for measuring agility, which is based on the agile values of the manifesto.Method: We developed a questionnaire comprising 36 items that measure the current state of a team’s agility in six dimensions (communicative, change-affine, iterative, self-organized, product-driven and improvement-oriented). This questionnaire has been evaluated with respect to several expert reviews and in a case study.Results: The questionnaire provides a method for measuring the current state of agility, which takes the individual context of the team into account. Furthermore, our research shows, that this technique enables the user to uncover dysfunctionalities in a team.Conclusion: Practitioners and organizations can use our questionnaire to optimize collaboration within their teams in terms of agility. In particular, the value delivery of an organization can be increased by optimizing collaboration at the team level. The development of this questionnaire is a continuous learning process with the aim to develop a standardized questionnaire for measuring agility.

APA, Harvard, Vancouver, ISO, and other styles

Cline, Alan. "Overview of an Agile Iteration." In Agile Development in the Real World, 141–63. Berkeley, CA: Apress, 2015. http://dx.doi.org/10.1007/978-1-4842-1679-8_8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Kuusinen, Kati. "BoB: A Framework for Organizing Within-Iteration UX Work in Agile Development." In Human–Computer Interaction Series, 205–24. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-32165-3_9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Hughes, Ralph. "Iterative Development in a Nutshell." In Agile Data Warehousing Project Management, 33–79. Elsevier, 2013. http://dx.doi.org/10.1016/b978-0-12-396463-2.00002-8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

"The Agile and Iterative Development Process." In Developing Chemical Information Systems, 26–33. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2006. http://dx.doi.org/10.1002/9780470068793.ch5.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Russo, Barbara, Marco Scotto, Alberto Sillitti, and Giancarlo Succi. "Effort Estimation." In Agile Technologies in Open Source Development, 232–55. IGI Global, 2010. http://dx.doi.org/10.4018/978-1-59904-681-5.ch013.

Full text

Abstract:

As in more traditional development processes also in agile and iterative methodologies, estimation of development effort without imposing overhead on the project and the development team is of paramount importance. This analysis proposes a new effort estimation model aimed at iterative development environments, which are not suitable for description by traditional prediction methods. We propose a detailed development methodology, discuss a number of detailed architectures of such models (including a wealth of augmented regression models and neural networks) and include a thorough case study of XP carried out in two real semi-industrial projects.

APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Agile iterative development"

Ge, Xiaocheng, Richard F. Paige, and John A. McDermid. "An Iterative Approach for Development of Safety-Critical Software and Safety Arguments." In 2010 AGILE Conference. IEEE, 2010. http://dx.doi.org/10.1109/agile.2010.10.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Njegus, Angelina, and Goran Milanov. "Qualitative comparison of agile and iterative software development methodologies." In 2011 19th Telecommunications Forum Telfor (TELFOR). IEEE, 2011. http://dx.doi.org/10.1109/telfor.2011.6143783.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Santos, Nuno, Jaime Pereira, Francisco Morais, Júlio Barros, Nuno Ferreira, and Ricardo J. Machado. "Deriving user stories for distributed scrum teams from iterative refinement of architectural models." In XP '18 Companion: 19th International Conference on Agile Software Development. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3234152.3234165.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Jinzenji, Kumi, Takashi Hoshino, Laurie Williams, and Kenji Takahashi. "Metric-Based Quality Evaluations for Iterative Software Development Approaches Like Agile." In 2012 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW). IEEE, 2012. http://dx.doi.org/10.1109/issrew.2012.40.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Asuncion, Hazeline, David Socha, Kelvin Sung, Scott Berfield, and Wanda Gregory. "Serious game development as an iterative user-centered agile software project." In Proceeding of the 1st international workshop. New York, New York, USA: ACM Press, 2011. http://dx.doi.org/10.1145/1984674.1984690.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Danh Nguyen-Cong and De Tran-Cao. "A review of effort estimation studies in agile, iterative and incremental software development." In 2013 IEEE RIVF International Conference on Computing & Communication Technologies, Research, Innovation, and Vision for the Future (RIVF). IEEE, 2013. http://dx.doi.org/10.1109/rivf.2013.6719861.

Full text

APA, Harvard, Vancouver, ISO, and other styles

"Agile Requirements Engineering: An Empirical Analysis and Evidence from a Tertiary Education Context." In InSITE 2019: Informing Science + IT Education Conferences: Jerusalem. Informing Science Institute, 2019. http://dx.doi.org/10.28945/4287.

Full text

Abstract:

[This Proceedings paper was revised and published in the 2019 issue of the journal Issues in Informing Science and Information Technology, Volume 16] Aim/Purpose: The study describes empirical research into agile Requirements Engineering (RE) practices based on an analysis of data collected in a large higher education organization. Background: Requirements Engineering (RE) in agile development contexts is considerably different than in traditional software development. The field of agile RE is still nascent where there is a need to evaluate its impact in real-world settings. Methodology: Using a case study methodology, the study involved interviewing nine experienced software practitioners who reflected on the use and implementation of various agile RE practices in two software development projects of a student management system. Contribution: The primary contribution of the paper is the evaluation of agile RE practices in a large tertiary educational organization. Based on the analysis of the data, it provides valuable insights into the practice of agile RE in a specific context (i.e., education), but just as importantly, the ones that were omitted or replaced with others and why. Findings: While the evolutionary and iterative approach to defining requirements was followed in general, not all agile practices could be fully adhered to in the case organization. Although face-to-face communication with the customers has been recognized as one the most important agile RE practices, it was one of the most difficult practices to achieve with a large and diverse customer base. Addressing people issues (e.g., resistance to change, thinking, and mindset) was found to be a key driver to following the iterative RE process effectively. Contrary to the value-based approach advocated in the literature, the value-based approach was not strictly adhered to in requirements prioritization. Continuous integration was perceived to be a more beneficial practice than prototyping, as it allows frequent integration of code and facilitates delivering working software when necessary. Recommendations for Practitioners: Our study has important implications for practitioners. Based on our empirical analysis, we provide specific recommendations for effective implementation of agile RE practices. For example, our findings suggest that practitioners could address the challenges associated with limited face-to-face communication challenges by producing flexible, accessible, and electronic documentation to enable communication. Recommendations for Researchers: Researchers can use the identified agile RE practices and their variants to per-form in-depth investigations into agile requirements engineering in other educational contexts. Impact on Society: There are a number of new technologies that offer exciting new opportunities that can be explored to maximize the benefits of agile and other requirements techniques. Future Research: Future research could conduct case studies in different contexts and thus con-tribute to developing bundles or collections of practices to improve software development processes in specific contexts.

APA, Harvard, Vancouver, ISO, and other styles

Bakke, Christine, and Rena Sakai. "Using Design-Based Research to Layer Career-Like Experiences onto Software Development Courses." In InSITE 2022: Informing Science + IT Education Conferences. Informing Science Institute, 2022. http://dx.doi.org/10.28945/4998.

Full text

Abstract:

Aim/Purpose: This research aims to describe layering of career-like experiences over existing curriculum to improve perceived educational value. Background: Feedback from students and regional businesses showed a clear need to in-crease student’s exposure to career-like software development projects. The initial goal was to develop an instructor-optional project that could be used in a single mid-level programming course; however, the pilot quickly morphed into a multi-year study examining the feasibility of agile projects in a variety of settings. Methodology: Over the course of four years, an agile project was honed through repeated Design Based Research (DBR) cycles of design, implementation, testing, communication, and reflective analysis. As is common with DBR, this study did not follow single methodology design; instead, analysis of data coupled with review of literature led to exploration and testing of a variety of methodologies. The review phase of each cycle included examination of best practices and methodologies as determined by analysis of oral and written comments, weekly journals, instructor feedback, and surveys. As a result of participant feedback, the original project was expanded to a second project, which was tested in another Software Engineering (SE) course. The project included review and testing of many academic and professional methodologies, such as Student Ownership of Learning, Flipped Classroom, active learning, waterfall, agile, Scrum, and Kanban. The study was homogenous and quasi-experimental as the population consisted solely of software engineering majors taking required courses; as based on validity of homogenous studies, class sizes were small, ranging from 8 to 20 students. Close interactions between respondents and the instructor pro-vided interview-like settings and immersive data capture in a natural environment. Further, the iterative development practices of DBR cycles, along with the inclusion of participants as active and valued stakeholders, was seen to align well with software development practitioner practices broadly known as agile. Contribution: This study is among the first to examine layering a career-like software development project on top of a course through alteration of traditional delivery, agile development, and without supplanting existing material. Findings: In response to industry recommendations for additional career-like experiences, a standalone agile capstone-like project was designed that could be layered over an existing course. Pilot data reflected positive perceptions of the project, although students did not have enough time to develop a working prototype in addition to completing existing course materials. Participant feedback led to simultaneous development of a second, similar project. DBR examination of both projects resulted in a simplified design and the ability to develop a working prototype, if and only if the instructor was willing to make adjustments to delivery. After four years, a solution was developed that is both stable and flexible. The solution met the original charge in that it required course delivery, not course material, to be adjusted. It is critical to note that when a working prototype is desired, a portion of the lecture should be flipped allowing more time for guided instruction through project-focused active learning and study group requirements. The results support agile for standalone software development projects, as long as passive delivery methods are correspondingly reduced. Recommendations for Practitioners: Based on the findings, implementation of a career-like software development project can be well received as long as active learning components are also developed. Multiple cycles of DBR are recommended if future researchers wish to customize instructional delivery and develop complex software development projects. Programming instructors are recommended to explore hybrid delivery to support development of agile career-like experiences. Small class sizes allowed the researchers to maintain an interview-like setting throughout the study and future studies with larger classes are recommended to include additional subject matter experts such as graduate students as inter-action with a subject matter expert was highly valued by students. Recommendations for Researchers: Researchers are recommended to further examine career-like software development experiences that combine active learning with agile methods; more studies following agile and active learning are needed to address the challenges faced when complex software development is taught in academic settings. Further testing of standalone agile project development has now occurred in medium sized in person classes, online classes, independent studies, and creative works research settings; however, further research is needed. Future re-search should also examine the implementation of agile projects in larger class sizes. Increasing class size should be coupled with additional subject matter experts such as graduate students. Impact on Society: This study addresses professional recommendations for development of agile career-like experiences at the undergraduate level. This study provides empirical evidence of programming projects that can be layered over existing curriculum, with no additional cost to the students. Initial feedback from local businesses and graduates, regarding agile projects with active learning, has been positive. The area business that refused to hire our underprepared SE graduates has now hired several. Future Research: Future research should explore layering agile projects over a broader range of software development courses. Feedback from hiring professionals and former students has been positive. It is also recommended that DBR be used to develop career-like experiences for online programming courses.

APA, Harvard, Vancouver, ISO, and other styles

Sakai, Rena, and Christine Bakke. "Student Ownership of Learning: A Student’s Experience." In InSITE 2022: Informing Science + IT Education Conferences. Informing Science Institute, 2022. http://dx.doi.org/10.28945/4992.

Full text

Abstract:

Aim/Purpose: This study reports the outcome of Student Ownership of Learning (SOL) through developing a shopping application. This research aims to describe embedding agile career-like experiences into software development courses in order to improve perceived educational value. Background: Many classes consist of lectures, homework, and tests; however, most students do not remember what they learn through passive instruction. The re-searchers of this study believe that SOL and Scrum can be combined to guide students as they take an active and leading role in their learning. Methodology: This study implemented SOL and Scrum to promote learning through teacher and student collaboration. Iterative development of an ill-defined and complex software project progressed through goal setting, task determination, prioritization, and timeboxing. Following Scrum, the complex project was first broken down into small units. The development followed short periods of independent work followed by meetings; each timeboxed development cycle is modeled after a Scrum sprint. Weekly instructor-student meetings emphasized planning and reflection through code review, discussions of progress and challenges, and prioritization for the next iteration. The project followed the agile philosophy of soft-ware development flow through iterative development rather than focusing on a defined end date. Contribution: This study provides a practical guide for successful student learning based on SOL and Scrum through project details such as project successes and iterative challenges. Findings: This study found that SOL, when combined with Scrum, can be used to provide a career-like software development experience. Student perceptions reflect regular interactions with a subject matter expert for the development of a complex software project increased willingness to learn, helped clarify goals, and advanced development of independent programming skills. Recommendations for Practitioners: Practitioners can share this research with faculty members from different faculties to develop the best solutions for SOL using Scrum. Recommendations for Researchers: Researchers are encouraged to explore different disciplines and different perspectives where SOL and Scrum methods might be implemented to increase active learning through teamwork or project-based learning. Impact on Society: This study is beneficial for creating or redesigning a course to include career-like experiences. Readers can understand that the high level of engagement and achievement achieved through SOL and Scrum are the driving forces for project success. Future Research: Practitioners and researchers can expand the current body of knowledge through further exploration of Scrum and SOL in educational settings where the emulation of real career experiences is desired. Future research examining best practices, tools, and methods for embedding complex software development projects into programming courses would benefit instructional faculty in many technical disciplines.

APA, Harvard, Vancouver, ISO, and other styles

Junior, Gerson, João Amaral, Patrícia Matsubara, and Valdemar Neto. "Influences of Organizational Culture in the Adoption of Agile Methodologies in Information Systems Development A Systematic Mapping." In XI Simpósio Brasileiro de Sistemas de Informação. Sociedade Brasileira de Computação, 2015. http://dx.doi.org/10.5753/sbsi.2015.5821.

Full text

Abstract:

Information Systems (IS) industry has been pressured to deliver software products under reduced time-to-market and restrict budget. Agile Methodologies (AM) have been adopted to meet those aforementioned needs by the adoption of self-managing teams, iterative development cycles, fast delivery, and focus on functional software. Adoption of AM requires a suitable organizational environment, with significant changes in the employees’ behavior and in the working processes, impacting, and suffering the impact of Organizational Culture (OC). In this direction, methods, actions, and policies must be thought to align the company’s OC to the use of AM, in such a way that both can benefit each other. However, there is a lack of proposals that systematically investigate how to align both OC and AM. In this sense, a systematic mapping study (SMS) was conducted to identify studies that associate OC in initiatives of AM adoption. This paper presents the state-of-the-art about the influence of OC in the adoption of AM. The main contribution of this paper is bringing up an overview of the area, indicating perspectives of research, and exposing (i) a list of actions which have been reported to align OC and AM; (ii) OC factors recognized as essential to the successful adoption of AM; and (iii) the perceptions on a lack of awareness about the influence of OC in IT organizations.

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!