Software Development Cross Solution - Index of - Free

confidence comes at a price
When is your iteration too long?
Suppose you have three developers on your team who are working at a velocity of 0.7. This
means that to calculate how long an iteration will really take your team, you need
to apply your velocity to the iteration’s estimate:
Title:
Description:
Title: Order flight DVD
Description:
Est:
92 Chapter 3
Review flight
Choose seating
15 days
15 days
15 days
Description:
Title:
Est:
Est:
Title:
Order in-flight meal
Description:
Title: Book a shuttle
Description:
Title:
Description: Est:
Est:
Est:
Pay with Visa/MC/PayPal
15 days
15 days
Title:
15 days
Review flight
Description:
Title: Order flight DVD
Choose seating
15 days
15 days
15 days
Description:
Title:
Description:
Est:
Est:
Est:
Iteration 1
55 days / 0.7 =
Iteration 2
50 days / 0.7 =
Iteration 3
58 days / 0.7 =
How would you bring your estimates
back to 20 work-day cycles so you
can deliver Milestone 1.0 on time,
without working weekends?
79 days
72 days
83 days
Even with three
people, we still can’t deliver
Milestone 1.0 in time!
Yes, these estimates are getting
longer...but you’re building confidence
in your estimate along the way.
All three iterations
break the 20 workday
target.
= 234 days of work
So if you have 3 developers, each of them has to work 78
days in 3 months... but there are only 60 working days.
Download at WoweBook.Com