Schedule a call

It’s crucial for stakeholders to have a good idea of how long a project will take. The first encounter with Agile might raise concerns of uncertainty, but there are ways to address it—which is good news! Estimation techniques are directly related to the velocity of your team, so let’s define that first.


Velocity is the amount of work that can be done in an iteration. It’s used to track how much work you’re getting done, and to estimate the team’s capability going forward.

In this article, we’ll cover the most commonly used velocity estimation techniques in Agile ceremonies, such as Planning Poker, Story Points, and more.

1. Planning Poker

In this technique, each team member receives a set of cards that contain numbers that the team agreed to use as their estimate. Usually, it would be a modified Fibonacci sequence.

Next, the product owner reads a product backlog item and discusses it with the team.

Once each team member decided on an estimate, they pull that card out of their hand holding it so no one else can see it. When everyone has picked an estimate the cards are revealed all at the same time.

If everyone is holding the same number… hooray! We pick that number as an estimate and move on.

But if the numbers are different, the team tries to align their understanding of the task and estimate again until most of them hit the same number.

Planning Poker establishes mutual understanding

While this varies, most teams won’t be perfectly aligned with their estimates. This makes Planning Poker the perfect vehicle for team alignment. Discussing tasks is a great way for the team to learn and discover new perspectives, but you might’ve guessed that it’s time-consuming. As such, Planning Poker is recommended for smaller backlogs.

2. T-shirt size

A less formal and more creative type of estimation where items are estimated in standard t-shirt sizes (XS, S, M, L, XL… ).

Agile estimation is abstract as it is but this takes it to the next level. You’re not even using numeric values. T-shirt size estimates mean that the concept of velocity is almost gone, at least as a single value. We can no longer say that the team velocity is 70 points or 100 points.

Instead, we still can aggregate the data and say that in one sprint the team can deliver 1 XL task, 3 M tasks and 8 S.

It’s a great technique for teams that are new to agile estimations and are having a hard time estimating time/points to complete a story. It’s also great for design estimates. You can’t exactly use comparative estimation for designs, but you can probably gauge whether designing a certain feature is a large or a small task.


Includes tools to maximise your website potential.

3. Complexity Buckets

Complexity Buckets have been used in software development since the 1980s and it’s still one of the most popular methods.

The technique consists of three steps:

  1. The first step is to divide the entire project into smaller tasks and assign them to different categories depending on their complexity level. These categories are called “buckets” or “levels”. There are five levels: Very Simple, Simple, Moderate, Difficult and Complex.
  2. The second step is to estimate how many hours each task will take and what level of expertise will be required for its completion. This can be done by using a simple questionnaire that includes questions about the difficulty of specific tasks (e.g., how complicated is it?) as well as estimates for how many hours each task will take (e.g., how many hours do you think it will take?)
  3. The third step is to calculate an average value based on all answers provided by employees who participated in this estimation process so that everyone has a chance to contribute their knowledge about what needs to be done in order for this project to succeed without any problems whatsoever!

4. Fibonacci Sequence for Story Point Estimation

What is the Fibonacci sequence?

The Fibonacci Sequence is a sequence of numbers where each number is the sum of the previous two numbers. The first two numbers in the sequence are both 1, and all subsequent numbers are calculated by adding the previous two numbers together. For example: 1, 1, 2, 3, 5, 8, 13, and so on.

How does this apply to agile? Finishing a user story estimated with 2 points should be two-thirds of the complexity of a user story with 3 points.

Which agile estimation technique should you choose?

Using different estimation techniques can have a large impact on the velocity of an agile team.

The most common technique is planning poker. It’s approachable, but it’s also not very precise and doesn’t scale well. The other two techniques, story points and t-shirt sizes require more effort but they give you a more specific estimate than planning poker does.

Ultimately, the right choice for your team depends on what you’re trying to accomplish—do you need quick estimates or very precise ones?

Be aware that story point estimates are best used for sprint planning. Bucket systems, dot planning, and t-shirt sizing are better for a roadmap and release planning.

Originally published Jun 05, 2022 4:53:00 PM, updated June 23 2022.

Don't forget to share this post!