Burndown Chart 20%

Your burndown should start with whatever the team forecasts for the upcoming sprint.   There is no concept in Scrum for additional Sprint Backlog items in case the team completes items early.

To better identify additional work that is brought into a sprint due to excess capacity, you may want to research burnup charts.

The essential thing is that the Development Team must have a view of how much work they believe remains in a Sprint. The purpose of having this view is so that the team can demonstrate and evidence Sprint control. A burnup or burndown chart can help with this, but there is no prescriptive practice. 

In fact, there should not be more items in the sprint backlog than what the Dev Team agrees as the work to be done in that sprint. If, for any reason, there is capacity for more work items at the end of the sprint, it is down to the Dev Team to work with the Product Owner to decide which items from the product backlog can still be added to that sprint. The final word is given by the Dev Team.

Mind you that adding / excluding work from a running sprint is not a good practice, as not only it jeopardizes the predictability of the team capacity but it also negatively impacts other factors, such as the team confidence in its own work.

One more scenario to this, what if you fail to complete additional tasks ? You would say that team completed the forecasted backlog and hence the sprint was successful even if additional items are not done. on the contrary if you manage to complete these additional items then why would you add them up to your success :-)

Hi Guys,

Thanks you very much for your anwsers