CAPM Practice: Explain the components of an adaptive plan
Question 58 of 60 in Explain the components of an adaptive plan
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: SAFe adds program-level Program Increments with PI Planning events, portfolio-level Epics, and Value Streams to coordinate adaptive planning across multiple teams and organizational levels
Explanation
SAFe adds structure for scaling agile beyond single teams: Portfolio (Epics, investment themes), Program (Features, PI Planning), and Team (Stories, Sprints) levels. PI Planning aligns multiple teams on a shared 8-12 week plan, adding coordination mechanisms that individual team adaptive planning lacks.
**Why not A:** SAFe does not replace iteration planning; teams still run their own Sprint Planning within each Program Increment. PI Planning coordinates multiple teams at the program level but does not eliminate team-level ceremonies.
**Why not B:** SAFe incorporates Scrum at the team level but adds multiple additional layers — Program and Portfolio — along with unique artifacts like Features, Epics, and Value Streams that have no direct Scrum equivalent. The two frameworks share principles but are architecturally distinct.
**Why not D:** SAFe is used across industries including hardware, government, and healthcare, and it scales down to organizations with as few as two or three teams. There is no minimum developer count required for adoption.
Key Concept
This question covers Explain the components of an adaptive plan under Explain the components of an adaptive plan (Agile Frameworks/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