Agile Estimation

Agile teams need to estimate how much work each task requires. Accurate estimates help teams plan how much they can complete in a given time period.

Why Hours Often Fail

Estimating tasks in exact hours sounds precise, but it often leads to wrong guesses. A task that looks like two hours of work might take five hours once unexpected problems appear. Agile teams instead use relative sizing to compare tasks against each other.

Story Points

Story points measure the size and difficulty of a task compared to other tasks. A team might rate a simple task as 1 point and a complex task as 8 points. The numbers do not represent hours directly. They represent relative effort.

The Fibonacci Scale

Many teams use a number sequence such as 1, 2, 3, 5, 8, 13, and 21 for story points. The gaps between numbers grow larger as tasks become bigger, which matches how uncertainty grows with task size.

Small task:  1 - 3 points
Medium task: 5 - 8 points
Large task:  13+ points (consider splitting)

Planning Poker

Planning poker is a popular estimation game. Each team member picks a card showing a number that represents their estimate. Everyone reveals their card at the same time. Large differences between team members spark a short discussion until the team agrees on a number.

Layman's Example

Imagine guessing how many boxes you need to move your apartment. You compare your apartment size to a friend's apartment that needed ten boxes. If your apartment looks twice as full, you guess twenty boxes. You compare sizes rather than counting every single item in advance.

Key Takeaway

Agile estimation focuses on relative size rather than exact time. Story points and planning poker help teams reach quick, reasonable estimates together.