Estimation is the process of finding an estimate, or approximation. It is basically an Art of guessing. Estimation includes four main factors – money, effort, resources, and time needed to build a specific system or product. There are many techniques available in today’s world for doing estimations in an Agile Project. The main objective for doing estimations include Relative Estimation, discussions to get more information of items whose estimations need to be done and ensuring the commitment and enthusiasm of the whole team towards the tasks assigned to them.
Agile Project Estimation Techniques are:
- Dot Voting:
In Dot Voting Techniques all the user stories along with their description are posted on the board. Each member out a dot in front of those stories that they consider most important. This way the stories are sorted according to their priorities. This is done to select the most important stories that should be taken forward.
- T-Shirt Size:
This technique helps in open and mutual collaborative discussions. In this technique t-shirt sizes -XS (Extra Small), S (Small), M (Medium), L (Large), XL (Extra Large) are used. User stories are are given t-shirt sizes according to the member understanding. This technique gives rough estimation very fastly.
- Planning Poker:
Planning Poker is the most famous Estimation technique in Agile. This technique makes sure that each and every member participate in estimation and shares his/her opinion. In this technique cards with number on them, are given to each member of the team. Product Owner read the story, after which every member have to hold the card showing the level of efforts they will make for the user story. Discussion and Re-estimation goes on until the whole team reach to a consensus.
- The Bucket System:
The Bucket System estimation technique is much faster than the Planning Poker technique. In this buckets are created with random values: 0, 1, 2, 3, 4, 5, 8, 13, 20, 30, 50. The whole team estimates the items by placing them in these “buckets”. In Bucket System Divide and Conquer approach is followed.
This technique is for doing rough estimation and it is simpler than the Bucket system technique. All the items are categorized in Large/Uncertain/Small. First simple user stories are chosen for estimation then more complex are taken. It’s a good technique when there are comparable items in the Product Backlog.
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Software Engineering | Project size estimation techniques
- Software Engineering | Application Composition Estimation Model (COCOMO II | Stage 1)
- Automation Estimation Tools
- Cost Estimation Models in Software Engineering
- Software Cost Estimation
- Software Engineering | Agile Development Models
- Software Engineering | Agile Software Development
- Software Engineering | Comparison between Agile model and other models
- Techniques to be an awesome Agile Developer (Part -1)
- Agile Software Process and it's Principles
- Agile Software Testing
- Difference between Agile Testing and Waterfall Testing
- Difference between Agile Model and V-Model
- Difference between Agile and Scrum Testing
- Difference between Traditional and Agile Software Development
- Difference between Agile and DevOps
- Agile Methodology Advantages and Disadvantages
- Agile Testing Quadrants
- Disciplined Agile Delivery (DAD) in Software Engineering
- Difference between Agile Testing and V-Model Testing
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.