Milestone-Driven Agile Execution

2021 ◽  
pp. 1-27
Author(s):  
Eduardo Miranda
Keyword(s):  
Process Control ◽  
Software Development ◽  
Empirical Process ◽  
Strategic Plan ◽  
Agile Development ◽  
Just In Time ◽  
Development Framework ◽  
Time Planning

This chapter introduces a hybrid software development framework, called Milestone-Driven Agile Execution, in which the empirical process control and the just-in-time planning of tasks of agile development are retained but the prioritization of the backlog is done according to a macro or strategic plan that drives the execution of the project. Selecting work items from the product backlog according to a plan instead of following the immediate concerns of a product owner adds visibility, predictability, and structure to the work of the team while preserving the adaptive advantages of agile development.

An Agile Perspective on Open Source Software Engineering

2012 ◽  
Vol 4 (3) ◽  
pp. 52-65
Author(s):  
Sofiane Sahraoui ◽  
Noor Al-Nahas ◽  
Rania Suleiman
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Agile Development ◽  
Planning And Design ◽  
Development Framework ◽  
Software Engineering Process ◽  
Development Processes ◽  
Agile Software

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.

Batch-based agile program management approach for coordinating IT multi-project concurrent development

2021 ◽  
pp. 1063293X2110152
Author(s):  
Qing Yang ◽  
Yingxin Bi ◽  
Qinru Wang ◽  
Tao Yao
Keyword(s):  
Software Development ◽  
New Technologies ◽  
Program Management ◽  
Agile Development ◽  
Management Approach ◽  
Development Projects ◽  
Project Development ◽  
Concurrent Development ◽  
Communication And Coordination ◽  
Development Practice

Software development projects have undergone remarkable changes with the arrival of agile development approaches. Many firms are facing a need to use these approaches to manage entities consisting of multiple projects (i.e. programs) simultaneously and efficiently. New technologies such as big data provide a huge power and rich demand for the IT application system of the commercial bank which has the characteristics of multiple sub-projects, strong inter-project correlation, and numerous project participating teams. Hence, taking the IT program management of a bank in China as a case, we explore the methods to solve the problems in multi-project concurrent development practice through integrating the ideas of program and batch management. First, to coordinate the multi-project development process, this paper presents the batch-based agile program management approach that synthesizes concurrent engineering with agile methods. And we compare the application of batch management between software development projects and manufacturing process. Further, we analyze the concurrent multi-project development practice in the batch-based agile program management, including the overlapping between stages, individual project’s activities, and multiple projects based on common resources and environment to stimulate the knowledge transfer. Third, to facilitate the communication and coordination of batch-based program management, we present the double-level responsibility organizational structure of batch management.

scholarly journals Modelo Aplicable A La Gestión De Procesos Ágiles De Desarrollo De Software Basado En Cmmi –Dev 1.3 Y Scrum

2015 ◽  
Vol 3 (1) ◽  
Author(s):  
Adriana Iglesias ◽  
Acellys Messino ◽  
Patty Pedroza ◽  
Ricardo Llanos
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Continuous Improvement ◽  
Process Management ◽  
Model Development ◽  
Agile Development ◽  
Total Quality ◽  
Model Quality ◽  
Development And Management ◽  
Buenas Prácticas

El presente Artículo de Investigación propone un modelo orientado a las necesidades de calidad total en las organizaciones dedicadas al desarrollo de software conforme a la alineación de los procesos de desarrollo y gestión con los objetivos organizacionales; lo cual hace pertinente la formulación de un modelo de gestión de procesos de desarrollo basado en los principios y prácticas del enfoque ágil, orientado hacia la aplicación de buenas prácticas y procesos de mejora continua. El modelo planteado se denomina SUMM - “Modelo Unificado de Madurez de Scrum” y está orientado a la gestión de procesos ágiles de desarrollo de software enmarcados en las buenas prácticas de CMMI-DEV 1.3 y el marco de trabajo de SCRUM. SUMM consta de cinco niveles de madurez, de acuerdo a la representación por etapas de CMMI - DEV, estos niveles a su vez están compuestos de Metas, Objetivos, Prácticas e Indicadores que permitirán a la organización poder emplear un modelo de desarrollo ágil de calidad, enfocados en procesos de mejora continua.AbstractThis article of Research proposes a model oriented to the needs of total quality in organizations dedicated to software development according to the alignment of development and management processes with organizational objectives, which makes the formulation of relevant management model development process based on the principles and practices of agile approach towards the application of best practices and continuous improvement processes. The proposed model is called SUMM - "Unified Model Scrum Maturity" and is focused on process management software development agile framed in the best practices of CMMI-DEV 1.3 and SCRUM framework. SUMM consists of five maturity levels, according to the staged representation of CMMI - DEV, these levels in turn are composed of Goals, Objectives, Practices and indicators that enable the organization to employ an agile development model quality focused on continuous improvement processes.

