Stakeholders are the people whose input the product depends on and whose
interests it serves. Scrum gives their participation a specific shape.
Where input enters
Anyone may propose Product Backlog items, and anyone wanting a change makes the
case to the Product Owner. The Sprint Review is the scheduled point where the
Scrum Team and stakeholders inspect the Increment together, discuss what has
changed in the environment, and collaborate on what to do next. The Product
Backlog may be adjusted as a result.
Where the decision sits
The Product Owner decides what enters the Product Backlog and in what order. For
that to work, the organisation must respect the decision. This is the boundary
scenario questions most often probe, usually by giving the stakeholder seniority
or a revenue argument.
The Sprint Review is a working session
It is not a demonstration for sign-off and not a gate. The Increment may already
have been released. What the event produces is a revised Product Backlog and a
shared understanding of what to do next.
The Scrum Master's part
Serving the organisation includes removing barriers between stakeholders and
Scrum Teams, and serving the Product Owner includes facilitating stakeholder
collaboration when requested or needed.
Common misconceptions
“The Sprint Review is a demonstration where stakeholders approve the work.”
It is a working session. The Scrum Team and stakeholders review what was accomplished and what has changed, and collaborate on what to do next. The Product Backlog may be adjusted as a result.
“Stakeholders should be kept out of Scrum events.”
Stakeholders are invited to the Sprint Review by the Scrum Team. The Scrum Master also works to remove barriers between stakeholders and Scrum Teams.
“A stakeholder with budget authority can reorder the Product Backlog.”
Ordering is the Product Owner's decision. Stakeholders influence it by persuading the Product Owner, and the organisation is expected to respect the resulting decisions.
5 questions test this concept
A sales director with revenue responsibility instructs the product owner to move a customer's feature request to the top of the Product Backlog for the next Sprint. What should happen?
AThe product owner complies, because revenue responsibility outranks the product owner.
BThe product owner hears the case, decides, and makes the reasoning visible. Stakeholders influence the order by persuading the product owner, and the organisation is expected to respect the resulting decision.
CThe Scrum Master arbitrates between the two.
DThe item is added to the Sprint Backlog immediately, since it is urgent.