Adaptive Project Framework Part 4: Cycle Build
APF is an approach to a class of projects for which neither the traditional nor the extreme methods are appropriate. APF is entirely compatible with the PMI PMBOK Standards. This series is derived from selected content from the 3rd edition of Effective Project Management: Traditional, Adaptive, Extreme (John Wiley & Sons Publishers, July, 2003).
An Overview of the Cycle Build Phase
As shown in Figure 1, the Cycle Build Phase is:
Figure 2: The Adaptive Project Framework
The principal activity of the Cycle Build Phase is to deliver whatever parts of the prioritized functionality that was assigned to this cycle that can be delivered within the established time box and resource constraints of the cycle. There are two characteristics that separate the APF Cycle Build from the similar activity in a TPM project. The first is that the time box is never extended. It was set during the Version Scope Phase and it is fixed at that value. In a TPM project, the schedule completion date of the project may be extended. The analog in an APF project is the cycle and its completion date is never extended--never. If something was scheduled to be completed during the cycle and time expired, that deliverable will be put back in the mix and reprioritized for the next cycle. The second difference is that changes are never approved within a cycle.
Please log in or sign up below to read the rest of the article.