Software Development Cross Solution - Index of - Free

Iterations should be short and sweet
So far Orion’s Orbits has focussed on 30-day iterations, with 3
iterations in a 90-day project. You can use different size iterations,
but make sure you keep these basic principles in mind:
Keep iterations short
The shorter your iterations are, the more chances you get to
find and deal with change and unexpected details as they
arise. A short iteration will get you feedback earlier and bring
changes and extra details to the surface sooner, so you can
adjust your plans, and even change what you’re doing in the
next iteration, before you release a faulty Milestone 1.0.
Keep iterations balanced
Each iteration should be a balance between dealing with change,
adding new features, beating out bugs, and accounting for real
people working. If you have iterations every month, that’s not
really 30 days of work time. People take weekends off (at least
once in a while), and you have to account for vacation, bugs,
and things that come up along the way. A 20-work-day iteration
is a safe bet of work time you can handle in an actual 30-day,
calendar-month iteration.
project planning
SHORT iterations help you
deal with change and keep
you and your team motivated
and focused.
Download at WoweBook.Com
30-day iterations
are basically 30
CALENDAR days...
...which you can assume turn
into about 20 WORKING
days of productive
development.
you are here 4 85