Burndown

[KellSilveira]

Hey! How to Create a Scrum Sprint Tracking Chart My team has an existing report in Excel that I'm trying to revamp in Power BI that uses a burndown chart. Thanks in advance for any help

• Sprint total de 5 dias
• horas orçadas
• horas de corrida                                                                                                                

https://1drv.ms/u/s!Aj3tDf4ersZ_ol6M5228wXeyerKu?e=NDV2PV  

[v-jayw-msft]

Hi @KellSilveira ,

You have three values in your screenshot but only one working time column in your table.

Can you describe how these three values are obtained?

Best Regards,

Jay

[KellSilveira]

Hi @v-jayw-msft ,

Follow the rationale in Excel (I need to reproduce this chart in Power BI). https://1drv.ms/x/s!Aj3tDf4ersZ_pGSZpmE5rxTUHkww?e=Pd3X58 

Graphic

On the vertical axis, the sum of budgeted hours needed to carry out the activities of the current iteration (eg, sprint 22.23) and, on the horizontal axis, the work days of the iteration.

This graph is represented in two lines. The first is the ideal line (budgeted hours), straight, from top to bottom, representing the complete demand for work at the beginning of the project (top left) and going to the lowest point on the right, where the forecast completion of the sprint on the schedule.

The second is the actual line (in my case, hours executed), which reveals how the team behaved in relation to the projection of time usage for demand during the sprint selected in the segmentation.

In the pbix file the Task Creation Date, Column (Task Created At) and Completion (Task Due At) 

[KellSilveira]

Hi

Complementing

Graphic

On the vertical axis, the sum of budgeted hours needed to carry out the activities of the current iteration (eg, sprint 22.23) and, on the horizontal axis, the work days of the iteration.

This graph is represented in two lines. The first is the ideal line (budgeted hours), straight, from top to bottom, representing the complete demand for work at the beginning of the project (top left) and going to the lowest point on the right, where the forecast completion of the sprint on the schedule.

The second is the actual line (in my case, hours executed), which reveals how the team behaved in relation to the projection of time usage for demand during the sprint selected in the segmentation.