scholarly journals New Approach on the Agile Cycles Containment Effectiveness Metrics in Automotive SW Development

ACTA IMEKO ◽  
2019 ◽  
Vol 7 (4) ◽  
pp. 3
Author(s):  
Ionut Andrei Sandu ◽  
Alexandru Salceanu
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Extended Version ◽  
New Approach ◽  
Development Team ◽  
Real Application ◽  
Original Contribution ◽  
Agile Software

<p class="Abstract"><span lang="EN-US">In an ideal Agile Development Team, defects should not exist. But in reality and especially in Automotive Agile Software Development, we need to have a mechanism for defects handling and tracking to closure. In this paper we describe the benefits and principles for measuring the defects handling metrics in automotive programs and organizations which adopted Agile SW Development. We are presenting the Iteration Containment Effectiveness, Program Increment Containment Effectiveness and Defect Debt Trend metrics. The acquired advantages are demonstrated by a detailed example of real application on how to measure the classical Phase Containment Effectiveness metric on Iteration (Sprint) and Program Increment (Scum of Scrums / Scaled Agile) Level. This paper is an extended version of the original contribution to the IMEKO TC 4 2017 symposium in Iasi, Romania.</span></p>

scholarly journals KONSEP DAN TEKNIK MANAIEMEN MUTU TERPADU

2017 ◽  
pp. 94-101
Author(s):  
Saut Pruba
Keyword(s):  
Process Control ◽  
Statistical Process Control ◽  
Continuous Improvement ◽  
Six Sigma ◽  
Employee Empowerment ◽  
Just In Time ◽  
Statistical Process

Quality is a term that has diflferent meanings to different people. Quality set out in this paper are the features and characteristics of the total of a product or service associated with its ability to satisfij the needs of the visible or disguised. The quality of the environment requires an establishment of TQM because quality can not be examined only in a product. In this paper also discussed the concept of the seven TQM: continuous improvement, Six Sigma, employee empowerment, benchmarking, just in time, the concept of Taguchi TQM techniques and knowledge. TQM is the seventh technique check sheet, scatter diagrams, cause-effect diagrams, Pareto charts, flow charts, histograms, and statistical process control.

Making Agile Development and Offshoring Practice Successful on Global Software Development Project

2013 ◽  
pp. 107-119
Author(s):  
Edward Chen
Keyword(s):  
Software Development ◽  
Development Project ◽  
Lessons Learned ◽  
Global Software Development ◽  
Agile Development ◽  
Business Practices ◽  
Global Business ◽  
Software Development Project ◽  
Business Applications ◽  
Develop Software

Two significant trends have been gaining momentum in software development: the utilization of Agile development methodologies, and the continuing trend of companies to outsource development work offshore. These two trends have changed the way companies develop software and business applications. This chapter seeks to evaluate how a company can successfully manage both trends in conjunction with each other on global business. The primary question addressed is whether the benefits derived from Agile development methodologies and the savings from outsourced software development efforts cancel each other out when applied together, or whether they create a synergy greater than the sum of the parts. In order to answer this question, this chapter intends to examine several relevant business practices and industry experiences. From lessons learned, we identify factors which seem to influence a successful combination of Agile methodology and offshoring in global software development projects.

Toward Agile Interactive Software Development Process Models for Crowd Source Projects

2014 ◽  
pp. 117-131
Author(s):  
Izzat Alsmadi ◽  
Saqib Saeed
Keyword(s):  
Software Development ◽  
Process Models ◽  
Agile Development ◽  
Software Project ◽  
Interactive Software ◽  
Crowd Sourcing ◽  
Software Projects ◽  
The Public ◽  
Development Models ◽  
High Level

Typical traditional software development models are initially designed for company-style software project teams. They also assume a typical software project that has somewhat clear goals, scope, budget, and plan. Even Agile development models that are very flexible in considering previous project parameters assume somewhat stable team and project structures. However, in recent years, the authors have noticed expansion in software projects that are developed in a very illusive flexible team, scope, budget, and plan structures. Examples of such projects are those projects offered in open competition (also called crowd sourcing) structure for software developers to be part of. In typical open competition projects, initial, high level project ideas are submitted to the public through the Internet. The project initiators give their initial requirements, constraints, and conditions for successful products or submissions. Teams can be organized before or through the competition. Submission and evaluation of deliverables from teams are subjected to project initiator evaluation along with evaluation teams organized through the open competition host. This chapter investigates all traditional project characteristics. The authors elaborate on all those elements that should be modified to fit the open competition agile structure. They use several case studies to demonstrate management issues related to managing software projects in open competitions.

Sign in / Sign up

Export Citation Format

Share Document