Demand to value
Every request, from a one-line fix to a cross-organisation capability, travels the same nine stages. Only its size decides which board it lives on.
The nine stages
Capture
Demand from any source enters one front door and becomes a Jira request.
One request formTriage
Kept as ad hoc work, made a story, or routed. Service requests and small changes go to the sprint backlog (planned to the team’s service share guide); third-party changes go to the Supplier board; emergencies pause the sprint; safety-critical items go to the expedite lane.
Size and routeReview
Feasibility and scope. Cross-organisation work becomes a capability on the Network Kanban.
Tech TalkDiscover
User research and prototyping with customers and staff. The PVI and benefit estimate are scored here.
Analyse, prototypePrioritise
The backlog is ordered by the DelPulse Value Index; the Product Manager can move items with a recorded reason.
Score and orderDeliver
Stories are built and configured in sprints.
2-week sprintsAssure
Testing, safety and compliance assessment and change approval as one stage inside the flow.
Test, safety, CABRelease
Deployed in the agreed window, smoke-checked and confirmed with users in live.
Deploy, validateRealise
Benefit measured against the estimate. Feedback and benefits create new demand.
Measure benefitsThe rest of this page is for subscribers
Subscribe to read the other 3 sections of this page:
- Routing at triage
- Work item hierarchy
- Definition of done at each level