# Estimating Projects with Agile

NB: Scroll to the bottom for the short version.

I have a 7 year history of managing projects with Agile. Early, I failed because I didn’t practice Agile seriously. The mistakes I made early on in my Agile career are still being made by numerous companies I work with. So, here I’m giving up the “secret” of why following Agile strictly works. It’s an effort to get there but it is worth it if your business wants to achieve the Agile promise of on-time and on-budget delivery.

## Doing Agile right

I know, I’m opinionated. Most organizations practice a weak form of Agile. When looking at those organizations find out if they’re delivering higher quality software, on-time, on-budget with measurable business value. Here are the key artifacts you get when doing Agile right:
– Consistent iteration velocity
– Green builds
– Low defect kill rate (92%)
– Automated builds
– Low code duplication percentage (<2%)

You have a well functioning team if you have all of these. You are delivering consistently. You will be able to successfully estimate delivery of a new project. Any estimate padding is more of a security blanket or contingency fund. I use 20% to cover for staff changes, holidays, family leave, sick days, etc.

Your estimates will need quite a bit of extra padding if you are missing some. You may need to pad as much as 100% if you aren’t doing any of these.

Commonly, I’m asked how I estimate projects, in terms of both time and money. This is easy if you have reliable Agile metrics. Here’s the process I use:

### Calculating the delivery time

1. Estimate the entire story in points
2. Find your weekly point velocity
3. Divide #1 by #2 to find your realistic delivery time frame
4. Calculate the weekly cost of the development team
5. Multiply #4 by #5 to find your realistic development cost
6. Multiply both values by 1.2 for a 20% padding

#### Example:

1. You’ve rough estimated a project for 160 points
2. Your current team is getting 8 points a week
3. The project will take about 20 weeks (160/8)
4. Padded, this is 24 weeks

### Calculating cost

1. Your entire development team costs \$250K year (small team!)
2. Your cost per week is \$4,807
3. The project will cost \$96,152 (24 * \$4,807)
4. Padded, this is \$115,382 (1.2 * \$96,152)

This is very reliable for me. Many of the details require an experienced Agile manager. Skills required for this analysis:

1. Calculating points for the stories

* This requires skill and experience
* You won’t have all the stories in the beginning. I find that I have about 80% of them though. A 200 point backlog takes me about one week to build.
1. Knowing the average team velocity
* This requires having consistently measured the team.

The three above metrics are built upon solid Agile practice skills:

1. Building and maintaining a backlog
2. Actionable requirements
3. Completing stories on time
4. Focus on quality
5. Ruthless meetings
6. Dedication
7. Commitment

#### Nota Bene:

Many organizations and teams claim to be “Agile”. 99% of them are not. Hire an experienced Agile manager if you want to deliver high quality software, on-time, on-budget, in a repeatable and measurable way.