“The emergent process and work must be visible to those performing the work as well as those receiving the work.” (Scrum Guide)
Cambridge Dictionary: receiving = “getting or accepting something that is sent or given to you.”
Now the uncomfortable Scrum translation: “receiving” is not “watching a demo.”
It’s anyone who must live with what you ship and who can also (partially) change what happens next.
If Scrum feels busy but outcomes feel thin, this is usually where the leak is.
In real product work, the people receiving the work are the users.
Depending your organisation’s structure, people receiving the work may also include:
- support who gets the tickets,
- sales/customer success,
- compliance/security,
- ops/IT,
- managers paying for outcomes.
If your transparency only serves the builders, you’re doing internal theatre. The team sees the work… while the receivers discover reality the hard way: late, via complaints, escalations, or workarounds.
Professional Scrum asks for decision-grade visibility for receivers:
- What changed for them? (not what you worked on)
- What’s actually usable now? (Done, not “done-ish”)
- What trade-offs were made? (scope, risk, quality, rollout)
- What should they decide next? (keep, stop, pivot, invest)
Some practical moves:
- Add an explicit “receiver view” to the Product Backlog/board: one line per item: “If this lands, X can now do Y.”
- Publish a 5-bullet “what changed” note for your Increment, written for the most surprised audience (often support). Link to the evidence (screens, feature flag, release notes, known limits).
- In the Sprint Review, let receivers try the Increment first. Talk later. Watching is cheap; using the Increment reveals truth.
So…
Who is the most ignored “receiver” in your context: users, support, ops, compliance, or the next team in the chain?
And what’s one visibility tweak you could ship next Sprint to make their reality cheaper to see?
I hope you find value in these short articles and if you are looking for more clarifications, feel free to make contact.
Don't want to miss any of these blog posts? Have the “The Scrum Guide Explored” series weekly in your mailbox.
Wishing you an inspiring read and a wonderful journey.
Scrum on!
