# 9 Agile Estimation Techniques

Many people have used a variation of Planning Poker to do Agile estimation.  Here is a reference of 9 different Agile estimation techniques for different circumstances.  I have seen all of these techniques work in practice, except one.  Try a new one each Sprint!

Planning Poker

Participants use specially-numbered playing cards to vote for an estimate of an item.  Voting repeats with discussion until all votes are unanimous.  There are lots of minor variations on Planning Poker.  Good technique to estimate a very small number of items (2 to 10).

The Bucket System

Using the same sequence as Planning Poker, a group or a team estimate items by placing them in “buckets”.  The Bucket System is a much faster Agile estimation technique than Planning Poker because there is a “divide-and-conquer” phase.  The Bucket System can also be used with larger groups than Planning Poker and with very large numbers of items to be estimated (50 to 500).

Big/Uncertain/Small

For super-fast Agile estimation, the items to be estimated are simply placed by the group in one of three categories: big, uncertain and small.  The group starts by discussing a few together, and then, like the Bucket System, uses divide-and-conquer to go through the rest of the items.

TFB / NFC / 1 (Sprint)

This Agile estimation technique is similar to Big/Uncertain/Small but puts a specific “size” into the mix, namely 1 Sprint.  The categories are “Too F-ing Big”, “No F-ing Clue” and “1” Sprint (or less).  I learned this one recently from someone in one of my CSPO classes.

Dot Voting

Dot voting is usually considered a decision-making tool, not an Agile estimation technique.  However, for estimating small numbers of items, dot voting can be a super-simple and effective technique.  Each person gets a small number of “dots” and uses them as votes to indicate the size of an item; more dots means bigger.

T-Shirt Sizes

Items are categorized into t-shirt sizes: XS, S, M, L, XL.  The sizes can, if needed, be given numerical values after the estimation is done.  This is a very informal technique, and can be used quickly with a large number of items.  Usually, the decisions about the size are based on open, collaborative discussion, possibly with the occasional vote to break a stalemate.  There is a brief description of T-Shirt Sizes here.

Affinity Mapping

Items are grouped by similarity – where similarity is some dimension that needs to be estimated.  This is usually a very physical activity and requires a relatively small number of items (20 to 50 is a pretty good range).  The groupings are then associated with numerical estimates if desired.

Ordering Protocol

Items are placed in a random order on a scale labeled simply “low” to “high”.  Each person participating takes turns making a “move”.  A move involves one of the following actions: change the position of an item by one spot lower or one spot higher, talking about an item, or passing.  If everyone passes, the ordering is done.  The Challenge, Estimate, Override and the Relative Mass Valuation methods are variations on the ordering protocol.

Divide until Maximum Size or Less

The group decides on a maximum size for items (e.g. 1 person-day of effort).  Each item is discussed to determine if it is already that size or less.  If the item is larger than the maximum size, then the group breaks the item into sub-items and repeats the process with the sub-items.  This continues until all items are in the allowed size range.

## Principles of Agile Estimation

Agile estimation techniques are collaborative.  All appropriate people are included in the process.  For example the whole Scrum team participates in estimating effort of Product Backlog Items.  Collaborative techniques are also designed so that it is impossible to blame someone for an incorrect estimate: there is no way to trace who estimated what.

Agile estimation techniques are designed to be fast (-er than traditional techniques) and deliberately trade off accuracy.  We are not trying to learn to predict the future… or get better at estimation. Instead, we recognize that estimation is a non-value added activity and minimize it as much as possible.

Most Agile estimation techniques use relative units.  This means that we don’t try to estimate dollars or days directly.  Instead, we use “points” or even qualitative labels and simply compare the items we are estimating to each other.  This takes advantage of the human capacity to compare things to each other and avoids our difficulty in comparing something to an abstract concept (such as dollars or days).

Check out my recent “Agile Planning in a Nutshell” article.

What Other Agile Estimation Methods Are There?  Please let me know in the comments and feel free to include a link!

