Adaptive Project Management
From apppm
(Difference between revisions)
| Line 1: | Line 1: | ||
==Abstract== | ==Abstract== | ||
| − | Adaptive project management (APM) is a method applied in project management. The method adapts and changes in response to requests from the stakeholder | + | Adaptive project management (APM) is a method applied in project management. The method adapts and changes in response to requests from the stakeholder. The process in the method allows the manager to improve decisions and practices during the project life cycle based on experiences from previous results obtained during the project. The method accommodates uncertainties where the process is an adaptive structured and systematic iterative process <ref> name= ''M.Mrsic '' >'' M. Mrsic (2017) “Adaptive Project Management” ActiveCollab. Link: https://activecollab.com/blog/project-management/adaptive-project-management'' </ref>. The method derives from agile project management, however, in adaptive project management, the methodology allows the team to respond to unexpected challenges and adapt new improved methods towards reaching the project goal <ref> name= ''Think Thyme'' >'' Alex (2018) “Adaptive Project Framework Methodology” ThinkThyme. Link: https://thinkthyme.com/project-management/adaptive-project-framework-methodology'' </ref>. |
| − | The method can be implemented in nearly all project types with a defined goal but an undecided process to reach the goal. However, one exception is in construction project, where little flexibility is accepted during the project lifecycle. | + | The method can be implemented in nearly all project types with a defined goal but an undecided process to reach the goal. However, one exception is in construction project, where little flexibility is accepted during the project lifecycle. An example of application of the method is during restoration of coastal ecosystem projects <ref> name= ''article'' >'' R. M. Thom (2000) “Adaptive management of coastal ecosystem restoration projects” 15(3-4) p.365-372. Ecological Engineering'' </ref>. |
==History== | ==History== | ||
| − | The method was introduced in 2008 by Robert K. Wysocki <ref | + | The method was introduced in 2008 by Robert K. Wysocki <ref name= ''Think Thyme''>. Often, most project management methods include static strategies, well-defined work, and people working on projects directed by the project manager <ref name=''Lucidchart''>''Lucidchart (2018) "What is adaptive project framework" Blog. link: https://www.lucidchart.com/blog/what-is-adaptive-project-framework'' </ref>. However, strategy is dynamic and unpredictable, and therefore project may fail if the project approach do not deal with uncertainties that exits towards the way to reaching the goal of the project. The APM approach can be compared to the evolution in biology, where favorable traits are adapted in time, and correspondingly, in the adaptive management approach the project manager can adapt new more favorable decisions during the project life cycle to reach the project goal. A change in strategy is accepted as more knowledge, experience and information becomes available, which will be adapted in the strategy < name= ''Think Thyme'' >. The APM method can be viewed as a response to the complexity of projects, where the two most common failure reasons for complex projects are because of re-prioritization and change in strategy <ref name=''Lucidchart''>. |
==Principles== | ==Principles== | ||
The key principles of the methodology are: | The key principles of the methodology are: | ||
| Line 9: | Line 9: | ||
#*Learn from during | #*Learn from during | ||
#*Client driven | #*Client driven | ||
| − | + | The method is distinguished from other management methodologies by placing the client as the central figure, where the demands of the costumer can change the direction of the project <ref> name= ''Think Thyme'' >. In contrast to a static strategy, the APM method has a dynamic and iterative strategy approach, where the uncertainty is accommodated<ref name=''Lucidchart''>. The method prepares the team to respond to the unexpected, and results and decisions are continually being evaluated with a flexible mindset of the team members <ref name=''Lucidchart''>. | |
| − | The method is distinguished from other management methodologies by placing the client as the central figure, where the demands of the costumer can change the direction of the project. In contrast to a static strategy, the APM method has a dynamic and iterative strategy approach, where the uncertainty is accommodated. The method prepares the team to respond to the unexpected, and results and decisions are continually being evaluated with a flexible mindset of the team members. | + | ==Approach== |
| − | + | The method approach has an adaptive and iterative approach, where the project is adapted and improved after each iteration, in agreement with the clients demand and wishes. The method is divided into cycles, where each cycle represents a minor project. After each end minor project, the project team will evaluate results and improve work and procedures if needed. | |
| − | ==Approach | + | The method demands a frequently contact with stakeholders for the team to adapt and deliver the project goal. |
| − | The method approach | + | ==Project Life Cycle== |
| − | + | The project life cycle can be related to the life cycle of a living organism with three major events: | |
| − | The method is divided into cycles, where each cycle represents a minor project. After each end minor project, the project team will evaluate results and improve work and procedures if needed. | + | :1. Project “DNA”: Building the project; the initial evolution and the DNA string defining the building blocks for the project. This phase includes project scope, budget, schedule |
| − | The method demands a frequently contact with stakeholders | + | :2. The living project: The project is breathing and living with planning, design, go-live, development, and delivery. Here unexpected events may occur, and more favorable decisions may be adapted. |
| + | :3. End of life cycle: The project goal is reached. | ||
| + | The life cycle of the APM project is divided into five phases and is illustrated in figure XX, and in the following the phases will be described. | ||
===Phases=== | ===Phases=== | ||
| − | + | ====1. Project scope==== | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | ===1. Project scope=== | + | |
The first part of the project scope is to recognize how the costumer would be satisfied. | The first part of the project scope is to recognize how the costumer would be satisfied. | ||
:1.1. Develop Conditions of Satisfaction (CoS) | :1.1. Develop Conditions of Satisfaction (CoS) | ||
:: In this step the conditions of satisfaction for the project is identified where stakeholders defines project goal and successful outcome. This step forms a reference point and assists the manager to direct the project on course throughout the subsequent phases. | :: In this step the conditions of satisfaction for the project is identified where stakeholders defines project goal and successful outcome. This step forms a reference point and assists the manager to direct the project on course throughout the subsequent phases. | ||
| − | |||
:1.2. Writing the Project Overview Statement (PoS) | :1.2. Writing the Project Overview Statement (PoS) | ||
:: The project overview statement is the deliverable from the developed CoS. With this step the potential risk, obstacles, and assumptions are identified. | :: The project overview statement is the deliverable from the developed CoS. With this step the potential risk, obstacles, and assumptions are identified. | ||
| Line 37: | Line 30: | ||
: 1.4. Work breakdown structure (WBS) | : 1.4. Work breakdown structure (WBS) | ||
:: The work is divided into smaller parts | :: The work is divided into smaller parts | ||
| − | : 1.5. The triangle | + | : 1.5. The triangle scopes |
:: Intersection between time, cost and quality | :: Intersection between time, cost and quality | ||
===2. Cycle Plan=== | ===2. Cycle Plan=== | ||
: This part is the start point of the iterative project cycle which can be repeated unlimited. The cycle plan defines all of the tasks to be conducted and creates the dependencies for the completion of the tasks. In this part, the information defined in the WBS step is assessed and may be changed and adapted between the iterations. | : This part is the start point of the iterative project cycle which can be repeated unlimited. The cycle plan defines all of the tasks to be conducted and creates the dependencies for the completion of the tasks. In this part, the information defined in the WBS step is assessed and may be changed and adapted between the iterations. | ||
| − | |||
===3. Cycle Completion=== | ===3. Cycle Completion=== | ||
| − | : At this point, all tasks are planned and agreed and the work is in progress. The work will continue until the cycle point is complete. Any requests for changes and improvement are being written down. | + | : At this point, all tasks are planned and agreed, and the work is in progress. The work will continue until the cycle point is complete. Any requests for changes and improvement are being written down. |
===4. Client Checkpoint=== | ===4. Client Checkpoint=== | ||
| − | : This step is a review point and will control the planning for the succeeding cycle. The project team will review the quality of what has been completed and assure this is in correspondence with the client opinion. If needed, adaptations are implemented in the following cycle. After the review, the cycle | + | : This step is a review point and will control the planning for the succeeding cycle. The project team will review the quality of what has been completed and assure this is in correspondence with the client opinion. If needed, adaptations are implemented in the following cycle. After the review, the cycle is repeated until the project is completed. |
===5. Final Review=== | ===5. Final Review=== | ||
| − | : The last step is a final review of the project results. This will determine whether the achieved result meets the | + | : The last step is a final review of the project results. This will determine whether the achieved result meets the client satisfaction. In addition, the report should be reflective and consider the effectiveness of the methods implemented. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
==References== | ==References== | ||
<references/> | <references/> | ||
| − | Lucidchart (2018) "What is adaptive project framework" Blog. link: https://www.lucidchart.com/blog/what-is-adaptive-project-framework | + | M. Mrsic (2017) “Adaptive Project Management” ActiveCollab. Link: https://activecollab.com/blog/project-management/adaptive-project-management |
| − | + | Alex (2018) “Adaptive Project Framework Methodology” ThinkThyme. Link: https://thinkthyme.com/project-management/adaptive-project-framework-methodology | |
| + | R. M. Thom (2000) “Adaptive management of coastal ecosystem restoration projects” 15(3-4) p.365-372. Ecological Engineering'' | ||
| + | Lucidchart Team (2018) "What is adaptive project framework" Blog. link: https://www.lucidchart.com/blog/what-is-adaptive-project-framework | ||
Revision as of 11:53, 5 March 2019
Abstract
Adaptive project management (APM) is a method applied in project management. The method adapts and changes in response to requests from the stakeholder. The process in the method allows the manager to improve decisions and practices during the project life cycle based on experiences from previous results obtained during the project. The method accommodates uncertainties where the process is an adaptive structured and systematic iterative process [1]. The method derives from agile project management, however, in adaptive project management, the methodology allows the team to respond to unexpected challenges and adapt new improved methods towards reaching the project goal [2]. The method can be implemented in nearly all project types with a defined goal but an undecided process to reach the goal. However, one exception is in construction project, where little flexibility is accepted during the project lifecycle. An example of application of the method is during restoration of coastal ecosystem projects [3].
History
The method was introduced in 2008 by Robert K. Wysocki Cite error: Closing </ref> missing for <ref> tag. However, strategy is dynamic and unpredictable, and therefore project may fail if the project approach do not deal with uncertainties that exits towards the way to reaching the goal of the project. The APM approach can be compared to the evolution in biology, where favorable traits are adapted in time, and correspondingly, in the adaptive management approach the project manager can adapt new more favorable decisions during the project life cycle to reach the project goal. A change in strategy is accepted as more knowledge, experience and information becomes available, which will be adapted in the strategy < name= Think Thyme >. The APM method can be viewed as a response to the complexity of projects, where the two most common failure reasons for complex projects are because of re-prioritization and change in strategy Cite error: Closing </ref> missing for <ref> tag
Cite error:
<ref> tags exist, but no <references/> tag was found
