SAFe SSM · Scaled Agile · Supporting Team Events · Bank updated 2026-09-12
SAFe SSM practice questions: Supporting Team Events
5 free questions from 21 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Supporting Team Events section of our SAFe SSM bank (21 questions on this area, which carries 19% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.
1/5 · Supporting Team Events · easy
What best characterizes Backlog Refinement in SAFe?
AAn ongoing activity in which the Product Owner and the team review, split, and estimate Stories to keep the Team Backlog ready for future Iteration Planning
BA dedicated, one-time Scrum event that must occur only on the final day of the Iteration
CA meeting where the Scrum Master/Team Coach alone decides the priority order of Stories to reduce the Product Owner's workload
DAn activity conducted exclusively during PI Planning to prepare Features for the entire Program Increment
Show answer & explanation
2/5 · Supporting Team Events
A Story planned for the Iteration has its code written, but automated tests are not yet complete, as the Iteration Review approaches. What is the most appropriate approach for the team?
AHave the Scrum Master/Team Coach personally complete the missing tests before the Review so the Story can be shown as done
BDemo the unfinished Story as if it were complete to maintain a positive impression with stakeholders, since it will likely be finished soon
CSkip the Iteration Review entirely for this Iteration since not all committed Stories were finished
DDemonstrate only the Stories that meet the Definition of Done and be transparent that the incomplete Story will carry forward rather than presenting it as finished
Show answer & explanation
3/5 · Supporting Team Events
In SAFe's Flow Metrics, what does Flow Velocity measure for a team?
AThe percentage of time a work item is actively being worked on versus waiting in a queue
BThe total number of Program Increment Objectives achieved by the entire Agile Release Train
CThe average number of defects escaping to production per Iteration
DThe number of Stories, or story points, a team completes in a given Iteration, tracked over time to understand throughput trends
Show answer & explanation
4/5 · Supporting Team Events · hard
A team's Flow Velocity looks strong and stable across several Iterations, yet stakeholders report that individual Stories still take a long time to move from 'started' to 'done.' Which combination of Flow Metrics should the Scrum Master/Team Coach investigate together to explain this apparent contradiction?
AOnly the number of Iteration Goals achieved, since that is the sole indicator of delivery speed in SAFe
BFlow Time, which measures how long items take end-to-end, and Flow Efficiency, the ratio of active work time to total time, since high WIP or queues can inflate Flow Time and depress Flow Efficiency even while completed-item counts stay stable
CThe team's estimated story points versus actual story points, since Flow Metrics do not apply to team-level delivery in SAFe
DFlow Velocity and Flow Distribution alone, since Flow Velocity already fully explains cycle time by definition
Show answer & explanation
5/5 · Supporting Team Events · hard
A Scrum Master wants the team to use data during its Iteration Retrospective to drive process improvement. The team's velocity has been flat for three Iterations while a sister team on the same ART reports a higher velocity. Which use of metrics best aligns with SAFe guidance for this Retrospective?
AUse Flow Efficiency data to set individual performance targets for each team member to close during the Retrospective.
BReplace the Iteration Retrospective with a metrics dashboard review, since flow metrics alone provide sufficient insight for improvement.
CExamine the team's own trends in flow metrics, such as Flow Time and Flow Load across recent Iterations, to identify internal bottlenecks and improvement opportunities, without comparing velocity against the other team.
DRank the team's velocity against the sister team's velocity to determine which team is more productive and should be assigned fewer resources.
Show answer & explanation
C is correct. SAFe explicitly cautions against comparing velocity across teams because story-point sizing is relative and team-specific, making cross-team comparisons misleading and potentially harmful to trust and collaboration. Instead, SAFe promotes Flow Metrics (Flow Velocity, Flow Time, Flow Load, Flow Efficiency, Flow Predictability, Flow Distribution) as a more objective, systemic way for a team to inspect its own process trends during the Iteration Retrospective and identify real bottlenecks to address.
↗ the SAFe 6.0 framework (framework.scaledagile.com) + the official SAFe Scrum Master course content — Supporting Team Events
Other SAFe SSM areas
The same kind of free sample for every other section of the SAFe SSM bank:
Study Supporting Team Events with instant feedback
6 free questions · filter study mode by area and difficulty · error log with spaced repetition · no card, no dumps, no ads.
Create your free account →
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by Scaled Agile. SAFe SSM and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official Scaled Agile materials (as of August 2026); always confirm current details with the vendor before booking.