-
Suggestion
-
Resolution: Fixed
-
None
-
None
- The Velocity chart will show amount of the Backlog item estimation statistic from Sprint to Sprint
- The graph is bucketed by Sprint
- For each Sprint the velocity is equal to the sum of the backlog item estimate for all issues that are in the last column at the end of the Sprint
- Would also show the sum of estimation statistic committed to during the Sprint (i.e the ones that did not get done)
- The PBI estimate used is from the time the issue was added to the Sprint (i.e at the start of the Sprint if the item was in at Sprint start or at the time it was added in the middle of the Sprint)
- The graph is followed by a table that describes the values shown in the table
- For each Sprint a row is shown along with the sum of completed and non completed PBIs, hyperlink to the Sprint report
- A link is provided to the detailed Sprint burndown for that Sprint
- For now hardcode to last 7
- is related to
-
- Closed
[JSWSERVER-4916] Implement the Velocity chart
Needs line for zero on the chart - negative values make for a pretty unreadable chart.
Terminology guidelines would make this:
Use the Velocity Report to track the the amount of work completed from sprint to sprint. The average amount of work completed is the velocity and estimates the work the team can realistically achieve in future sprints.
"Use the Velocity Report to track the the amount of work completed from Sprint to Sprint. The average amount of work completed is the Velocity and estimates the work the team can realistically achieve in future Sprints"
"If a user changes their estimate statistic, historical burndown data will be a bit meaningless. We will just display zero on the velocity chart for those sprints, though we might want to flag this as a warning to the user." - Ian
This is not on default