Business stakeholders of an agile project frequently skip the review meetings. What should the agile practitioner do?

Question

Options

• AAsk the product owner to inform all stakeholders about the project's progress.
• BSend meeting notes to all stakeholders after each review meeting.
• CInclude the results of the review meetings in the information radiators.
• DConvince the stakeholders of the benefits of attending the review meetings.

• A
  6% (3)
• B
  13% (6)
• C
  2% (1)
• D
  79% (37)

Explanation

Sprint reviews exist specifically for stakeholder feedback - they are a critical feedback loop that shapes the product. When stakeholders skip reviews, the root cause must be addressed directly: stakeholders don't understand or appreciate the value of their participation. The agile practitioner should educate and persuade stakeholders of this value rather than work around their absence. Options B and C (meeting notes, information radiators) are passive workarounds that do not restore meaningful stakeholder engagement. Option A delegates the problem to the product owner without solving it. Only Option D tackles the underlying disengagement.

No community discussion yet for this question.