Software Development Cross Solution - Index of - Free

performance and burn down
Work
left
0
44
The total work
left in the
iteration for all
of your team
20
104 Chapter 3
You were asked to take a few minutes to glance over the burn-down graph below and describe
what you think the different parts of the graph are for and how it is one of the key tools for
monitoring your software development progress and ensuring that you deliver on time.
Burn Down
Each unit is a day of work
left on your user stories,
starting at the total days
at the top and decreasing
to 0 days at the bottom.
What do you think would
be measured on this
graph, and how?
This graph monitors how quickly you and
your team are completing your work,
measured in days on the vertical axis.
This chart then plots how quickly you
tick off your work remaining against the
number of days left in your iteration.
The ideal
task burndown
rate
15 10 5
0
Days left
You’ll plot your work against
the days left. Plots above
the line mean you’re a bit
behind schedule.
If you’re plotting
below the line, you’re
ahead of schedule.
Days left in this iteration
We’ll talk a lot more about burndown
in the next few chapters.
Don’t worry if you’re still a little fuzzy
on how burn-down rates work, and how
to track it. You’ll start creating a chart of your own in the
next chapter, tracking your project’s progress.
Download at WoweBook.Com