Tasks done / hours spend

[Rick]

Hi All,

This is my first sprint in agile and need to inform team and stakeholders every day.
Based on the screenshot I have the following questions/problems:
1. If I count the number of tasks I have 47 tasks but in the dashboard it says "36"
2. From the 47 tasks 10 are done but the burndown by taks is not showing it
3. For the tasks done we have entered a value in "work completed" (actual hours) but capacity bar (right top) is not showing it. The 4 hours shown are from a bug we added an estimate figure in. Is the capacity bar shown actual used hours?
4.  If i look on the dashboard to "burn down by task estimate" (not in the picture) I have a simalair line as described in step 2. Can you tell me how this is calculated or what does it trigger?

Regards *newbie* Rick

[Elena Hristova]

Hi Rick,

 Thank you for your interest in TeamPulse. Here is a link to our online documentation for the Dashboard that could help you. However, I will cover your questions in more details bellow:

 1, 2 and 4: On the bashboard you see burndown based on a metric you choose, in your particular case - task count. The burndown shows the work that is left to be done. There are three lines: optimal (black), actual (blue) and trend line (green). Burndowns help you understand the status of the current iteration by seeing a trend of how much work is left to do and when it is forecasted to be completed. Your goal should be to make the actual line reach zero near the end of the iteration.

 3: Iteration minimum and maximum capacity can be set on the View Schedule screen. These are the boundaries that you set in the beginning of each iteration and are mainly used when planning what are you going to work on during the iteration. Currently the capacity is calculated based on the estimate that is put on stories, bugs, issues and risks in the iteration. In future we may make calculation of the capacity configurable, so you are able to choose whether to use task ours, story estimate, or some other metric.

 If you have any other questions or concerns do not hesitate to contact us again.

Greetings,
Elena Peneva
the Telerik team