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. 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. APF is designed to continually adapt to the changing situation of a project from its very beginning to its very end. 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. 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.

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.

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.

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. 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 need to be accomplished. Finally there is the triangle scope, which is how time, cost and quality will converge.

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. The cycle plan involves defining each task that needs to be accomplished in each project cycle according to the WBS but is adapted between cycles. Order of the tasks is established, their interdependencies are identified and assigned to employees with an given deadline.

</references>