Adaptive Project Framework
Draft
Adaptive Project Framework (APF) is a methodology used in project management where the need to constantly adapt to the changing environment of a project.[1] This is a systematic and structured process that allows project managers to enhance their decisions and practices during the project life cycle based on learning from previous results achieved during the project. [2] APF is designed to continually adapt to the changing situation of a project from its very beginning to its very end.[3] Therefore, with this approach, nothing is fixed: neither the duration of the project, nor the budget, nor the risks, and everything can be continuously adjusted according to changes in the project's characteristics.[1] This is a costumer driven process that requires the client and the project team to be effectively involved, acting in an open and trusting partnership.[3]
Contents |
Overview
Recognised strategic leader in the field of project management, Robert K. Wysocki published the book Adaptive Project Framework in 2010, where he describes the APF approach when managing complexity in uncertainty. The AFP method was created to help teams adapt continuously to projects changing environment. Therefore, with this approach, nothing is fixed: neither the duration of the project, nor the budget, nor the risks, and everything can be continuously adjusted according to changes in the project's characteristics. [1]
To implement the APF methodology successfully, project teams must be willing to accept and adapt to changes. It is a costumer driven process, where the client is involved in every stage of the process and even given the opportunity to control the direction of the project. Consequently requires the project team to be effectively involved, acting with an open mind and trusting partnership. [4]
Application
Taking a closer look at the project framework, it consists of five main steps.
Project Scope
The first part of the process is identifying the project scope and that involves understanding the needs of the costumer. Therefore Stakeholders first step is to determine the conditions of satisfaction (CoS). That is the project goals and the desired outcome, by finding out what are the client's needs and how to meet those needs. From this point the project overview statement (POS) is written to outline the CoS and is approved by all stakeholders, this is done to evaluate the effectiveness of the process and how it will be accomplished. [4] Finally three documents are needed to finish the project scope. First, there is the functional requirements, that prioritises actions as well as possible risks, challenges and assumptions. As the project progresses, this may change. Second, there is the Work Breakdown Structure (WBS) that enables teams to estimate costs, develop schedule and break down the processes into manageable parts that needs to be accomplished. Finally there is the triangle scope, which is how time, cost and quality will converge. [5]
Cycle plan
The project is divided into multiple mini-projects or cycles, where each cycle delivers one or more deliverables. This is the iterative part of the method, that is repeated over and over again for the next three steps.
This is the start of the cycle that is repeated over and over again for the next three steps. This is the iterative portion of the method. The cycle plan defines each task to be performed in this mini-project and establishes the dependencies for the completion of these tasks. This relates to the information provided in the WBS but may be changed and adapted between iterations. The cycle plan also establishes meaningful groups of tasks and allocates these groups to team members or different teams. The team member or team will respond with a schedule and a list of resources needed to accomplish the task.
The project is divided into mini-projects or cycles (also called iterations), and each cycle must provide one or more deliverables. This second step involves the planning of each project cycle. The objective is to define and plan the tasks to be accomplished.
You list the individual tasks to be carried out according to the WBS, establish the order in which they are to be carried out, identify their interdependencies, assign them to your employees, and define their deadlines.
As the team works on the project, cycles can be adjusted. When the pre-defined time elapses, the cycle ends, and all the tasks that hadn’t been completed during this cycle move to the next one. It’s important to ensure clear communication, noting any requests for change and new ideas for improvement. When the team encounters any unexpected problems, they should also be addressed in the next cycle.
Cycle completion
Client checkpoint
Post-version review
Limitations & Challenges
text
Annotated Bibliography
text
References
- ↑ 1.0 1.1 1.2 David Galiana (2020) Adaptive Project Framework: an introductory guide for beginners. Available at: https://www.wimi-teamwork.com/blog/adaptive-project-framework-introductory-guide-beginners/ .
- ↑ Paul Naybour (2018) Adaptive Project Framework Explained. Available at: https://www.parallelprojecttraining.com/adaptive-project-framework-explained/ .
- ↑ 3.0 3.1 Robert K. Wysocki Ph.D. (2010) Adaptive Project Framework. Managing Complexity in the Face of Uncertainty. Available at: https://books.google.dk/books?hl=en&lr=&id=M6GDUXXOtxsC&oi=fnd&pg=PT15&dq=adaptive+project+framework&ots=yEHeTTRqmv&sig=Jl-nX12tB_o8DMn-vYijB6R9uio&redir_esc=y#v=onepage&q=adaptive%20project%20framework&f=false .
- ↑ 4.0 4.1 StartValley (2021) Adaptive Project Framework: How to Implement It. Available at: https://www.startupvalley.news/adaptive-project-framework/ .
- ↑ ThinkTheme (n.d.) Adaptive Project Framework Methodology. Available at: https://thinkthyme.com/project-management/adaptive-project-framework-methodology .
