Relative Estimation - The Right way of using Story Points for Agile Teams

Businesses need an estimation to be able to forecast when a story or feature will be ready. On the other hand, development teams are not comfortable to estimate! This is an ongoing conflict between business owners and development teams.

In this video, I explain what relative estimation means, how it should be calculated by all team members, and what will impact on relative estimation.

There are 4 factors that influence on relative estimation:
1. The amount of work
2. Complexity
3. Knowledge and what we know about the job
4. Risk and uncertainty: What we don't know about the job

For further details about what we do in Sprint Agile, please have a look here:

[bullsfan]

This is not relative estimation. Proposing that an estimate of 3 is 3x the size and complexity of a 1, or a 2 is 2x the size of a 1, implies a level of exactness that simply isn't there.

All we are saying is that a 3 is larger than a 2, and a 2 is larger than a 1.

[wiseenterprise]

I have seen story points used wrongly so often. People covert it to days or hours. But that's wrong