Sprint Report - Closed and New one
Can you please suggest the best possible Sprint Report examples with:
- Carried over backlog.
- Velocity
- Story Points
- Capacity
What do you hope to accomplish with this "Sprint Report" that can't be accomplished through an effective Sprint Review with active participation from the Scrum Team and key stakeholders?
In a Sprint Review the Product Backlog is updated and nothing is carried over. That's it. The best possible report is no report at all. Who would be reported to and why?
Joining the bandwagon but in a slightly different way.
Can you please explain the best possible reasons for Sprint Reports with:
- Carried over backlog.
- Velocity
- Story Points
- Capacity
Can you provide definitions of Velocity, Story Points, Capacity so that we can all align on your understanding of them?
Can you explain why the Sprint Review is not adequate enough that you need additional reports?
Thanks Thomas, Ian and Daniel for your responses. I have it now.
The interactive transparent monitoring tools used by developers, would it be Burn Down chart, Kanban, Jira output, whatever else, combined with increment of the product and POs feedback about its value and future release is a best report you can think of. PO can aslo have product burn up chart.