Lecture 02 – HOW TO ESTIMATE AND TECHNIQUES
HOW TO ESTIMATE AND TECHNIQUES
In this lecture, we dive into the intricacies of estimation techniques in Agile development. Explore a variety of proven methods, from story points and planning poker to relative sizing and reference stories. Gain practical insights into when and how to apply each technique effectively, empowering teams to estimate with confidence and accuracy
How to estimate
Estimating work items for new teams get quite difficult as the teams are unfamiliar with the requirements and require solution but over time, as team members get used to the product, they develop a progressively precise sense of how they are going to approach stories and how much effort each user story will take to complete.
As human beings, we are typically good at relatively estimating the items, e.g. we cannot predict at first instance if the Earth is heavier than Mercury, because heaviness is dependent on density which is not a visual thing to determine but we can confidently say that the circumference of Earth is bigger than that of Mercury as size is can be determined easily by visualization. Hence, we can relatively estimate the size of earth in comparison to the Mercury just by looking at it. Let’s consider the image below which shows how the product can be estimated.
Teams across the world use a variety of methods to estimate their work. You just have to find the right way or the way most suitable for your team’s needs. There is no fixed rule for estimation and luckily, we live on a planet where options are not scarce, and this applies to estimation as well.
Estimating effectively in Agile development involves several key steps and techniques:
Understand the Scope: Ensure that everyone involved in the estimation process has a clear understanding of the scope of the work to be estimated. This includes reviewing user stories, acceptance criteria, and any other relevant documentation.
Break Down Tasks: Break down larger work items into smaller, more manageable tasks or user stories. This makes it easier to estimate effort accurately and allows for better granularity in planning.
Choose an Estimation Technique: Select an estimation technique that best suits the needs of your team and the nature of the work being estimated. Common techniques include story points, planning poker, relative sizing, and reference stories.
Collaborate with the Team: Conduct estimation sessions collaboratively with the entire team involved in the work. This ensures that everyone’s perspectives are considered, leading to more accurate and reliable estimates.
Use Comparative Estimation: For relative sizing techniques like story points or planning poker, compare the complexity or effort of the task being estimated to other known tasks. This helps provide context and consistency in estimation.
Leverage Historical Data: Refer to historical data from previous sprints or projects to inform your estimates. This can include actual effort spent on similar tasks or user stories, velocity metrics, or past performance.
Iterate and Refine: Estimation is an iterative process. As you gain more experience and data, continuously review and refine your estimation techniques to improve accuracy and reliability over time.
Document and Track Estimates: Record your estimates and track them alongside actual effort spent on tasks or user stories. This allows you to compare estimated versus actuals and identify areas for improvement.
Review and Reflect: After completing the estimation process, take time to review and reflect on the estimates with the team. Discuss any discrepancies or challenges encountered and identify lessons learned for future estimation efforts.
By following these steps and leveraging appropriate estimation techniques, Agile teams can estimate work effectively, enabling better planning, decision-making, and delivery of value to stakeholders.