A team is creating a highly marketed, time-sensitive product. The agile coach is concerned that anything other than exceptional quality will result in bad publicity for the company. What should the…

Question

Options

• AEstablish pair programming partners, and regularly perform peer reviews.
• BPerform demos at the end of each iteration.
• CSend coding to the quality assurance (QA) team upon completion.
• DDemonstrate each feature to the client as soon as coding is complete.

• A
  5% (3)
• B
  77% (48)
• C
  15% (9)
• D
  3% (2)

Explanation

End-of-iteration demos (Option B) provide a regular, structured feedback loop where working software is demonstrated to stakeholders, enabling quality issues to be identified and addressed continuously - not just at the end. This aligns with the agile principle of delivering potentially shippable increments frequently and getting early feedback. Option A (pair programming and peer reviews) improves code quality at the developer level but does not ensure stakeholder validation of the product. Option C (handing off to QA upon completion) is a waterfall-style sequential approach that delays feedback. Option D (demoing each feature as soon as coding is complete) is too granular and bypasses the structured sprint review process.

No community discussion yet for this question.