17

I have on my project many PBIs and each PBI has tasks with remaining work filled in. I have finished some of my tasks, others are not started and others are in progress.

However, the burndown chart is not showing anything. Not sure exactly what I am missing to configure!

enter image description here

My iterations are like this:

enter image description here

beaudetious
  • 2,354
  • 3
  • 36
  • 60
Luis Valencia
  • 32,619
  • 93
  • 286
  • 506

1 Answers1

22

This has to do with the fact that the burn down needs at least 2 days of data to show something. So basically it won't show any data the first day of the sprint but everything works 'surprisingly' on the second day. This is a longer existing issue as can seen for example on https://connect.microsoft.com/VisualStudio/feedback/details/788378/tfs-ervice-burndown-chart-first-day-work-did-not-get-reflected-in-burndown-chart.

In my current team we will just make the first day of our sprint (when we do the sprint planning) a team day off. This will make sure that the next day the chart is showing. Closing items directly on the day of planning will lower the starting point of the burn down chart. For scrum this is not a real issue because the chart must reflect the work that needs to be done and not the work that has already been done, but for our intern processes this has been causing a lot of confusion in the past.

dennisdegroot
  • 431
  • 3
  • 6
  • Hi @dennisdegroot, any chance you can clarify part of your answer for me, please? We have tried setting our sprints (10 working days) to start the day after planning (so they are really only 9 working days in TFS). This causes the issue described above - the day of planning, and the day after, the burndown chart is empty. Are you manually setting holidays somewhere in TFS for your planning days? Or are you setting your sprints to begin a day later than planning? (thanks!) – Vin St. John Sep 23 '15 at 22:05
  • You are correct. We set the first day of the sprint (when we do the sprintplanning) as team day off. You can do this in the capacity tab. Sadly enough we need to do this manually every sprint. – dennisdegroot Sep 24 '15 at 05:10
  • Seems obvious when you think about it, just not when you first look at it! – Karl Gjertsen Nov 25 '15 at 09:42