Relative estimating is a method used in project management to figure out how big a project or task will be or how much work it will take. It involves comparing the size or difficulty of a task to that of other tasks in a project instead of trying to figure out its size or difficulty on its own.
This method is often used in the Agile and Scrum approaches to project management, where it is called “planning poker.” Planning poker brings together a group of team members with different skills and points of view to figure out how big a task or user story is. Each person on the team is given a set of cards with numbers on them that show how big or hard the task is. These numbers range from 1 to 20.
The team then talks about the task, and each person chooses a card that they think shows how big or hard the task will be. Then, each team member shares the values he or she chose, and any big differences are talked about. The process is repeated until everyone on the team agrees on how big or hard the task is going to be.
Relative estimating can be a more efficient and accurate way to estimate how long a project will take because it lets the team use all of their knowledge and experience to make better estimates. It also makes sure that everyone on the team has a say in the estimation process and lessens the effect of personal biases.
But there are some things you can’t do with relative estimates. It can be hard to compare tasks that are very different in how hard they are, and it may not give accurate estimates for projects that are very big or complicated. Also, the accuracy of the estimates can be affected by how experienced and skilled the people on the team are who help make the estimates.
Usage
It is used in Agile Project Management
