A hybrid consisting of Agile and Stage Gate
(→Method description) |
(→Abstract) |
||
| Line 5: | Line 5: | ||
Project Management is not only about achieving a purpose. It is about achieving a purpose within a limited time, cost, and meeting the preset quality criteria - this is known as the triple constraints illustrated by the Iron Triangle <ref name=two> Geraldi, J., Thuesen, C., Oehmen, J. & Stingl, V.. ''Doing Projects: A Nordic Flavour to Managing Projects'', 2nd edition, 2017, ISBN: 978-87-7193-076-4. </ref> [p. 71]. A combination of an Agile approach and the Stage-Gate model is a systematic way of controlling these three constraints as the project manager and make the project effective and efficient. The large project is divided into stages by the Stage-Gate model and running Agile cycles in each stage. Time, cost and quality is reviewed at each gate before moving on to the next stage. This combination is even possible for a program with several parallel projects - projects with their own individual stages but sharing gates across the program to align and keep the whole project and parts on track and without exceeding the time-, cost-, and quality limits. | Project Management is not only about achieving a purpose. It is about achieving a purpose within a limited time, cost, and meeting the preset quality criteria - this is known as the triple constraints illustrated by the Iron Triangle <ref name=two> Geraldi, J., Thuesen, C., Oehmen, J. & Stingl, V.. ''Doing Projects: A Nordic Flavour to Managing Projects'', 2nd edition, 2017, ISBN: 978-87-7193-076-4. </ref> [p. 71]. A combination of an Agile approach and the Stage-Gate model is a systematic way of controlling these three constraints as the project manager and make the project effective and efficient. The large project is divided into stages by the Stage-Gate model and running Agile cycles in each stage. Time, cost and quality is reviewed at each gate before moving on to the next stage. This combination is even possible for a program with several parallel projects - projects with their own individual stages but sharing gates across the program to align and keep the whole project and parts on track and without exceeding the time-, cost-, and quality limits. | ||
| − | + | As it is claimed in the book ''Doing Projects: A Nordic Flavour to Managing Project'' | |
= Method description = | = Method description = | ||
Revision as of 17:29, 11 February 2021
Contents |
Abstract
Project, Program and Portfolio Management is the application of processes, tools and methodologies to successfully plan and execute projects. Agile project management is an iterative approach that focuses on breaking down large projects into smaller and more manageable tasks in small cycles/sprints, which are completed in short iterations throughout the project life cycle. [1] The Stage-Gate model is an approach to guide a project from idea to launch by efficient project management. The large project, or even program, is separated into stages, and the end of each stage requires a review to pass a gate and begin on the next stage. These gates review whether or not the project is ready to continue and move on to the next stage, which also include portfolio management - is the project balanced and aligned with the portfolio.
Project Management is not only about achieving a purpose. It is about achieving a purpose within a limited time, cost, and meeting the preset quality criteria - this is known as the triple constraints illustrated by the Iron Triangle [2] [p. 71]. A combination of an Agile approach and the Stage-Gate model is a systematic way of controlling these three constraints as the project manager and make the project effective and efficient. The large project is divided into stages by the Stage-Gate model and running Agile cycles in each stage. Time, cost and quality is reviewed at each gate before moving on to the next stage. This combination is even possible for a program with several parallel projects - projects with their own individual stages but sharing gates across the program to align and keep the whole project and parts on track and without exceeding the time-, cost-, and quality limits.
As it is claimed in the book Doing Projects: A Nordic Flavour to Managing Project
Method description
The Agile approach and the Stage Gate model for project management are in following described. In the end of the section the hybrid consisting of the two approaches will be introduced as a strong combination for you as a Project Manager.
Agile
The history of Agile goes all the way back to 1957 when building software for IBM and Motorola. In these projects incremental development techniques were used, which today are known as Agile. [3] Although, not knowing what to name and how to classify the way of working with the projects they were still practicing it and knew that it was different from Waterfall. The modern way of an Agile approach and the approach today classified as Agile was officially introduced in 2001 by a group of professional software developers. These developers met to discuss alternative project methodologies and the outcome of this meeting was the Manifesto for Agile Development [4]. Even though the approach was discussed and mapped out by software professionals, the Agile approach of Project Management is adapted by more than IT teams. Marketers, universities, the military, and even the automotive industry are using the Agile methodology to develop and deliver innovative products/services in markets or environments who possesses uncertainty.
Over the years, the Agile approach has turned into several Agile Frameworks suited for different projects and situations. A selection of the most popular Agile Frameworks is Scrum, Kanban, Lean, and XP. [5] Despite of the Agile Frameworks being used in the given project, the project manager has the usual five phases to manage in the temporary project life cycle: [2] [p. 46-47]
- Project Initiation
- Project Planning
- Project Execution
- Project Monitoring and Control
- Project Closure
What makes these frameworks different is how they approach these five phases.
The Manifesto for Agile Development published in 2001 clearly specifies the fundamental principles of the approach:
- Individuals and interactions over processes and tool
- Working software over comprehensive documentation
- Customer collaboration over contact negotiation
- Responding to change over following a plan
In contrast to a straightforward linear approach like the waterfall model, Agile projects consist of a sequence of steps (known as sprints in Scrum). The steps can be seen in Figure 1. This sequence can easily turn into a cycle if the product/service does not perform as expected and agreed with the client in step 5. In this case, the sequence will start up again from step 1 and keep going until satisfaction is achieved. This approach is at most used as a cycle from the beginning - a project is cut into small pieces and developed though many cycles/sprints of the Agile Methodology in close contact with the client.
A short description of the five steps in Figure 1:
- Step 1: Mapping processes to determine the starting point and the "Actual State".
- Step 2: Optimize a process with the right combination of technologies.
- Step 3: Choose technologies and review options with the client. The client is part of the project from the very beginning and feedback is vital.
- Step 4: Weekly/monthly delivery of developments for the end user to operate and request for changes. It is ideal, that the end user is part of the process of development and testing.
- Step 5: Evaluate through Key Performance Indicators (KPI's), reports and other metrics, in order to monitor that the process is working as agreed.
Stage Gate
The hybrid
They complement each other quite well - Stage Gate is a predictive way of managing project and Agile is adaptive (p. 49 in doing projects).
(p. 46-47 in doing projects - what is a project lifecycle? Stage Gate define the life cycle and Agile is used within the phases. DS p. 11 - monitoring/controlling is connected to all the phases.
The hybrid can be used for innovation for both digital solitions, physical products and service products.
"First, because this novel Agile-Stage-Gate® hybrid approach provides a framework for dealing with uncertainties and ambiguity in the front-end, accelerates the process through the use of time-boxed iterations, and focuses on the results via development of tangible product increments as the measure of progress."
Application
As the project manager you need to know, setup and controle the key components of the Agile Approach (User stories, sprints, stand-up meetings, agile board, backlog) and be aware of the team roles (scrum master, product owner, team members, stakeholders).
Limitations
(All approaches and methods got their limitations and this combination is no exception.)
References
Citation
- ↑ Workfront, Agile Project Management, accessed 10 February 2021, https://www.workfront.com/project-management/methodologies/agile
- ↑ 2.0 2.1 Geraldi, J., Thuesen, C., Oehmen, J. & Stingl, V.. Doing Projects: A Nordic Flavour to Managing Projects, 2nd edition, 2017, ISBN: 978-87-7193-076-4.
- ↑ Altexsoft, Agile Project Management: Best Practices and Methodologies, accessed 11 February 2021, https://www.altexsoft.com/whitepapers/agile-project-management-best-practices-and-methodologies/
- ↑ Fowler, M. & Highsmith, J., The Agile Manifesto, August 1, 2001 accessed February 11, 2021, https://www.drdobbs.com/open-source/the-agile-manifesto/184414755
- ↑ Agile-Mercurial, Comprehensive List of Agile Frameworks, accessed 11 February 2021, https://agile-mercurial.com/2019/02/06/agile-frameworks-fact-sheet/
- ↑ Sudarsan Reddy, Agile Project Management Methodology - Manifesto, Frameworks and Process, accessed 10 February 2021, https://medium.com/@sudarhtc/agile-project-management-methodology-manifesto-frameworks-and-process-f4c332ddb779
Annotation
1. Yes this is good
