01.02.2013 Views

Software Development Cross Solution - Index of - Free

Software Development Cross Solution - Index of - Free

Software Development Cross Solution - Index of - Free

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Deal with velocity BEFORE you break into iterations<br />

A lot <strong>of</strong> this pain could actually have been avoided if you’d applied velocity at the<br />

beginning <strong>of</strong> your project. By applying velocity up front, you can calculate how many<br />

days <strong>of</strong> work you and your team can produce in each iteration. Then you’ll know exactly<br />

what you can really deliver in Milestone 1.0.<br />

First, apply your team velocity to each iteration<br />

By taking the number <strong>of</strong> people in your team, multiplied by the number <strong>of</strong> actual working<br />

days in your iteration, multiplied finally by your team’s velocity, you can calculate how<br />

many days <strong>of</strong> actual work your team can produce in one iteration:<br />

3 x 20 x 0.7 = 42<br />

The amount <strong>of</strong> work, in<br />

The number <strong>of</strong><br />

people on your team.<br />

20 working days in<br />

your iteration<br />

Your team’s first<br />

pass velocity.<br />

Add your iterations up to get a total milestone estimate<br />

Now you should estimate the number <strong>of</strong> iterations you need for your milestone. Just<br />

multiply your days <strong>of</strong> work per iteration by the number <strong>of</strong> iterations, and you’ve got the<br />

number <strong>of</strong> working days you can devote to user stories for your milestone:<br />

42 x 3 = 126<br />

Number <strong>of</strong><br />

iterations in<br />

Milestone 1.0.<br />

Q: That sucks! So I only have 14 days <strong>of</strong> actual productive<br />

work per iteration if my velocity is 0.7?<br />

A: 0.7 is a conservative estimate for when you have new members<br />

<strong>of</strong> your team coming up to speed and other overheads. As you and<br />

your team complete your iterations, you’ll keep coming back to that<br />

velocity value and updating it to reflect how productive you really are.<br />

Download at WoweBook.Com<br />

project planning<br />

person-days, that your team<br />

can handle in one iteration.<br />

Amount <strong>of</strong> work in days that<br />

you and your team can do before<br />

Milestone 1.0 needs to be shipped.<br />

Q: With velocity, my Milestone 1.0 is now going to take 79<br />

working days, which means 114 calendar days. That’s much<br />

more than the 90-day/3-month deadline that Orion’s Orbits set,<br />

isn’t that too long?<br />

A: Yes! Orion’s Orbits need Milestone 1.0 in 90 calendar days, so<br />

by applying velocity, you’ve now got too much work to do to meet that<br />

deadline. You need to reassess your plan to see what you really can<br />

do with the time and team that you have.<br />

you are here 4 93

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!