Tracking progress via a burndown chart when sprints overlap
Our team has adopted some agile practices to help us develop and deliver our software to our client. We adopt practices as needed (as problems/challenges were identified) rather than jumping wholesale into the agile camp. The big ones for us are maintaining a product and sprint backlog and developing and delivering new versions in roughly one month sprints. We do estimate the items in our sprint backlog to guesstimate what we can deliver within a sprint. However we do not track progress very well so it’s difficult to know whether or not we are on target.
Tracking progress via a burndown chart when sprints overlap
Our team has adopted some agile practices to help us develop and deliver our software to our client. We adopt practices as needed (as problems/challenges were identified) rather than jumping wholesale into the agile camp. The big ones for us are maintaining a product and sprint backlog and developing and delivering new versions in roughly one month sprints. We do estimate the items in our sprint backlog to guesstimate what we can deliver within a sprint. However we do not track progress very well so it’s difficult to know whether or not we are on target.
Scrum: Capacity vs Velocity when planning a sprint
We have completed 11 sprints so far in our current project. In most sprints we have not been burning down well and usually finish with our velocity gradient flattening as we approach the end of the sprint. However, having looked back at our last few burn downs it seems we are consistent with how much work we carry over to the next sprint.
How to draw sprint burndown chart?
In my company, there are 3 different development teams, newly started scrum. They mainly follow same path in doing scrum, but when it comes to sprint burndown chart, the act differently.