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.

factoring in team performance<br />

76 Chapter 3<br />

Hello?! Can’t we just add some more people to cut down<br />

our estimates? Add two developers, and we’ll get done<br />

in 1/3 the time, right?<br />

It’s about more than just development time<br />

While adding more people can look really attractive at first, it’s really not<br />

as simple as “double the people, halve the estimate.”<br />

Every new team member needs to get up to speed on the project;<br />

they need to understand the s<strong>of</strong>tware, the technical decisions,<br />

and how everything fits together, and while they’re doing that they<br />

can’t be 100% productive.<br />

Then you need to get that new person set up with the right tools and<br />

equipment to work with the team. This could mean buying new licenses<br />

and purchasing new equipment, but even if it just means downloading<br />

some free or open source s<strong>of</strong>tware, it all takes time and that time<br />

needs to be factored in as you reassess your estimates.<br />

Finally, every person you add to your team makes the job <strong>of</strong> keeping<br />

everyone focused and knowing what they are doing harder. Keeping<br />

everyone moving in the same direction and on the same page can<br />

become a full-time job, and as your team gets larger you will find that<br />

this complex communication can start to hit your team’s overall ability to<br />

be productive and develop great s<strong>of</strong>tware.<br />

In fact, there is a maximum number <strong>of</strong> people that your team can<br />

contain and still be productive, but it will depend very much on your<br />

project, your team, and who you’re adding. The best approach is to<br />

monitor your team, and if you start to see your team actually get less<br />

productive, even though you have more people, then it’s time to<br />

re-evaluate the amount <strong>of</strong> work you have to do or the amount <strong>of</strong> time in<br />

which you have to do it.<br />

Download at WoweBook.Com<br />

If it takes you 273 days, with 2 more<br />

people like you, that would reduce the<br />

overall development time by a factor<br />

<strong>of</strong> 3, right?<br />

Later on in this chapter you’ll be introduced<br />

to the burn-down rate graph. This is a great<br />

tool for monitoring the performance <strong>of</strong> your<br />

team.

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

Saved successfully!

Ooh no, something went wrong!