CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach
Question 20 of 85 in Explain when it is appropriate to use a predictive, plan-based approach
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: Consider a hybrid approach where the software and infrastructure workstreams use their natural methodologies within an integrated plan
Explanation
When a project combines workstreams with different characteristics, a hybrid approach may be optimal. The software development component benefits from iterative sprints; the infrastructure deployment component benefits from sequential, plan-driven execution. An integrated project plan coordinates both streams while allowing each to use the most appropriate methodology for its work.
**Why not A:** Adopting Scrum for the entire project ignores the infrastructure component, which requires sequential, plan-driven execution. Infrastructure work such as hardware procurement, installation, and configuration does not naturally fit into sprint-based iterative delivery.
**Why not C:** Adopting waterfall for the entire project forces the software development component into a rigid sequential process that may not serve it well. Software development often benefits from iterative delivery and feedback, which waterfall methodology does not naturally support.
**Why not D:** Methodology selection should be based on project characteristics, work type, and constraints — not team preference. Letting the team vote without considering which approach best fits each workstream could lead to a suboptimal methodology choice.
Key Concept
This question covers Explain when it is appropriate to use a predictive, plan-based approach under Explain when it is appropriate to use a predictive, plan-based approach (Predictive, Plan-Based Methodologies).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free