Software Development Cross Solution - Index of - Free

esults from an iteration
Your iteration is just about complete...
You’ve made it! You’ve successfully put your process in place: the stories
have piled up in the Completed section of your board, and everyone’s
ready for a little breather. Before people head out for the weekend,
though, let’s do a quick status check:
With testdriven
development
and automated
testing, your
code works...
and you’ll always
know if it stops
working.
318 Chapter 9
What we’ve got
Customer-driven functionality
Compiling code
Monitored builds
Continuously tested code
Solid test coverage
Reliable progress tracking
Pacing that adapts to the team
The burn-down graph and velocity
turn idealistic schedules into real,
quantifiable dates and deliverables.
That’s an impressive list—but don’t turn the
lights out in the office just yet. Suppose all your
hard work has resulted in a day or two to spare
at the end of your iteration. What else could you
do if you had more time?
Skeptical you could have time left?
A good velocity calculation, staying
on task, and accurate estimates will
get you there faster than you think.
Download at WoweBook.Com
User stories and frequent customer
interaction ensure your software does
what the customer wants it to do.
You know if someone tries to check in
code that won’t build—and because of
continuous integration, you know your
code is always buildable.