In the context of a Team Increment, every Iteration each team plans, builds, tests, integrates, and?

Question

Options

• AReorganizes
• BReview their work
• CSets new objectives
• DClears out the backlog

• A
  2% (1)
• B
  92% (59)
• C
  5% (3)
• D
  2% (1)

Explanation

B is correct because the standard Iteration cadence in SAFe (Scaled Agile Framework) follows a defined rhythm: plan, build, test, integrate, and review - culminating in an Iteration Review where the team demonstrates completed work to stakeholders and gathers feedback.

• A (Reorganizes) is wrong - team structure isn't reassessed every Iteration; reorganization is a much rarer, deliberate event.
• C (Sets new objectives) is wrong - objectives are set during Iteration Planning, not as a closing step; the final step is reviewing what was accomplished.
• D (Clears out the backlog) is wrong - backlogs are never truly "cleared"; they are continuously refined and reprioritized, not emptied on a schedule.

Memory tip: Think of the Iteration cycle as a story with a beginning and end - it starts with planning and ends with a review. The sequence spells out P-B-T-I-R (Plan, Build, Test, Integrate, Review), which you can remember as "Please Bring The Iteration Report."

No community discussion yet for this question.