Software Development Cross Solution - Index of - Free

Recalculate your
estimates and
velocity at each
iteration, applying
the things you
learned from the
previous iteration.
We can fit more user stories in this next
iteration, right? We should have gotten over a
lot of setup stuff, and understand the overall
app better now, right?
You need to revise your story and task
estimates and your team’s velocity.
When originally planning Orion’s Orbits, you and
your team came up with estimates for each of the user
stories for Version 1.0, and then the tasks associated
with each of those user stories. Now that it’s time
to kick off another iteration, you have a lot more
knowledge about how things will work. So it’s time to
revisit those estimates for the remaining user stories
and tasks.
Also, when you originally calculated how much work
you could complete in the first iteration, you didn’t
know how fast your team could develop software and
complete their tasks. You probably used an initial value
of something like 0.7 for your team’s velocity. But that
was just a rough guess...now, you and your team have
completed an iteration. That means you’ve got hard
data you can use for recalculating velocity, and getting
a more accurate figure.
Remember, your estimates and your velocity are about
providing confident statements to your customer about
what can be done, and when it will be done. You
should revise both your estimates and your velocity at
every iteration.
Download at WoweBook.Com
the next iteration
Velocity accounts
for overhead in your
estimates. A value
of 0.7 says that
you expect 30% of
your team’s time to
be spent on other
things than the
actual development
work. Flip back to
Chapter 3 for more
on velocity.
you are here 4 353