Introduction
“There is no failure. Only feedback.” - Robert Allen (Author)
Sprint reviews represent the opportunity for program leaders to see incremental progress made by teams and, more importantly, learn how they can better support teams during execution.
Decisions to make
- Decide where the teams need help to consistently execute successful sprints, including predictable planning, friction-free value delivery, and effective execution
Context
- Teams have completed their latest iteration/sprint and are now reviewing the work they have done and reflecting on how they want to improve going forward
Why we care
- The lean principle of “go and see” encourages leaders to go to where the work is happening to form opinions on how to help
- The sprint demos are the best place for leadership to stay engaged on team-level progress and learn how they can help
- Teams and programs should seek to optimize the flow of value through the organization by minimizing dependencies between teams
- Continuous improvement can (and should) happen from sprint to sprint, and program leadership should set that expectation and support it with servant-leadership behaviors
The Atlassian view
- While the team is expected to work day-to-day in Jira Software, there is great visibility into the sprint-level work in Jira Align available for program leaders
Next step:
Jobs to be doneWas this content helpful?
Connect, share, or get additional help
Atlassian Community