(select 2) What are the benefits of cadence and synchronization?

Question

Options

• ASynchronization enables multiple perspectives to be understood, resolved, and integrated at the
• BThey enable systems builders to operate reliably and with certainty within a safety buffer.
• CSynchronization enables reduction in WIP.
• DCadence limits variance.
• ECadence enables variability and makes wait times predictable.

• A
  93% (27)
• B
  3% (1)
• E
  3% (1)

Explanation

Cadence and Synchronization in SAFe/Agile Frameworks

Why A and D are correct: Cadence creates a regular, fixed rhythm that limits variance (D) - by locking in predictable iteration lengths, you remove ambiguity around when things happen. Synchronization serves a different purpose: it brings together multiple teams or workstreams so their differing perspectives can be understood, resolved, and integrated (A), enabling alignment across organizational boundaries.

Why the distractors are wrong:

• B - "Safety buffer" language mischaracterizes the benefit; cadence/synchronization don't inherently create slack or certainty buffers.
• C - Reducing WIP is a Lean/Kanban technique (WIP limits), not a property of synchronization.
• E - This is the classic trap: cadence makes wait times predictable, but it limits variability, not enables it. The first half of E contradicts D, the correct answer.

Memory tip: Split the two concepts cleanly - Cadence = Consistency (limits variance), Synchronization = Shared understanding (integrates perspectives). If an answer says cadence enables variability or synchronization reduces WIP, those are swapped/wrong.

No community discussion yet for this question.