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

User Story In Agile Scrum - By Ankur Mistry

In this article, we will learn what User Story is and how to write one. User Story plays a major role here. It is the part of the Agile process where instead of writing comprehensive requirements, we write a short description of a feature. As the  Agile Manifesto  says 'Working Software' Over 'Comprehensive Documents'. What is User Story? User Story is a short and simple description of the feature or requirements of the project. Generally, user stories are written on sticky notes or index cards as a user or role-based perspective. User Story Template As a < type of user or role >, I want < some goal > so that < some reason >. The template identifies 3 questions - "Who", "What", and "Why". If the team doesn't know these three answers, it means they don't understand the story, and if they don't understand the story, then it's difficult to split it well.   Reference:https://mazoea.wordpres
Post a Comment
Read more

Visual Studio Team Services - Agile - Scrum Project Management Tools

Before starting this article let's understand what is Agile and Scrum.  What is Agile Agile is a  Method  of project management that is characterized by dividing module in to tasks and t asks into short phases of work and frequent reassessment and adaptation of plans. In other words, Agile is a Time Boxed incremental software development method.  What is Scrum Scrum is an incremental agile software development framework  (Agile Framework).   Agile Scrum Process in Short. Product Backlog:  A product owner creates a customer’s wish list and prioritized it and create backlog, called Product Backlog. Sprint Planning:  In this meeting team select small part or module from the Top Priority Wish List of Product Backlog and prepare a small task list. Setting Capacity and Sprint:  Team has to deliver the tasks in 2 weeks or 4 weeks sprint, here Scrum Master bind tasks with Time and User. Scrum Master’s role:  Is to make sure team focused on its goal. End of the sprint:  
Post a Comment
Read more

The Burn Up Charts In Scrum By: Namrata Parik

I would like to propose a less-taken path in my maiden article to track the progress in scrum. We usually do it using the burn down chart which is relatively easier to understand as compared to the burn up chart. These charts help the team and stakeholders to see and track the progress at any point in the release process or sprint. Burn-down chart provides us the information showing the progress based on the remaining hours or story points from top to bottom. (The burn-down chart can be plotted using story points, task count or the remaining effort) This chart is a plot of expected remaining and actual remaining, this is the most used chart in scrum and since it has only two lines it is considered to be a simple chart. It does not cover the scope creep. So sometimes what might look like ‘no work ‘ done by the team may actually be a result of scope creep. The chart below reflects that the team has not done any progress in Sprint 5 and 6 as the story points remain the same. Image
Post a Comment
Read more