A project team is using the Stacey Complexity Model to map the degree of uncertainty in the project and select the appropriate project life cycle. As the meeting progresses, it becomes evident that while the requirements are well-known, the team is unfamiliar with the technology required to implement them. As a result, the team selects an adaptive project life cycle.
Where on the Stacey Complexity Model did the team most likely map the project?
(Please note that on the real PMP exam you may be asked to provide your answer by clicking the correct area in the image. But here in the simulator, we are asking you to select the answer below.)
Explanation:
A project life cycle is the series of phases that a project passes through from its start to its completion. (Note, the word "phase" in this context is used differently from how it's used in multi-phase projects). The project life cycle provides the basic framework for managing the project. Predictive, iterative, incremental, adaptive, hybrid are examples of a project life cycle. The selection of the life cycle depends on project characteristics. There are various models that can be used to describe project characteristics. One of them is the Stacey Complexity Model. The model addresses the degree of uncertainty as it relates to the project requirements on the one hand and how to fulfill those requirements using current knowledge and technology on the other hand. The technical degree of uncertainty is mapped on the horizontal axis, and the uncertainty of requirements is on the vertical axis. According to the model, as project uncertainty increases along any of those dimensions, so too does the risk of rework and the need to use a different project management approach.
When project requirements, as well as the technology to implement these requirements, are clear, the predictive project life cycle is typically the way to go. As the degree of uncertainty increases, the likelihood of changes, risk, and rework increases as well. Such projects would benefit from either iterative, incremental, adaptive, or hybrid life cycles. When both the technical degree of uncertainty and the degree of uncertainty in project requirements is very high, a project is considered chaos (or anarchy). Managing such a project is very hard to impossible.
In the scenario, the project requirements are well-known, meaning the degree of uncertainty in requirements is low. However, the team is unfamiliar with the technology required to implement them, implying the technical degree of uncertainty is high. Based on these findings, the team selects an adaptive project life cycle, implying the project has been mapped within area C.