Software Development Cross Solution - Index of - Free

Q: If I’m close on my estimates, can I fudge a little and
squeeze something in?
A: We REALLY wouldn’t recommend this. Remember, your
estimates are only educated guesses at this point, and they are
actually more likely to take slightly longer than originally thought than
shorter.
It’s a much better idea to leave some breathing room around your
estimates to really be confident that you’ve planned a successful set
of iterations.
Q: I have a few days left over in my Milestone 1.0. Can’t I add
in a user story that breaks my day limit just a little bit?
A: Again, probably not a good idea. If your stories add up to leave
you one or two days at the end of the iteration, that’s OK. (In Chapter
9 we’ll talk about what you can do to round those out.)
Q: OK, without squeezing my last user story in I end up
coming under my work-day limit by a LONG way. I have 15 days
free at the end of Milestone 1.0! Is there anything I can do about
that?
A: To fit a story into that space, try and come up with two simpler
stories and fit one of those into Milestone 1.0 instead.
Stay confident that you can achieve
the work you sign up for. You should
promise and deliver rather than
overpromise and fail.
Download at WoweBook.Com
project planning
Q: 0.7 seems to add up to a LOT of lost time. What sorts of
activities could take up that sort of time?
A: 0.7 is a safe first guess at a team’s velocity. One example is
where you are installing a new piece of software, like an IDE or a
database (naming no specific manufacturers here, of course). In
cases like these two hours of interrupted work can actually mean
FOUR hours of lost time when you factor in how long it can take a
developer to get back in “the zone” and developing productively.
It’s also worth bearing in mind that velocity is recalculated at the
end of every iteration. So even if 0.7 seems low for your team right
now, you’ll be able to correct as soon as you have some hard data.
In Chapter 9 we’ll be refining your velocity based on your team’s
performance during Iteration 1.
Alright, it’s worth it to me to
lose space miles in Milestone
1.0 to keep things moving.
Let’s do it.
you are here 4 99