An Agile Team collects the Iteration Metrics they have agreed upon during which part of the team retrospective?

Question

Options

• ADuring the Features agreement retrospective
• BDuring the qualitative part of the team retrospective
• CDuring the quantitative part of the team retrospective
• DDuring the time and materials retrospective

• A
  3% (1)
• B
  6% (2)
• C
  88% (30)
• D
  3% (1)

Explanation

Agile teams structure their retrospectives into two distinct parts: a quantitative section (reviewing measurable data like velocity, defects, and iteration metrics) and a qualitative section (discussing team dynamics, processes, and subjective feedback). Iteration Metrics - agreed-upon numerical measurements such as story points completed, test coverage, or cycle time - are collected and reviewed in the quantitative part (C) because they are objective, data-driven measures.

Why the distractors are wrong:

• A - "Features agreement retrospective" is not a recognized Agile/SAFe ceremony or retrospective phase; it's a fabricated term.
• B - The qualitative part focuses on feelings, team health, and process observations - not numerical metrics.
• D - "Time and materials retrospective" is a contract/billing concept, not an Agile retrospective phase.

Memory tip: Think "Q for Quantities = Quantitative" - anything you can count or measure (metrics, velocity, defects) belongs in the quantitative part of the retrospective.

No community discussion yet for this question.