Agile Zone is brought to you in partnership with:

I am an author, speaker, and loud-mouth on the design of enterprise software. I work for ThoughtWorks, a software delivery and consulting company. Martin is a DZone MVB and is not an employee of DZone and has posted 83 posts at DZone. You can read more from them at their website. View Full User Profile

"How do you estimate on an Agile project?" by Martin Folwer and ThoughtWorks

  • submit to reddit

If you’re interested in techniques for estimation, you should take a look at this pdf ebook. It contains half-a-dozen essays on estimating in agile projects, drawn from our experiences with a wide range of clients. We explain approaches based on story points and on story counting, which should give you a good overview for you to explore an approach that will work for you.

(Free Estimation Ebook)

Published at DZone with permission of Martin Fowler, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


Ian Mitchell replied on Sun, 2013/05/05 - 2:54am

This is a nice e-book, and is an absorbing read as well as a handy reference. Whichever estimation method is chosen, I think it's important to emphasise the benefits of keeping stories as small as possible whilst still reflecting user value. Some of the teams I work with don't allow stories with point sizes greater than 13 into their Sprint Backlog. This improves flow rate and makes it more likely that any discrepancies will average out. It also encourages a deeper team analysis of the requirements.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.