Estimation Summary
We programmers estimate stories in points, based on perfect engineering time, and we keep track of how many points we can do in each iteration. That lets our customer steer us to success by choosing the best combination of stories given the time and money available.
Except at the beginning, most stories are best estimated by comparing them with other stories already completed, and giving them points according to their relative size. It turns out, as you'll find, that programmers are generally very good at making this comparison. Sometimes, at any stage in the project, stories will come along that you're not ready to compare. In this case you do a spike solution, a quick experiment that prepares you to estimate.
Even the strangest ...
Get Extreme Programming Installed now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
