Adaptive Project Framework is a project methodology that makes use of selected phases of the traditional project management approach focusing on planning for just-in-time as opposed to scheduling the whole project from the beginning to the end (Stare 300). It is normally client-focused, and requirements are expected to change constantly. This approach has five main phases that include version scope, cycle plan, cycle build, client checkpoint and post-version review. During all the phases, planning is primarily founded on functionality, and this is kept at the high level unit for each cycle and is iterative in nature. This paper is an analysis and description of metrics that would be put in place as early warning signs that an Adaptive Project Framework is headed for a distressed condition in each of the phases. These phases are represented as follows
Version Scope is the first phase of Adaptive Project Framework and, like the planning phase in TPM project management, the project scope, project risks assessment and conditions of satisfaction are identified. In this phase, goals, objectives, risks and problem description takes place (Wysocki 34). The metrics for the version scope phase are when timelines are exceeded by one week since the commencement of the project.
Cycle plan is the second phase of Adaptive Project Framework and takes about fixed duration of time. In this phase, work breakdown structures are filled with tasks, dependency tasks agreed, and resources agreed (Wysocki 36). The duration that each task is to take is agreed by the customer, and typically workers work in parallel and in small groups on various tasks. The metric in this phase is that when the schedule of the phase is exceeded by two weeks, the project manager must redefine the project progress.
The Cycle build is the third phase of APF where the duration must be limited to planned duration. It ensures that much of the developed functionalities of the project such as software modules are developed and implemented within the timeframe stipulated. It monitors corrective action needed to be taken, records problems in issues log and records change requests. The metric for this project is exceeding the budget for this phase by 5% and falling behind the schedule by three weeks.
The last phase for APF is the Post version review that checks the whole project against the predefined success criteria and if the project is severely below the expectations, it is dropped especially if it has exceeded schedule by six months and the budget is well above 35% of the initial budget.
Works Cited
Stare, Aljaž. "Agile Project Management in Product Development Projects." Procedia-Social and Behavioral Sciences 119 (2014): 295-304. Print.
Wysocki, Robert K. Effective project management: traditional, agile, extreme. John Wiley & Sons, 2014. Print.
