Software Development Cross Solution - Index of - Free

different project hurdles
340 Chapter 9
Below are three burn-down graphs. It’s up to you to decide what to do next.
What would you do next?
Here, the team just got finished at the end of the
iteration, so there’s likely nothing you can squeeze in.
However, that steep drop at the end probably means
something was skipped. Testing is going to be vital
after this iteration, and you should probably expect
to schedule some time next iteration for refactoring
and cleanup, to recover from the rush. You could
probably revisit your task breakdown approach, too,
as well as take a look at adjusting velocity.
What would you do next?
In this iteration, things wrapped up early; the
team may have a couple of days at the end of the
iteration. If the project has been ticking along for
a little bit, you may have a backlog of bugs you can
start to tick off. Or, depending on how big your
stories are, you might be able to grab the highest
priority story waiting for the next iteration and
get started on that.
What would you do next?
Download at WoweBook.Com
Nothing! This team is late already. Before the
next iteration, you should look at what caused the
slowdown and whether it’s a velocity problem, an
estimation problem, or something else. Chances are
there’s unfinished code, too, which means there
are going to be bugs coming your way. Make sure
you leave room in the next iteration to cover any
problems that come up.