Skip to main content

Agile Story Point Estimation Techniques - T-Shirt Sizing by - Ankur Mistry

In my previous articles, we have discussed Agile Story Point Estimation and Agile Story Point Estimation Techniques - Planning Poker. In this article, we will learn Story Point Estimation using T-Shirt Size Technique.

What is T-shirt sizing?T-shirt Sizing is one of the Story points sizing technique to estimate user story usually used in agile projects. It's a relative Estimation Technique.

Rather than using a number of planning pokers, here, Items are classified into t-shirt sizes: XS, S, M, L, XL.

The term originates from the way T-shirt sizes are indicated in the US. Rather than having T-shirts in sizes 4, 5, 6 etc, there are just a few sizes: Small (S), Medium (M), Large (L) and Extra Large (XL) and so on.

With T-shirt measuring, the development team is made a request to evaluate whether they think a story is extra-small, small, medium, large, extra-large, or double extra-large. By expelling the numerical score, the development team is allowed to think in a more dynamic manner about the exertion associated with a story. The sizes can, if necessary, be given numerical value after the estimation is finished.


Image Source: http://www.deltamatrix.com/agile-estimation/Steps
  1. Make S, M, L, XL Cards
  2. Product Owner will explain the story to be estimated and the development team will ask questions if they have any issues or unclarity. For example,

    Design Related- Do we have to learn new things before starting the design/HTML/jQuery etc?
    Coding Related- Do we have any code class library ready or we have to write it from the scratch?
    Testing Related- Any specific setup required for Unit testing?
  3. Each developer gives each story a t-shirt size.
  4. All in Development team will raise their cards simultaneously.
  5. The development team will discuss the differences.
  6. The product owner explains the story further or clarifies misunderstanding if any.
  7. The team will Go back to Step 3-Step5 until all are agree with one size.
  8. Complete or place the stories in size buckets.
  9. Estimate the time to complete all stories in S, M, L, XL buckets.

     
    Image source :https://www.slideshare.net/agiledad/agile-estimating-planning 
Benefits
  • This is a very informal strategy and can be utilized quickly with a large number of items.
  • It is a popular agile relative estimation technique.
  • Forcing the estimate into one of a fixed set of sizes allows the process to go quickly
  • It is a good way to Introduce terms to relative estimating.
  • It is very effective for affinity estimating
T-shirt sizes can be a great way to becoming familiar with relative estimating. So, start with them if your dev team finds that easier.
But However, insignificantly put some fundamental numbers on them (e.g., Medium=5) and after that steadily shift to using the numbers directly.

I hope you like this article. stay tuned for more article on Agile Development. If you have any query, please feel free to post in the comments section.

Reference 
  • http://www.deltamatrix.com/agile-estimation/ 
  • https://www.mountaingoatsoftware.com/blog/estimating-with-tee-shirt-sizes
  • https://blogs.msdn.microsoft.com/oldnewthing/20090512-00/?p=18293
  • https://www.slideshare.net/agiledad/agile-estimating-planning

Comments

Post a Comment

Popular posts from this blog

What is User Story ?

A User Story is a short description of something that your customer will do when they come to your website or use your application/software,  focused on the value or result they get from doing this thing. User stories are: written from the point of view of a person using your website or application written in the language that your customers would use. Three C’s of the user story: Card – stories are traditionally written on note cards, and these cards can be annotated with extra details Conversation – details behind the story come out through conversations with the Product Owner Confirmation – acceptance tests confirm the story is finished and working as intended. Template for User Stories : A user story template often uses the following type of format: As a <role> , I want <feature> so that <reason> . Examples of user stories are: As a  user , I want  to upload photos  so that  I can share photos with others . A...
1 comment
Read more

Retrospective Meetings By:Namrata Parik

This article talks about the least important meeting in a Sprint, the retrospective meeting, at  least as considered by the business and sometimes also by the developers. It is often considered to be a waste of time and given the least priority, and sometimes even omitted if there are time constraints. In fact it is the most important meeting but does not show any immediate business value. Talking about my own experience, we were newly into the project and the geek in the team was not getting enough technical tasks to devour, resulting in not so good documentations by him and his general disinterest in the team. This was discussed in the retrospective and his problem was faced, assessed and solved within a span of two weeks (a single Sprint), and he was given enough tasks to fulfill his coding appetite, resulting in better output by the entire team. Talking about retrospective techniques, the most effective way to conduct a retrospective is the Timeline Review. The te...
Post a Comment
Read more