Software Project Estimation is Wrong – Part 1

Why estimation is wrong and will hurt you ?

1- Starting with All Our Requirements Is Wrong:
At the very beginning, we know less about our project than we’ll ever know again.

2- Estimating When We’ll Be Done Is Wrong; Forcing the Answer Is Worse:
Developers too, know less about this product than they ever will again, and they don’t understand most of these requirements very well.

3- Agile Teams Work in Short Iterations; They Pick an Amount of Work that They Forecast They Can Accomplish:
If a team has more work thrust upon it than they think they can accomplish, they generally fall short.

4- Having Demanded the Impossible, Management Asks for Better Estimates:


About Ahmed

Software craftsman, programmer, developer, system/business analyst, DBA and PM.
This entry was posted in Agile, Estimation, Lessons Learned. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s