Why would a Release Train Engineer use an Iteration and Program Increment Calendar?

Question

Options

• ATo visualize the Agile Release Train's cadence and synchronization
• BTo know the cycle time between important team and train events
• CTo create a BVIR of the important team and ART milestones
• DTo ensure that key ceremonies don't conflict with non-SAFe ceremonies

• A
  89% (24)
• B
  4% (1)
• C
  7% (2)

Explanation

A Release Train Engineer uses the Iteration and Program Increment Calendar primarily to visualize the Agile Release Train's cadence and synchronization - it gives the RTE and all teams a shared view of when key events (Iteration Planning, System Demos, Inspect & Adapt, PI Planning) occur across the entire train, keeping everyone aligned and in sync.

Why the distractors are wrong:

• B is incorrect because the calendar shows when events occur on a schedule, not cycle time (the elapsed time between events) - cycle time is a flow metric, not what a PI Calendar displays.
• C is incorrect because BVIR (Business Value, Innovation, and Research) is a portfolio-level budgeting concept, unrelated to the PI Calendar's purpose.
• D is partially related but too narrow - while avoiding conflicts is a byproduct of using the calendar, it is not its primary purpose; the calendar's core function is cadence visualization and synchronization.

Memory tip: Think of the PI Calendar as the ART's "heartbeat chart" - its job is to make the rhythm of the train visible to everyone, which is why visualizing cadence and synchronization is always the right answer.

No community discussion yet for this question.