Several city departments want a shared permitting platform and schedule a large, multi-team planning event to align features for the next program increment. Which framework-level component are they adopting that basic single-team Scrum does not include?
Select an answer to reveal the explanation.
Short Explanation
Picture a citywide traffic light sync—lots of crews, one big planning jam. That’s the flavor of SAFe® PI Planning. Plain single-team Scrum never invented that multi-team program event; it stays at one team’s Sprint cadence.
Full Explanation
SAFe® introduces Program Increment (PI) Planning as a cadence-based, face-to-face (or virtual) event that aligns multiple agile teams to a shared vision and PI objectives. Basic Scrum centers on a single Scrum Team’s Sprint events. CAPM depth expects recognizing PI Planning as a scaling-oriented component rather than a native Scrum ceremony.