#### Affiliated Promotions:

Try our automated online Scrum coach: Scrum Insight - free scores and basic advice, upgrade to get in-depth insight for your team. It takes between 8 and 11 minutes for each team member to fill in the survey, and your results are available immediately. Try it in your next retrospective.

# Agile Planning in a Nutshell

Agile methods such as Scrum, Kanban and OpenAgile do not require long-term up-front plans.  However, many teams desire a long-term plan.  This can be thought of as a roadmap or schedule or a release plan.  Agile planning helps us build and maintain long-term plans.

## Agile Planning Process

The steps to do this are actually very simple:

1. Write down all the work to be done.  In Scrum these are called “Product Backlog Items”, in Kanban “Tasks” and in OpenAgile “Value Drivers”.
2. Do some estimation of the work items.  Many Agile estimation techniques exist including Planning Poker, The Bucket System, Dot Voting, T-Shirt Sizes.  These tools can be applied to many types of estimation.  There are three kinds of estimation that are important for Agile Planning:
1. Estimating relative business value.  Usually done with the business people including customers and users.
2. Estimating relative effort.  Usually done by the Agile team that will deliver the work.
3. Estimating team capacity.  Also done by the Agile team (this is sometimes called “velocity”).
3. Create the long-term plan.  Use the team capacity estimate and the sum of all the effort estimates to come up with an estimate of the overall time required to do the work.  (In Kanban, which doesn’t have an iterative approach, this is a bit more complicated.)  Use the business value and effort estimates to determine relative return on investment as a way to put work items in a logical sequence.

Agile planning allows a team to update estimates at any time.  Therefore, the techniques used above should not be thought of as a strict sequence.  Instead, as the team and the business people learn, the estimates and long-term plan can be easily updated.  Scrum refers to this ongoing process at “Product Backlog Refinement”.

## Principles of Agile Planning

In order to use Agile planning effectively, people must be aware of and support the principles of Agile planning:

1. Speed over accuracy.  We don’t want to waste time on planning!  Planning in and of itself does not deliver value.  Instead, get planning done fast and use the actual delivery of your Agile team to adjust plans as you go.
2. Collaborative techniques.  We don’t want to be able to blame individuals if something goes wrong.  Instead, we create safe estimation and planning techniques.  Inevitably, when an estimate turns out to be wrong, it is impossible to blame a single individual for a “mistake”.
3. Relative units.  We don’t try to estimate and plan based on “real” units such as dollars or hours.  Instead, we use ordering, relative estimation and other relative techniques to compare between options.  Humans are bad at estimating in absolute units.  We are much better at relative estimation and planning.

#### Affiliated Promotions:

Try our automated online Scrum coach: Scrum Insight - free scores and basic advice, upgrade to get in-depth insight for your team. It takes between 8 and 11 minutes for each team member to fill in the survey, and your results are available immediately. Try it in your next retrospective.

