Leadership mentions SAFe® for coordinating several civic digital teams and asks how it differs from single-team Scrum. What CAPM-appropriate distinction applies?
Select an answer to reveal the explanation.
Short Explanation
SAFe is the multi-team stadium version—extra layers, roles, and ceremonies stacked on top of team agile ideas. Single-team Scrum does not already ship with RTE and PI planning as its core kit. Recognize the scaling add-ons; do not deep-dive the whole playbook.
Full Explanation
When leadership mentions SAFe® for coordinating several civic digital teams, the CAPM-appropriate distinction is that SAFe® is a scaling framework that adds layered roles and ceremonies beyond single-team Scrum components. Associates should distinguish those scaling components from team-level Scrum, not implement RTE practices as if taking a SAFe credential exam. SAFe does not erase backlogs or equal Kanban WIP limits alone.
Claiming SAFe® deletes all backlogs and forbids any iteration cadence fails conceptually because scaling frameworks still use backlogs and cadences; they add coordination layers. Claiming SAFe® is identical to Kanban WIP limits with no additional constructs fails because SAFe includes much more than WIP caps. Claiming single-team Scrum already includes RTE and PI planning as required core events fails because RTE and PI planning are scaling constructs, not basic Scrum essentials.
Exam caveat: At outline depth, identify SAFe as scaling beyond single-team Scrum—without requiring practitioner-level SAFe implementation detail. Operational check: if multiple civic teams need alignment, discuss whether scaling ceremonies are warranted; keep single-team Scrum vocabulary accurate when only one team is in scope.