To see the other types of publications on this topic, follow the link: Agile iterative development.
Journal articles on the topic 'Agile iterative development'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 journal articles for your research 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.
Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.
1
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 textAbstract:
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.
2
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
3
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 textAbstract:
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.
4
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 textAbstract:
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.
5
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
6
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 textAbstract:
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.
7
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 textAbstract:
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.
8
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 textAbstract:
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.
9
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 textAbstract:
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.
10
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 textAbstract:
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.
11
Nawaz, Marriam, Tahira Nazir, Seema Islam, Momina Masood, Awais Mehmood, and Samira Kanwal. "Agile Software Development Techniques: A Survey." Proceedings of the Pakistan Academy of Sciences: A. Physical and Computational Sciences 58, no. 1 (September 1, 2021): 17–33. http://dx.doi.org/10.53560/ppasa(58-1)721.
Full textAbstract:
In this IT era, where there is a race of software development, it is necessary to introduce such types of software development techniques which will help the practitioners to deliver fast solutions. In the past, various traditional approaches were used for this purpose, but now agile techniques are getting more popular because conventional software development approaches are not efficient in managing the changing requirements. The agile software development process is one of the most emerging lightweight software development methodologies, which uses iterative and prototype development approaches to accommodate changes in software requirements. Final software products are delivered to the end-users in short iterations. One of the most noticeable drawbacks of agile methods is their limited courtesy to the structured and architectural design of the system. Hence this development approach will restrict small to medium design decisions only. In this paper, we have performed the analysis of different agile techniques, which will help the readers to understand their positive and negative points and select the most appropriate technique suited to their projects.
12
Sharma, Poorti. "Impact of Agile Methodologies in Project Success." International Journal for Research in Applied Science and Engineering Technology 10, no. 5 (May 31, 2022): 3728–30. http://dx.doi.org/10.22214/ijraset.2022.43204.
Full textAbstract:
Abstract: The Agile Manisfesto of software development put forth a groundbreaking mindset on delivering value and collaborating with customers when it was created in 2001. Agile methodology that utilizes iterative development and prototyping are vitally used in variety of industry projects as a light weight development method which can satisfy to changes of requirements. Traditional waterfall approach is not much efficient to manage the rapid change in requirements. The purpose of this study is to present the impacts of agile methodology in project success. Most studies have reported that when comparing structured methodologies with agile methodologies, agile does improve software quality, other studies have contradicted and questioned the claimed benefits , while others argued that there is not enough empirical evidence. This study aims at investigating the impact that agile method on project success in an organization. The selected studies were published between 2018 to 2022. Index Terms: Agile methodology, agile practices, impact of agile, project success
13
Alrabaiah, Hazem Abdelkarim, and Nuria Medina-Medina. "Agile Beeswax: Mobile App Development Process and Empirical Study in Real Environment." Sustainability 13, no. 4 (February 10, 2021): 1909. http://dx.doi.org/10.3390/su13041909.
Full textAbstract:
Mobile application development is a highly competitive environment; agile methodologies can enable teams to provide value faster, with higher quality and predictability, and a better attitude to deal with the continuous changes that will arise in the mobile context application (App), and the positive impact of that on sustainable development through continuous progress. App development is different from other types of software. For this reason, our objective is to present a new agile-based methodology for app development that we call Agile Beeswax. Agile Beeswax is conceived after identifying the mobile development process’s issues and challenges, and unique requirements. Agile Beeswax is an incremental, iterative development process composed of two main iterative loops (sprints), the incremental design loop and the incremental development loop, and one bridge connecting these two sprints. Agile Beeswax is structured in six phases, idea and strategy, user experience design, user interface design, design to development, handoff and technical decisions, development, and deployment and monitoring. One of its main strengths is that it has been created with academic and business perspectives to bring these two communities closer. To achieve this purpose, our research methodology comprises four main phases: Phase 1: Extensive literature review of mobile development methodologies, Phase 2: Interviews with mobile application developers working in small to medium software companies, Phase 3: Survey to extract valuable knowledge about mobile development (which was carefully designed based on the results of the first and the second phases), and Phase 4: Proposal of a new methodology for the agile development of mobile applications. With the aim of integrating both perspectives, the survey was answered by a sample of 35 experts, including academics and developers. Interesting results have been collected and discussed in this paper (on issues such as the development process, the tools used during this process, and the general issues and challenges they encountered), laying the foundations of the methodology Agile Beeswax proposed to develop mobile apps. Our results and the proposed methodology are intended to serve as support for mobile application developers.
14
Fulbright, Ron. "Incorporating Innovation into Iterative Software Development Using the Inventive Problem Solving Methodology." International Journal of Innovation Science 5, no. 4 (December 1, 2013): 203–12. http://dx.doi.org/10.1260/1757-2223.5.4.203.
Full textAbstract:
Iterative software methodologies allow development teams to be agile in their response to changing requirements. However, the software development team is usually at the mercy of requirements changes, rather than being part of the project engineering staff defining the changes to the solution architecture. Therefore, projects tend to implement inferior solutions. Integrating a project-level innovation technique called Inventive Problem Solving into agile software development methodologies such as the spiral model, the Rational Unified Process, and Scrum, allows the development team to affect the overall solution architecture utilizing their expertise in information technology to the maximum benefit. As a result, more creative, innovative, and efficient solutions to the problem are conceived and implemented.
15
Galli, Brian J. "The Value of Communication Management in Agile Project Environments." International Journal of Applied Logistics 12, no. 1 (January 1, 2022): 1–21. http://dx.doi.org/10.4018/ijal.309089.
Full textAbstract:
In today's business environment, a less agile way of working is no longer a business choice. Implementing the agile method is not for fashion and not for keeping up with the “newest and greatest” trend. Without the agile method, it is difficult to implement any other strategic initiatives, such as digital transformation. Agile development focuses on the evolution of user needs and then uses a step-by-step approach as well as an iterative approach to software development. This paper finds that communication is vital in agile project management. The author puts forward some opinions on the communication management of agile projects, including the establishment of the information portal and agile communication matrix. Additionally, a literature review is performed to illustrate how certain variables, concepts, and models can assist in project management. This study takes a design-science-investigate approach to assess pre-existing literature.
16
Ozornin, S. Yu, and N. G. Terlyga. "DEVELOPMENT OF A CUSTOMIZED AGILE PROJECT MANAGEMENT MODEL." Quality. Innovation. Education, no. 1 (2022): 42–61. http://dx.doi.org/10.31145/1999-513x-2022-1-42-61.
Full textAbstract:
The transition of the domestic economy to the digital path of development has determined the need to change the models of project management. An analysis of the applicability of agile project management showed the presence of bottlenecks in the Russian markets and created the need to develop an adapted approach that takes into account the peculiarities of the domestic digital economy. The methods of analysis, symbiosis, modeling and visualization served as the basis for the development of an adapted model of agile project management in the digital economy. As a result of applying the methods, a symbiotic constraint model was developed that takes into account the limitations of the tripartite approach and supplements it with the provisions of the Agile concept. On the basis of symbiosis, a agile project management model has been developed, consisting of 8 subsystems declared in the seventh version of the PMBoK. The model is based on the principles of iterative development characteristic of the Agile approach, and also takes into account the key provisions of traditional project management through the introduction of operations of initial planning and control of compliance with constraints. The developed model can be used as a project management tool at domestic enterprises in information technology sphere.
17
Shahzeb Hussain, Namrata Bhadri, and Syed Razauddin Shahlal. "Factors Influencing the Efficacy of Agile Usage." International Journal of Engineering and Management Research 10, no. 5 (October 5, 2020): 1–4. http://dx.doi.org/10.31033/ijemr.10.5.1.
Full textAbstract:
Agile techniques that utilize iterative development are broadly used in various industry projects as a lightweight development technique which can satisfy the continuous changes of requirements. Short repetitions are used that are required for efficient product delivery. Traditional and old software development methods are not much efficient and effective to control the rapid change in requirements. Despite the benefits of Agile, criticism on agile methodology states that it couldn’t succeed to pay attention to architectural and design issues and therefore is bound to produce small design-decisions. The past decade has observed numerous changes in systems development with many organizations accepting agile techniques as a viable methodology for developing systems. An increase in the number of research studies reveals the growing demand and acceptance of agile methodologies. While most research has focused on acceptance rate and adaptation of agile practices, there is very limited knowledge of their post-adoption usage and incorporation within organizations. Several factors explain the effective usage of agile methodologies. A combination of previous research in Agile Methodologies, Diffusion of Innovations, Information Systems implementation, and Systems Development has been carried out to develop a research model that identifies the main factors relevant to the propagation and effective usage of agile methodologies in organizations.
18
Ribeiro, Artur Tavares Vilas Boas, Lorenna Fernandes Leal, Guilherme Soares Gurgel do Amaral, Ricardo Kahn, Bruno Guilherme Pacci Evaristo, Victor Romão, G. Altmann Ricardo, et al. "Agile Product Development: Features Identification and Application in the Electricity Sector." Proceedings of the Design Society: International Conference on Engineering Design 1, no. 1 (July 2019): 2149–58. http://dx.doi.org/10.1017/dsi.2019.221.
Full textAbstract:
AbstractThe electricity sector is in the midst of a structural change driven by new technologies. In Brazil, the electricity sector regulation has mechanisms to foster innovation, including investments in R&D. Recently, the regulatory agency and the industry have been calling for approaches to increase the rate at which R&D departments generate solutions that end up being adopted. As a result, novel approaches to R&D project management have entered the agenda. In this context, the objective of this paper is to characterise Agile Product Development and its application in a highly regulated sector. The paper presents a systematic literature review with the debates about Agile and new product development. Then, a case study exploring an early adoption of the Agile approach in R&D project management in the Brazilian electricity sector is presented. Results include the identification of the Agile features most frequently mentioned in the literature. Moreover, the case study explores the Agile features that were more easily absorbed in early adoption, such as iterative patterns, and discusses implementation challenges in team structure, feedback loops, and communication.
19
Kasurinen, Jussi, and Kari Smolander. "Defining an Iterative ISO/IEC 29110 Deployment Package for Game Developers." International Journal of Information Technologies and Systems Approach 10, no. 1 (January 2017): 107–25. http://dx.doi.org/10.4018/ijitsa.2017010106.
Full textAbstract:
Software development in a small development team is a challenge, as people have to fulfill several roles, which in larger groups would have dedicated people. To help in this aspect, the ISO/IEC 29110 Lifecycle profiles for Very Small Entities has been developed to help organization and manage the workflow. However, the model presented in the ISO/IEC 29110 is rather abstract, and prominently follows the waterfall approach, even though the documents do amend agile practices as one acceptable approach. In game development this loosely defined approach is problematic, since games industry heavily relies in the agile practices with short cycles of iterations. In this article, the authors present their study of game development organizations, and describe the ISO/IEC 29110 deployment package “Highly Iterative Software Processes” which combines the Entry level model with the industry-specific requirements. In general, the definition of support for the iterative development makes the model feasible for the industry.
20
Astuti, Nur Rochmah Dyah Puji, Nuril Anwar, and Muhammad Bayu Aji Sakirno. "Pengembangan Sistem Mata Kuliah Manajemen Proyek Teknologi Informasi dengan Metode Agile." Building of Informatics, Technology and Science (BITS) 3, no. 3 (December 31, 2021): 361–68. http://dx.doi.org/10.47065/bits.v3i3.1104.
Full textAbstract:
The work course at Ahmad Dahlan University's Informatics Engineering is a course that aims for students to go directly or get projects related to technology development. One of the creative courses that students must take in semester 6 is Information Technology Project Management (MPTI), where the course is conducted in groups. Processing of final grades from MPTI courses from 3 components, namely supervisors, examiners and industry supervisors (partners). Because the value components are from various sources, a system is needed to process all processes from registration to processing the final value. The agile development method is a development method that prioritizes input from partners as users, besides that the agile method has advantages including fast, adaptive, iterative. The model used in system development in agile is the Dynamic Systems Development Method. Data collection was done by literature study, observation, and interviews. The system development stage using an iterative model includes the needs analysis stage, the design stage, the implementation stage, the testing stage, and the evaluation stage. Implementation using the PHP programming language and the Laravel framework. Testing is done black box test. The results of the research produced an information system and tested. Tests carried out using a black box test which resulted in 82,76%
21
Sahraoui, Sofiane, Noor Al-Nahas, and Rania Suleiman. "An Agile Perspective on Open Source Software Engineering." International Journal of Open Source Software and Processes 4, no. 3 (July 2012): 52–65. http://dx.doi.org/10.4018/ijossp.2012070105.
Full textAbstract:
Open source software (OSS) development has been a trend parallel to that of agile software development, which is the highly iterative development model following conventional software engineering principles. Striking similarities exist between the two development processes as they seem to follow the same generic phases of software development. Both modes of development have less emphasis on planning and design and a more prominent role for implementation during the software engineering process. This article expounds on this connection by adopting an agile perspective on OSS development to emphasize the similarities and dissimilarities between the two models. An attempt is first made to show how OSS development fits into the generic agile development framework. Then, the article demonstrates how the development process of Mozilla and Apache as two of the most famous OSS projects can be recast within this framework. The similarity discussed and illustrated between agile and OSS development modes is rather limited to the mechanics of the development processes and do not include the philosophies and motivations behind development.
22
Salehi, Vahid, and Shirui Wang. "Munich Agile MBSE Concept (MAGIC)." Proceedings of the Design Society: International Conference on Engineering Design 1, no. 1 (July 2019): 3701–10. http://dx.doi.org/10.1017/dsi.2019.377.
Full textAbstract:
AbstractModel-based systems engineering (MBSE) is well-known in gaining the control over the complexity of systems and the development processes, while agile is a project management methodology originally from software development that uses short development cycles to focus on continuous improvement in the development of a product or service. In this paper, we adopt the concept of agile into MBSE and then proposed the new approach - Munich Agile MBSE Concept (MAGIC). The highlights of the MAGIC approach can be concluded as 1) the requirements which have been defined in the first stage will be examined and traced at each following stages; 2) communication between every 2 stages always exists in order to have a close connection during each system development phase; 3) the idea of Industry 4.0 has been included and reflected to achieve automation and data exchange with manufacturing technologies; 4) the concept of IOT (Internet of Things) is also considered when it comes to the usage and service of the system to satisfy the customer's needs; 5) the whole spirit of agile is reflected as the iterative and incremental design and development
23
Pilco, Hennry, Sandra Sanchez-Gordon, Tania Calle-Jimenez, Jorge Pérez-Medina, Yves Rybarczyk, Janio Jadán-Guerrero, César Maldonado, and Isabel Nunes. "An Agile Approach to Improve the Usability of a Physical Telerehabilitation Platform." Applied Sciences 9, no. 3 (January 30, 2019): 480. http://dx.doi.org/10.3390/app9030480.
Full textAbstract:
The goal of a telerehabilitation platform is to safely and securely facilitate the rehabilitation of patients through the use of telecommunication technologies complemented with the use of biomedical smart sensors. The purpose of this study was to perform a usability evaluation of a telerehabilitation platform. To improve the level of usability, the researchers developed and proposed an iterative process. The platform uses a digital representation of the patient which duplicates the therapeutic exercise being executed by the patient; this is detected by a Kinect camera and sensors in real time. This study used inspection methods to perform a usability evaluation of an exploratory prototype of a telerehabilitation platform. In addition, a cognitive workload assessment was performed to complement the usability evaluation. Users were involved through all the stages of the iterative refinement process. Usability issues were progressively reduced from the first iteration to the fourth iteration according to improvements which were developed and applied by the experts. Usability issues originally cataloged as catastrophic were reduced to zero, major usability problems were reduced to ten (2.75%) and minor usability problems were decreased to 141 (38.74%). This study also intends to serve as a guide to improve the usability of e-Health systems in alignment with the software development cycle.
24
Sohail, Fizzah, Syed Saood Zia, Rehan Qureshi, Muhammad Naseem, and Hira Haider. "Impact of Agile Methodology on Software Development Life Cycle." Pakistan Journal of Engineering and Technology 4, no. 2 (June 30, 2021): 153–58. http://dx.doi.org/10.51846/vol4iss2pp153-158.
Full textAbstract:
Software engineering strategies had been hired for decades to create software products. The most challenging task for the development of software is to select appropriate software development methodologies. Software developers use agile techniques to reduce the problems faced by the traditional waterfall process. These days, the motivation behind most programming associations is to give programming in a fast time, inside financial plan and changing situations that propelled the conveyance of Agile. The strategy that utilizes iterative expansion and prototyping is generally utilized in an assortment of industry ventures as a lightweight advancement method that could fulfil the alterations of necessities. Short cycles are utilized which can be required for proficient item delivery. In the paper, we become mindful of the impacts that the coordinated strategy has programming improvement strategies with prominence to decent inside the authoritative, efficient, and social system. Coordinated methods are not in every case great, they have a few restrictions too. In this paper, we likewise clarify the estimations of Agile, its points of interest, and its weaknesses.
25
Bergs, Thomas, Sebastian Apelt, Alexander Beckers, and Sebastian Barth. "Agile ramp-up production as an advantage of highly iterative product development." Manufacturing Letters 27 (January 2021): 4–7. http://dx.doi.org/10.1016/j.mfglet.2020.09.010.
Full text
26
Munetoh, Seiji, and Nobukazu Yoshioka. "Method Using Command Abstraction Library for Iterative Testing Security of Web Applications." International Journal of Secure Software Engineering 6, no. 3 (July 2015): 26–49. http://dx.doi.org/10.4018/ijsse.2015070102.
Full textAbstract:
A framework based on a scripting language is commonly used in Web application development, and high development efficiency is often achieved by applying several Agile development techniques. However, the adaptation of security assurance techniques to support Agile development is still underway, particularly from the developer's perspective. The authors have addressed this problem by developing an iterative security testing method that splits the security test target application into two parts on the basis of the code lifecycle, application logic (“active development code”) and framework (“used code”). For the former, detailed security testing is conducted using static analysis since it contains code that is changed during the iterative development process. For the latter, an abstraction library at the command granularity level is created and maintained. The library identifies the behavior of an application from the security assurance standpoint. This separation reduces the amount of code to be statically inspected and provides a mechanism for sharing security issues among application developers using the same Web application framework. Evaluation demonstrated that this method can detect various types of Web application vulnerabilities.
27
Chehili, Hamza, Lionel Seinturier, and Mahmoud Boufaida. "An Evolutive Component-Based Method for Agile Development of Service Oriented Architectures." International Journal of Information Systems in the Service Sector 9, no. 3 (July 2017): 37–57. http://dx.doi.org/10.4018/ijisss.2017070103.
Full textAbstract:
The adoption of the agile methods' principles has emerged as an effective way to develop service oriented architectures as it paves the way for a better reply to the changing needs of the environment and even the customer. However, these changes may also require the evolution of the development process itself. This paper presents an agile and service-oriented software development method that combines concepts from the Service-Oriented Computing (SOC) domain and the agile software engineering one. This method provides an iterative and incremental process to deliverer business processes, implemented as an assembly of components. This leads to a faster response to the change of needs by reconfiguring the assembly of components. The method is based on a framework that implements its phases as an assembly of components to allow a dynamic reconfiguration of it in case of a development process evolution. Finally, a case study is presented to illustrate the use of the presented method.
28
Thomas, Meetu, and Mali Senapathi. "Agile Requirements Engineering: An Empirical Analysis and Evidence from a Tertiary Education Context." Issues in Informing Science and Information Technology 16 (2019): 097–112. http://dx.doi.org/10.28945/4286.
Full textAbstract:
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.
29
Prakash, B., and V. Viswanathan. "A Survey on Software Estimation Techniques in Traditional and Agile Development Models." Indonesian Journal of Electrical Engineering and Computer Science 7, no. 3 (September 1, 2017): 867. http://dx.doi.org/10.11591/ijeecs.v7.i3.pp867-876.
Full textAbstract:
<p>Software projects mostly exceeds budget, delivered late and does not meet with the customer’s satisfaction for years. In the past, many traditional development models like waterfall, spiral, iterative, and prototyping methods are used to build the software systems. In recent years, agile models are widely used in developing the software products. The major reasons are – simplicity, incorporating the requirement changes at any time, light-weight approach and delivering the working product early and in short duration. Whatever the development model used, it still remains a challenge for software engineer’s to accurately estimate the size, effort and the time required for developing the software system. This survey focuses on the existing estimation models used in traditional as well in agile software development.</p>
30
Hansen, C. A., R. Arlitt, T. Eifler, and M. Deininger. "Design by Prototyping: Increasing Agility in Mechatronic Product Design through Prototyping Sprints." Proceedings of the Design Society 2 (May 2022): 201–10. http://dx.doi.org/10.1017/pds.2022.22.
Full textAbstract:
AbstractThis paper adapts the agile scrum sprint, typically used in software development, to a prototyping sprint for mechatronic product design. The Design by Prototyping framework describes how the prototyping sprint can be used to manage the prototyping process in design projects through an agile-stage-gate hybrid model. A comparison of 18 student projects using either prototyping sprints or a traditional iterative prototyping approach shows that prototyping sprints helped students make more deliberate, strategic decisions about their use of prototypes.
31
Parsons, David, and Rosemary Stockdale. "A Virtual World Workshop Environment for Learning Agile Software Development Techniques." International Journal of Virtual and Personal Learning Environments 3, no. 1 (January 2012): 37–54. http://dx.doi.org/10.4018/jvple.2012010103.
Full textAbstract:
Multi-User Virtual Environments (MUVEs) are the subject of increasing interest for educators and trainers. This article reports on a longitudinal project that seeks to establish a virtual agile software development workshop hosted in the Open Wonderland MUVE, designed to help learners to understand the basic principles of some core agile software development techniques. The authors take a design-based research approach that allows for cycles of learning and reflection that has enabled following an iterative path of development through two major iterations. The authors trace the research path followed from the real world workshop to its virtual incarnation, describing the design philosophy and the constructed virtual artefacts. The authors conclude by reflecting on the insights into learner perceptions and practical implementations gained from building and evaluating the virtual workshop.
32
Shafiq, Shagufta, Yaser Hafeez, Sadia Ali, Naila Iqbal, and Muhammad Jamal. "Towards Scrum Based Agile Framework for Global Software Development Teams." Mehran University Research Journal of Engineering and Technology 38, no. 4 (October 1, 2019): 979–98. http://dx.doi.org/10.22581/muet1982.1904.11.
Full textAbstract:
Organizations are moving their workforce to guarantee matters of trade and profit where accounts are expected to be less expensive and provide better quality products with the accessibility of skilled labor. With the evident benefits, distributed teams often face challenges with reliable and efficient communication coordination patterns that lead towards project failure. In the rapidly growing software industry, it becomes critical for any business to have better management activities to acquire right processes and practices. Agile methods are considered as a remedy for mitigating distributed teams’ challenges, with their consistent focus on communication. Here, we intend to propose a tailored Scrum based solution for distributed teams that empowers anticipated communication and coordination throughout the development process. In the first phase of framework development we have evaluated the state of agile practices from both literature and industry; based on collected evidence and suggestive guidelines a scrum based agile framework was formulated. The Scrum is a project management method in Agile Methods family. Scrum is an iterative process that asks for incremental development of the product, includes cross functional development and testing teams. Evaluation results show that the proposed framework contributes positively to improve development process quality. We have performed theoretical as well as empirical evaluation to validate proposed framework. We have eight project managing rising aspects in DSD (Distributed Software Development) to evaluate the proposed framework.
33
Cano, Sandra P., Carina S. González, César A. Collazos, Jaime Muñoz Arteaga, and Sergio Zapata. "Agile Software Development Process Applied to the Serious Games Development for Children from 7 to 10 Years Old." International Journal of Information Technologies and Systems Approach 8, no. 2 (July 2015): 64–79. http://dx.doi.org/10.4018/ijitsa.2015070105.
Full textAbstract:
The development of video games is a complex, multidisciplinary process, which involves different areas as well as a greater number of roles than for traditional software. Serious games face process constraints that concern a number of interactive, educational and psychological factors designed to lead to the fulfillment of educational objectives within a specific context. Based on a case study in the city Cali, Colombia, an iterative and incremental process is proposed, focusing on small and medium development for educational serious games and basing itself on two lines of research: agile development methodology and user-centered design (UCD) for children from 7 to 10 years. The agile methodology eXtreme Programming (XP) offers a useful option for the development of serious games as it establishes a continuous communication with all project stakeholders - including the end user - throughout the project, while UCD allows the user profile to be known and identified so that the game will meet the needs and match the capabilities, expectations and motivations of the child.
34
Jaggars, Damon, and DeEtta Jones. "An agile planning and operations framework." Performance Measurement and Metrics 19, no. 2 (July 9, 2018): 121–26. http://dx.doi.org/10.1108/pmm-11-2017-0057.
Full textAbstract:
Purpose The purpose of this paper is to describe the design and implementation of an agile planning and operations framework for an academic research library, designed to facilitate an ongoing organizational conversation about the organization’s strategic intent and how it plans to move from intention to reality. The goals motivating the implementation of such a framework include creating iterative, open-ended planning and management processes that enable increased flexibility and openness to unforeseen opportunities, as well as the ongoing integration of library faculty, staff, and external stakeholder voices into planning, management, and assessment discussions. Design/methodology/approach The framework seeks to harmonize planning, management, and assessment processes over 18-24-month rolling time horizons, during which organizational efforts and investments would be reviewed and revised in an iterative fashion. Findings The authors share results and analyses from stakeholder assessments used to develop foundational mission, vision, values, and strategic directions documentation and discuss the structural, cultural, and organizational development challenges confronted and gains experienced in implementing the framework. Originality/value Many academic libraries are exploring new approaches to strategic planning, ways to enhance organizational health, and manage change. The authors are unaware of an academic or research library that has attempted to design and implement a similar approach to strategic planning and its assessment. The agile planning framework provides an alternative to traditional “waterfall” approaches to strategic planning for libraries.
35
Ficco, Massimo, Roberto Pietrantuono, and Stefano Russo. "Bug Localization in Test-Driven Development." Advances in Software Engineering 2011 (June 15, 2011): 1–18. http://dx.doi.org/10.1155/2011/492757.
Full textAbstract:
Software development teams that use agile methodologies are increasingly adopting the test-driven development practice (TDD). TDD allows to produce software by iterative and incremental work cycle, and with a strict control over the process, favouring an early detection of bugs. However, when applied to large and complex systems, TDD benefits are not so obvious; manually locating and fixing bugs introduced during the iterative development steps is a nontrivial task. In such systems, the propagation chains following the bugs activation can be unacceptably long and intricate, and the size of the code to be analyzed is often too large. In this paper, a bug localization technique specifically tailored to TDD is presented. The technique is embedded in the TDD cycle, and it aims to improve developers' ability to locate bugs as soon as possible. It is implemented in a tool and experimentally evaluated on newly developed Java programs.
36
Popa, O., C. Mihele, C. Făgărăşan, and A. Pîslă. "Leadership approach towards Agile, Waterfall and Iterative implementation of the software development products." IOP Conference Series: Materials Science and Engineering 1169, no. 1 (August 1, 2021): 012017. http://dx.doi.org/10.1088/1757-899x/1169/1/012017.
Full text
37
Lesser, Eric, and Linda Ban. "How leading companies practice software development and delivery to achieve a competitive edge." Strategy & Leadership 44, no. 1 (January 18, 2016): 41–47. http://dx.doi.org/10.1108/sl-11-2015-0083.
Full textAbstract:
Purpose – Increasingly companies recognize that effective and rapid software development – from ideation to delivery – is crucial to achieving competitiveness. This article looks at how leading companies are establishing an enterprise capability for accelerated software delivery to differentiate themselves in the market. Design/methodology/approach – This research looks at how leading software organizations focus on software investments that efficiently and speedily deliver marketplace results. Findings – Successful companies build comprehensive skills in Agile and lean software development methods and for fostering extensive collaboration among business users, IT professionals and customers throughout the software development and delivery lifecycle. Practical implications – Advanced organizations are more likely to apply more mature development practices, such as service-oriented architecture (SOA) and Agile iterative development methods. Originality/value – Advanced organizations collaborate much more with customers and business partners to improve software development outcomes.
38
Ahmad, Imam, Rohmat Indra Borman, Jafar Fakhrurozi, and Gavan Gorbi Caksana. "Software Development Dengan Extreme Programming (XP) Pada Aplikasi Deteksi Kemiripan Judul Skripsi Berbasis Android." INOVTEK Polbeng - Seri Informatika 5, no. 2 (November 27, 2020): 297. http://dx.doi.org/10.35314/isi.v5i2.1654.
Full textAbstract:
To determine the topic or research title for the student's thesis, it is possible that the similarity of the title to the previous title, either accidentally or unintentionally. Therefore, the relevant section must check the titles submitted by students, so as to avoid plagiarism. The development of a thesis title similarity detection application is one of the efforts that can be made in solving this problem. The development of sosftware requires the right method to develop applications according to user needs. Extreme Programming (XP) is a part of the agile development approach based on iterative development, which is based on needs and solutions through collaboration among the development team. So, in this study, the development of a similarity detection application for the title of a thesis with the XP software development approach was carried out. Keywords - agile development, extreme programming, thesis
39
Elshandidy, Heba, and Sherif Mazen. "A Survey of Agile and Traditional Requirements Engineering." International Journal of Scientific & Engineering Research 4, no. 9 (September 25, 2013): 473–82. http://dx.doi.org/10.14299/ijser.2013.09.002.
Full textAbstract:
In the past few years, there has been an increasing awareness of the important role of requirements engineering (RE) in a project’s success, in both research and industry. Developing consistent requirements specifications that meet the customers’ needs, in traditional development, is likely to be infeasible. For one reason, customers do not usually have a clear picture of what they really want. Secondly, the business domain could be changing quickly, especially if it heavily depends on technologies. Agile software development (ASD), on the other hand, supports iterative and incremental development and emphasises customers’ involvement in the development process. We argue that adopting ASD in RE overcomes the limitations of the traditional development. ASD, however, is no silver bullet and its adoption comes at a price. This paper helps the reader to: (1) get a quick yet a comprehensive grasp of RE in traditional and ASD; (2) understand the synergies/commonalities between the two approaches in handling RE; (3) recognise the associated challenges of adopting ASD; and (4) identify the current prominent agile RE research areas.
40
Pawar, Rupali Pravinkumar, and Kirti Nilesh Mahajan. "Implementation of Change Management in Software Development by using Scrum Framework." International Journal of Advanced Research in Computer Science and Software Engineering 7, no. 7 (July 30, 2017): 400. http://dx.doi.org/10.23956/ijarcsse.v7i7.164.
Full textAbstract:
This paper will focus on implementation of change management in Scrum software development framework . Scrum is one of the mostly used software development framework from the Agile software development methodology. Scrum is based on iterative and incremental process. It is suitable for unstable requirements. The use of Scrum proved to be beneficial due to tight schedule and loosely defined user requirements that often changed during the development. The aim of the paper to study implementation process of change management in Scrum . First part of paper gives detailed information of Scrum framework. The middle of the paper presented the organizational process of agile software development using Scrum. Finally, the paper point out key points for managing changes in Scrum implementation. The primary data collection method was interviews of the industry expertise. The secondary source of data is reference books and Internet articles. This paper will help to understand basics of Scrum software development framework and process of change management in developing projects by using Scrum framework.
41
Vega, Florencia, Guillermo Rodríguez, Fabio Rocha, and Rodrigo Pereira dos Santos. "Scrum Watch: a tool for monitoring the performance of Scrum-based work teams." JUCS - Journal of Universal Computer Science 28, no. 1 (January 28, 2022): 98–117. http://dx.doi.org/10.3897/jucs.67593.
Full textAbstract:
Agile Methods propose an approach for developing software based on an iterative and incremental life cycle model, in which needs and solutions evolve through collaboration between multi-functional and self-organized teams. As such, agile practices in work teams are gaining much momentum. To meet the demanding level of projects, agile software development also has to keep up with several challenges. In this context, software industry has chosen to use several tools to ease development and communication between different teams’ members. However, these tools generate overwhelming volumes of data that hamper decision-making by project managers. To address this issue, we present Scrum Watch, a tool-based approach that focuses on generating, through cloud-based technologies, graphic elements and reports that assist project managers with information to support decision making. Results obtained from an undergraduate Systems Engineering course through a capstone project confirm the feasibility of the proposed approach, which exploits the benefits of the availability and visualization of process and product metrics.
42
Plotnikov, Andrei V., and Sergei A. Elkin. "APPLYING CLASSICAL MANAGEMENT KEYNOTES OF ORGANISATIONAL BEHAVIOUR IN AGILE MANAGEMENT APPROACHES." Krasnoyarsk Science 11, no. 4 (December 29, 2022): 52–66. http://dx.doi.org/10.12731/2070-7568-2022-11-4-52-66.
Full textAbstract:
This paper analyzes the works of management classics such as Russell Ackoff, Nancy Adler, Frederick Herzberg, Chris Argyris, Bennis Warren, Lyndall Urwick, experts of Aston Group, and others. A common bond between them is organizational behavior and the fact that their work was written in the last century and that elements of their theories were the basis for the neoclassical management theories that predominate today.
Purpose. The aim is to identify commonalities with the iterative-incremental (agile) approach to development and management from classical management theories.
Methodology. The paper analyses classical management papers in organizational behavior and leadership theory to identify commonalities with the iterative-incremental approach to management. The two categories are considered holistically, as leadership can determine organizational behavior. The paper applies ontological and integrated approaches.
Results. The paper identifies standard features of classical theories and agile approaches to management. It indicates that classical approaches to management have formed the basis of agile approaches to management.
Practical implications. The results apply to social management and organizational psychology scholars. In addition, the results will help to scientists write textbooks and manuals on management theory and related disciplines. The study’s results contribute to developing the history of managerial thought.
43
Binamungu, Leonard, and Masoud Mahundi. "Investigating the Support for Agility in Developing Government Software Systems: A Case of Three East African Countries." Tanzania Journal of Engineering and Technology 41, no. 3 (December 11, 2022): 1–13. http://dx.doi.org/10.52339/tjet.v41i3.839.
Full textAbstract:
Agile Software Development Methods support an iterative and incremental way of developing software systems while responding to change by prioritising various aspects at different times. This differs from traditional sequential methods like Waterfall, in which one software development stage has to be completed before starting the next stage. To produce software systems that meet the requirements of their institutions, several governments in Africa have issued standards and guidelines to be followed during the development of government software systems. Such standards and guidelines specify the specific activities and deliverables for each stage of software development. While well-intentioned, such guidelines and standards can also hinder creativity and innovation which could be key to producing good quality and sustainable software systems. Given the degree of leniency that they offer, Agile methods could give room for such creativity and innovation among team members. However, despite such good potential in Agile methods, the literature lacks evidence regarding if and how the software development guidelines and standards issued by several African governments support agility. Various documents from three East African countries were reviewed, to determine if and how they support for agility during the development of government software systems. Guidelines and standards were reviewed using the lens of four Agile Values stated in the Agile manifesto. Results show the following: there is a marked lack of support for agility during the development of government software systems; the standards and guidelines are generally characterised by excessive micromanagement of the development process, leaving little or no room for innovation and creativity amongst members of the development teams; and the guidelines seem to assume uniformity across development projects, irrespective of the fact that software development projects can vary depending specific contextual dictates. Furthermore, recommendations on how governments can adopt and support agility during software development are provided.
44
Mani, Swaminathan, and Mridula Mishra. "Characteristics and ingredients of an agile work force – a strategy framework." Strategic HR Review 19, no. 5 (August 3, 2020): 227–30. http://dx.doi.org/10.1108/shr-02-2020-0013.
Full textAbstract:
Purpose The purpose of this study is to provide a viewpoint on the characteristics and ingredients of what constitutes an agile team using the lens of progress made toward goals (with three sub-categories) and execution/a bias for action (with three sub-categories). Also, highlight the similarity of constructs between two different yet related concepts of employee engagement and agile workforce and how they can be a force multiplier for companies if leveraged right. Design/methodology/approach This study undertook literature review of key papers in the areas of building agile teams, its benefits and success stories largely popularized by the technology companies in the software development lifecycle and core constructs of employee engagement. The authors then build a framework of what constitutes an agile team, while briefly explaining the nine archetypes that emerge from the 3 × 3 matrix. Findings Employee engagement and agile teams, although different yet related concepts, have very similar underlying constructs. Companies can take advantage of the symbiotic and mutually reinforcing relationship between these two constructs to “futureproof” their business in these turbulent times. Adopting an agile mind-set to team development – experimentation, incremental, iterative progress, nimble and flexible to pivot as per changes in environment – has proven to be successful for many iconic companies. A 3 × 3 matrix plotted against progress toward goals and a bias for action (with three sub-categories each) has given nine team archetypes, with agile team occupying the aspirational, north-east corner of the matrix. Originality/value This paper provides insights into this important concept of building agile teams and offers a strategy model to be leveraged to build an agile mind-set in companies. HR managers now have a strategic framework to understand the characteristics and ingredients of agile team and understand the similarity of constructs between employee engagement and agile workforce. They can audit where their teams are at present and work on a clear road map to move them into agile mode.
45
Jondya, Aisha Gemala, Hisyam Izuddin Anwar, Muhammad Rifky Hermawan, and Tobia Azaria Deru. "Developing "EMBER": A Fantasy Puzzle Adventure Game with An Approach to Agile by Applying Game-Scrum Methodology." Engineering, MAthematics and Computer Science (EMACS) Journal 4, no. 2 (June 9, 2022): 39–43. http://dx.doi.org/10.21512/emacsjournal.v4i2.8428.
Full textAbstract:
Digital games development process is often done using traditional methods. Many digital game developers believe that the game development process cannot be equated and use other software development methods because game development is not only focused on technical processes such as programming and coding but also creative processes such as asset and display design. In this study, the process of developing a fantasy adventure puzzle game was carried out using the Game-Scrum approach, a method modified from the Agile Scrum method. As well as the software development process using the agile method, game development using this method is carried out with an iterative process where each process allows an update of the feedback given to each sprint backlog. At the end of the study it was concluded that although there were still some things that had to be adjusted, basically the Game Scrum method could be adapted for the development of a digital game.
46
Chung, Timothy, and Roshan Daniel. "DARPA OFFSET: A Vision for Advanced Swarm Systems through Agile Technology Development and ExperimentationDARPA OFFSET: A Vision for Advanced Swarm Systems through Agile Technology Development and Experimentation." Field Robotics 3, no. 1 (January 20, 2023): 97–124. http://dx.doi.org/10.55417/fr.2023003.
Full textAbstract:
As robotics and autonomous technologies continue to see breakthrough innovations, specifically in the areas of large-scale multi-robot teams, their alignment with operationally relevant applications in fielded contexts has been necessary to both obtaining valuable user feedback as well as informing and refining the use cases themselves, i.e., co-evolving the concepts of operations alongside technology maturation. The Defense Advanced Research Projects Agency (DARPA) OFFensive Swarm-Enabled Tactics (OFFSET) program1 was a four-year program which actively embraced this iterative, mission-focused development approach, coupling technology innovation with field experimentation activities to rapidly advance capabilities for large-scale, heterogeneous robotic teams in complex and adversarial urban environments. This vision paper highlights the motivation for the OFFSET program; provides descriptions of the technical objectives and outcomes; and offers insights into the program structure designed to facilitate and inject technology innovations through an ambitious campaign of field tests and learning.
47
Mei, Bing, Lawrence May, Rena Heap, Damon Ellis, Sue Tickner, Jacqui Thornley, Jamie Denton, and Richard Durham. "Rapid Development Studio: An Intensive, Iterative Approach to Designing Online Learning." SAGE Open 11, no. 3 (July 2021): 215824402110475. http://dx.doi.org/10.1177/21582440211047574.
Full textAbstract:
Given the increasing demand for online learning at the tertiary level, there currently exists a need to modify or develop instructional design (ID) models/approaches that can effectively facilitate the collaboration between learning designers and teachers, as well as to research the effectiveness of these models/approaches. Against this backdrop, adopting a design-based research approach, we tested a practical ID approach that is developed on two prior models: rapid prototyping and collaborative course development. Accordingly, a 2-week rapid development studio—an agile, intensive, iterative ID process—was arranged. Data from multiple sources were gleaned during the study to generate a comprehensive and in-depth understanding of the proposed approach. Overall, results suggest that the approach is effective for developing online courses in case of a limited time frame and was positively perceived by both course instructors and learning designers. Moreover, practical tips for replicating the process in other contexts are also shared. It is our hope that the study will stimulate further exploration of alternative ID models/approaches to improve online course design efficacy in other higher education institutions.
48
Horton, Randy, Bob Moll, and Ke Li Yew. "The Best of Both Worlds: Using Qualitative and Quantitative Feedback to Improve the Design of Connected Medical Devices." Proceedings of the International Symposium on Human Factors and Ergonomics in Health Care 11, no. 1 (October 2022): 95–97. http://dx.doi.org/10.1177/2327857922111019.
Full textAbstract:
The medical device industry has a long legacy of product development processes that are heavily influenced by the design of the device hardware. As devices have become connected, often to smartphones via connections such as Bluetooth, software is playing an increasing role in the overall system and in particular the user interface. As a result, iterative agile design practices that are prevalent in software are starting to influence the connected device development process. These modern agile practices put the user at the center of the design problem. But what is the best way in this new world to get feedback from users such that the overall product can be improved? In this paper, we share two techniques, one qualitative and one quantitative, that can answer this question. We’ll also explore the synergy of using both techniques together.
49
Padley, Ann. "The agile ethics process: An oxymoron or a new paradigm in education?" Industry and Higher Education 35, no. 4 (May 11, 2021): 347–52. http://dx.doi.org/10.1177/09504222211015606.
Full textAbstract:
Project-based innovation and entrepreneurship curricula encourage learners to approach challenges in an agile, iterative way, allowing for flexibility to respond to new information throughout the research and idea development process. This approach often clashes with traditional ethical approval processes designed for a more predictable set of research methods. This account of practice explores the tensions thus arising and asks how the ethics review process might better support the development of future ethical, responsible innovators? Three key insights related to the importance of balance, language and shared understanding are introduced and presented as part of a pilot project.
50
Owen, Hazel, and Nicola Dunham. "Reflections on the Use of Iterative, Agile and Collaborative Approaches for Blended Flipped Learning Development." Education Sciences 5, no. 2 (April 10, 2015): 85–103. http://dx.doi.org/10.3390/educsci5020085.
Full text