A Scrum team can be highly productive and still struggle to deliver value quickly.
The team may complete its Sprint Goals, maintain a healthy Product Backlog and regularly produce a usable Increment. Yet that work might then wait days or weeks before reaching the people who need it.
The problem may not be within the team. It may be the wider system around it.
Productivity is not the same as flow
Scrum helps a team organise its work, learn through feedback and create value incrementally.
But Scrum says relatively little about what happens before work reaches the team or after the team completes it.
Finished work may wait for:
- approval
- security review
- integration
- another team
- a release window
- marketing activity
- operational readiness
The Scrum team may appear productive because it completes a large amount of work. From the customer’s perspective, however, very little may have changed.
Lean invites us to look beyond local productivity and examine the flow of value through the whole system.
Local optimisation can hide wider problems
When an organisation focuses on making each team as busy as possible, it may create more work than the wider system can absorb.
Queues grow. Handoffs multiply. Work waits.
This can produce a strange situation: every team appears efficient, yet the organisation as a whole is slow.
The problem is not necessarily that people are working badly. It may be that the system encourages each part to optimise its own activity without considering the movement of work from idea to outcome.
Measure movement, not busyness
A better question is not simply how much work did the team complete?
It is how smoothly did value move from an identified need to a useful outcome?
That shifts attention from individual teams towards the relationships, dependencies and delays between them.
A productive Scrum team is valuable. But team productivity alone does not guarantee an efficient system.
Sometimes the greatest opportunity for improvement lies beyond the team boundary.
This post is part of a series exploring what Scrum leaves unsaid. Scrum provides a deliberately lightweight framework, but it does not attempt to explain every aspect of effective product development. Practices and insights from XP, Lean, Kanban and DSDM can help us understand the technical, organisational and delivery questions that Scrum leaves open.