###### Upcoming Courses
View Full Course Schedule
Disciplined Agile Lean Scrum Master (DALSM)
Toronto
C\$1425.00
Jan 20
2020
Management Consulting for You
Toronto
C\$2500.00
Jan 21
2020
Professional Scrum Master® (PSM I) [PSF Courseware]
London
C\$1525.00
Jan 21
2020
Certified ScrumMaster® (CSM)
Toronto
C\$1595.00
Jan 21
2020
Certified Scrum Product Owner® (CSPO)
Toronto
C\$1795.00
Jan 23
2020
BERTEIG Real Agility Series: Five Essential Agile Tools for Project Managers
Online
C\$0.00
Jan 27
2020
Licensed Scrum Master Product Owner® (LSMPO)
Toronto
C\$1995.00
Jan 29
2020
Agile Coaching at [YOUR COMPANY NAME HERE]
GTA
C\$2000.00
Jan 30
2020
Certified Scrum Professional - ScrumMaster® (CSP-SM)
Online
C\$2199.00
Feb 1
2020
Certified Scrum@Scale Practitioner® (CSaSP)
Toronto
C\$1995.00
Feb 1
2020
Online
C\$1599.00
Feb 1
2020
Agile Coaching at [YOUR COMPANY NAME HERE]
GTA
C\$2500.00
Feb 4
2020
Kanban System Design® (KMP I)
Toronto
C\$1795.00
Feb 6
2020
Professional Scrum Master® (PSM I)
Toronto
C\$1495.00
Feb 11
2020
Leading SAFe® with SA Certification (+FREE Scaling Workshop)
Toronto
C\$1395.00
Feb 11
2020
Certified Scrum Professional - ScrumMaster® (CSP-SM)
Online
C\$2199.00
Feb 15
2020
Management Consulting for You
Toronto
C\$2500.00
Feb 19
2020
BERTEIG Real Agility Series: Scrum and Kanban - A Case Study of Working Together
Online
C\$0.00
Feb 20
2020
Certified ScrumMaster® (CSM)
Toronto
C\$1355.75
Feb 25
2020
Certified Scrum Product Owner® (CSPO)
Toronto
C\$1525.75
Feb 27
2020
Certified Scrum Professional - ScrumMaster® (CSP-SM)
Online
C\$1869.15
Feb 29
2020
Team Kanban Practitioner® (TKP)
Toronto
C\$1015.75
Mar 4
2020
Online
C\$1359.15
Mar 6
2020
Agile Coaching at [YOUR COMPANY NAME HERE]
GTA
C\$2000.00
Mar 6
2020
Online
C\$1359.15
Mar 7
2020
Professional Scrum Master® (PSM I)
Toronto
C\$1270.75
Mar 9
2020
Toronto
C\$1355.75
Mar 10
2020
Online
C\$1359.15
Mar 20
2020
Online
C\$1359.15
Mar 21
2020
Certified ScrumMaster® (CSM)
Toronto
C\$1355.75
Mar 24
2020
Certified Scrum Product Owner® (CSPO)
Toronto
C\$1525.75
Mar 26
2020
Kanban System Design® (KMP I)
Toronto
C\$1525.75
Mar 31
2020
Certified ScrumMaster® (CSM)
London
C\$1525.75
Apr 1
2020
Kanban Management Professional® (KMP II)
Toronto
C\$1525.75
Apr 2
2020
Certified ScrumMaster® (CSM)
Toronto
C\$1355.75
Apr 7
2020
Toronto
C\$1525.75
Apr 7
2020
Team Kanban Practitioner® (TKP)
Toronto
C\$1015.75
Apr 14
2020
Agile Coaching at [YOUR COMPANY NAME HERE]
GTA
C\$2500.00
Apr 15
2020
Professional Scrum Master® (PSM I)
Toronto
C\$1270.75
Apr 20
2020
Leading SAFe® with SA Certification (+FREE Scaling Workshop)
Toronto
C\$1185.75
Apr 21
2020
Certified ScrumMaster® (CSM)
Toronto
C\$1355.75
Apr 21
2020
Certified Scrum Product Owner® (CSPO)
Toronto
C\$1525.75
Apr 23
2020
Professional Scrum Master® (PSM I) [PSF Courseware]
Toronto
C\$1270.75
Apr 27
2020
Coach Skills for the Agile Workplace® (IPC-ACC)
Toronto
C\$2020.00
Apr 27
2020
Toronto
C\$1355.75
Apr 29
2020
Facilitation Skills for the Agile Workplace® (ICP-ATF)
Toronto
C\$1500.00
Apr 30
2020
Certified ScrumMaster® (CSM)
Toronto
C\$1355.75
May 19
2020
Certified Scrum Product Owner® (CSPO)
Toronto
C\$1525.75
May 21
2020
Professional Scrum Master® (PSM I)
Toronto
C\$1270.75
May 26
2020
Professional Scrum Master® (PSM I) (PSM)
Toronto
C\$1270.75
Jun 16
2020