Wednesday, January 20, 2016

How to Respond to a Request for Estimates on Software Development

Response to: Do We Really Need Estimates?

I think it is a question of addressing the purpose those see for estimates. If they just say "lots of people do it, so we should" then your answer is fine in my opinion.

If they say they need some way of deciding if doing that work is wise or something that is going to be so difficult that it isn't worth it then a different answer is needed. If they talk about scheduling then other explanations make sense to me - talking about the issues with fixed estimates etc. but giving them alternatives of fixed schedule with variable features (if there is a business need to deliver on some date)., etc.

Related: Agile Story Point Estimation (2012) - Assigning Story Points to Bug Fixes (2011)

No comments: