PMP · Question #490
As part of the strategic plan, a company decides to implement a new software platform to manage a centralized document repository. Some requirements are clear and some need more detail. What should th
The correct answer is B. Determine the most appropriate life cycle approach for the project. With a mix of clear and unclear requirements for a new software platform, the project manager's initial action must be to evaluate and select the most suitable project life cycle approach.
Question
As part of the strategic plan, a company decides to implement a new software platform to manage a centralized document repository. Some requirements are clear and some need more detail. What should the project manager do first to decide how to manage this project?
Options
- ASelect a predictive development life cycle based on the team's experience
- BDetermine the most appropriate life cycle approach for the project
- CRegister all requirements into a backlog for further detailed analysis
- DSplit the requirements, put them into two separate projects, and apply different approaches
How the community answered
(45 responses)- A9% (4)
- B84% (38)
- C2% (1)
- D4% (2)
Why each option
With a mix of clear and unclear requirements for a new software platform, the project manager's initial action must be to evaluate and select the most suitable project life cycle approach.
Selecting a predictive life cycle solely based on team experience without considering the nature of the requirements (some unclear) might lead to an unsuitable approach that struggles with evolving details and stakeholder feedback.
When a project has a mix of clear and uncertain requirements, the first critical step for the project manager is to assess the project characteristics, such as requirements stability, complexity, technological uncertainty, and stakeholder engagement, to determine which life cycle approach (predictive, agile, or hybrid) will be most effective for managing the project successfully. This decision sets the foundation for all subsequent planning and execution.
Registering all requirements into a backlog is an action specific to an agile or hybrid approach; however, the project manager first needs to determine if such an approach is the most appropriate overall life cycle for the project.
Splitting requirements into two separate projects with different approaches is a significant organizational decision and a premature step before the project manager has even determined the overall best life cycle strategy for the current project.
Concept tested: Project life cycle selection; tailoring approaches
Source: https://www.pmi.org/learning/library/agile-predictive-hybrid-project-management-6599
Topics
Community Discussion
8
Samuel O.Feb 1, 2026B is the right call here. In the real world, you rarely get a perfectly defined scope on day one, and trying to force a fully predictive waterfall just because the team has done it before is a trap. Since some requirements are clear and others need work, you have to evaluate whether a hybrid approach fits best before committing to a execution strategy. I have seen too many PMs default to what they know and regret it later when the vague requirements blow up the baseline.
Nina C.Feb 3, 2026Agreed on B, and the other trap to watch for is picking hybrid without defining which parts go predictive and which go iterative, because the exam loves to test that boundary.
Nina C.Jan 12, 2026Got B on my exam last week. Mixed requirements scream hybrid, not predictive.
Mei-Ling H.Jan 2, 2026Agree with B. The key in the stem is "some requirements are clear and some need more detail," which signals a hybrid or tailored approach, so the PM must determine the most appropriate life cycle before doing anything else. A is wrong because it forces predictive before evaluating the unclear requirements, and C skips the life cycle decision entirely.
Anjali D.Jan 17, 2026Our group leaned A since clear requirements plus experienced team screams predictive, but a few of us felt B was safer. What do others think?
Mei-Ling H.Jan 17, 2026Anjali, the answer is actually B because the stem likely includes a qualifier that points away from pure predictive despite the clear requirements. Watch for words like "evolving" or "changing" paired with the experienced team, which signals adaptive is the safer pick.
Luis F.Feb 6, 2026Gotta be C here, guys. The question literally says some requirements need more detail, so the very first move is getting everything captured in a backlog so the team can refine and analyze what is unclear. I remember from my bootcamp that you cannot really pick a life cycle until you know what you are working with, so B feels like it comes too early in the process. Once the backlog is fleshed out and the fuzzy requirements are better understood, then you can make an informed call on the right development approach. Let me know if I am missing something on this one!
Samuel O.Feb 7, 2026Actually B is the right call here, Luis. When you have unclear or incomplete requirements that need more detail, that is exactly the scenario where an adaptive (agile) life cycle fits, since it is built to handle evolving requirements through iteration and ongoing refinement rather than requiring everything nailed down upfront.