According to the PMBOK Guide and the Agile Practice Guide, project life cycles range from predictive to adaptive. The selection of the life cycle depends on the degree of change and the frequency of delivery required by the project environment.
* Adaptive Life Cycles: Also known as agile or change-driven methods, these are specifically designed to handle high levels of change and require ongoing, extensive stakeholder involvement.
* Characteristics: In an adaptive environment, the overall scope is decomposed into a set of requirements and work to be performed, often called a product backlog. At the end of each iteration, the product is reviewed by stakeholders to provide immediate feedback, ensuring the project stays aligned with evolving business needs.
* Suitability: This model is most appropriate when the project requirements are not well-defined at the start or when the environment is highly volatile (high uncertainty).
Comparison with other options:
* B. Reflexive: This is not a recognized project life cycle model within PMI standards or the PMBOK Guide.
* C. Predictive: Also known as waterfall, this life cycle is used when the project scope, time, and cost are determined in the early phases of the life cycle. It is best suited for environments with low levels of change and well-understood requirements.
* D. Iterative: While iterative models involve repeating activities to further enhance the product, the Adaptive model is the more comprehensive term used by PMI to describe the specific combination of iterative and incremental approaches optimized for high change and high stakeholder engagement.