In this third and concluding part on the blog series on estimation, we focus on Agile estimation.
The reason we look at Agile estimation in detail is that not only does it offer an interesting and a unique approach to estimation, it also plugs one of the most common loopholes in estimation which is to ignore an individual and/or a team’s capacity that is determined by skill set, experience and speed or performance. In Agile project management, every feature to be implemented is narrowed down and called a story. For e.g., if you are looking at a retail portal, a single ‘Buy product’ page could be the source of hundreds of stories.