Vaibhav Sharma
Jul 05, 2024
2,259
15 mins
Have you considered estimating tasks in Agile as selecting a T-shirt size? If you are working on a project, you may try to understand the complexity of it before you start. T-shirt size is used to assign a task a relative T-shirt size based on its relative complexity. It transforms dry estimates into lively debates about whether a feature is a snug small or a roomy XL. It helps prioritize tasks without getting lost in details, much like organizing your wardrobe. Ready to dive into this engaging Agile estimation technique Read on!
As a team owner, I struggled to convey task difficulty until I discovered T-shirt sizing in Agile. This approach helps my team quickly grasp task complexity, aiding in effective planning and execution. Let us understand more about the T-shirt size estimates and their purpose in task planning.
T-shirt sizing in Agile is a technique to estimate the size or effort needed to complete stories or tasks. It includes assigning the sizes XS, S, M, L, and XL or assigning the Fibonacci sequence 1,2,3,5 or 8.
In simple terms, T-shirt sizing is a project estimation or a capacity planning tool to track effort or time a particular task need.
Let me explain you how agile T-shirt sizing can help your entire team:
1. Project Leads: They can easily understand the team capacity.
2. Individual contributors of a project: communicate their bandwidth of a project clearly.
3. Team Members: Understand which task is completed by whom and by what time.
Based on my experience, this tool is predominantly used by software and engineering development teams. However, I assure that this can be great for any team trying to streamline their tasks.
I use T-shirt size estimates due to its semi-detailed nature of task planning or complexity judging feature. I do not need to sit down and make a detailed plan by fully understanding the task. T-shirt sizing in Agile is my favorite tool because it helped me for the following purposes:
a. Task Prioritization
T-shirt sizing is helpful for teams to understand high-priority tasks early on. Thus, it helped me assign tasks and grade them into small tasks or epics. I would then ask my team to work on these tasks accordingly to deliver it within time.
b. Communication
I do not think anyone in this world is oblivious to the existence of T-shirts! Most of us do know and understand the sizing parameters at least a little better. So, in this case, t-shirt sizing in agile project management helps improve communication among project stakeholders.
c. Capacity Estimation
When individuals understand the sizing criteria of the tasks, they can predict the effort needed. I have used this method to identify my capacity for handling tasks based on sizing during a sprint. Sprint is a time box under which a scrum team performs a chunk of tasks within the specified period.
These are some of the purposes of T-shirt sizing estimation in agile working methods. You can also be a certified scrum master and use T-shirt sizing to its full potential for managing and completing tasks.
Let us first understand the types of T-shirt sizing in Agile that are present: XS, S, M, L, XL, XXL. Now, when I try to segregate the tasks, I follow these criteria:
1. Smaller than XS: A single Task
2. XS: Task with effort 1 (1 is used from the Fibonacci sequence)
3. S (Small): 2 (1 + 1 from the same Fibonacci sequence)
4. M (Medium): 3 (1+2 as obtained from Fibonacci sequence)
5. L (Large): 5 (2+3)
6. XL (Extra Large): 8
7. XXL (Larger than XL): an Epic.
After defining the sizing scale for my team, I try talking with them regarding the time it might take. For larger epics, I usually understand that they are going to take more than 2-3 days.
The next step is to assign each task a value from the t-shirt sizing in Agile while communicating with my team. The last stage of discussion comprises a relative comparison of tasks based on understanding.
The last step acts as a filter so that a S-graded task does not take more effort or time than a L-graded task. This is how exactly a T-shirt sizing estimate works in order to divide difficult tasks based on their complexity.
Depending on my experience, it is generally a collaborative framework. However, one may assign roles to limit the T-shirt sizing in agile estimates; the roles are:
1. For Project Backlogs: The owner of the project may assign T-shirt sizes as they are closest to work.
2. In the case of agile teams, the Scrum master of teams reviews the sizes of the T-shirt previously assigned by a project owner. This action is required before the team goes for a sprint. To get a detailed course addressing your queries, join the certified scrum master certification program and never look back at your career decisions.
3. For general project teams: Each member shares their T-shirt size estimation based on self-understanding.
There may be some other roles that you may implement at your convenience or the complexity of the project.
To understand more about T-shirt sizing and how to efficiently cater to your role, get a CSM certification. This will enable you to understand and appropriately manage teams or create a plan deriving conclusions from T-shirt sizing.
Recommended best practices from me to anyone implementing agile T-Shirt sizing chart are:
1. Always try to limit the sizes of the T-shirt strategy; it is intended to make decision-making easier.
2. Understand that all the estimates are preliminary. Thus, if there are added complexities, keep them in mind and communicate effectively.
3. I always recommend keeping a fixed scope and letting everyone know that beforehand. This ensures that when ideas come from multiple members, we do not sail away from our core mission.
4. You may include many other labels apart from T-shirt sizes to ensure you have more detailed estimates of the tasks.
These are some of the best practices to keep in mind when you consider using T-shirt sizing in Agile.
There are some limitations associated with using the T-shirt size estimation; they are:
1. The relative sizes are based on self-understanding; hence, there may be differences of opinion down the line.
2. Estimation based on size is less accurate than a numerical value assigned to each task.
3. There is no mathematical relationship between the sizes of T-shirts and complexity or effort required for a task as well.
Overall, T-shirt sizing in Agile is a rough estimate, and it is just a qualitative representation of the tasks.
Let us compare the agile T-shirt sizing chart with other estimation techniques for project Management Methodology:
1. Planning Poker Vs. T-Shirt Sizing
Planning poker is a more accurate technique compared to T-shirt sizing. However, it requires a team to jot down the complexities and create a detailed overview. Besides that, T-shirt sizing in Agile takes less time and helps teams adapt to start tasks relatively quicker.
2. Dot Voting Vs. T-shirt Sizing
Dot voting is simpler than T-shirt sizing and it does not require high-level engagement in team discussions. However, unlike T-shirt sizing, Dot voting is more qualitative and provides less accurate estimates.
3. User Story Estimation Vs. T-shirt Sizing
Like T-shirt sizing in Agile, this is a similar approach to assign story points estimation . by breaking a task. For each part of the task completed, you may assign two or more 'story points' to the task. This is a similar approach to T-shirt sizing but provides more precise information regarding task efficiency needs and completion deadline.
For an easier approach, I have designed a table to address the comparison above:
T-Shirt Sizing in Agile | Planning Poker | Dot Voting | User Story Estimation |
Qualitative discussions are needed among team members. | Semi-qualitative discussions require more time. | Do not need any discussions, but it is highly qualitative, self-understanding approach. | Needs a discussion level that is similar to the T-shirt sizing method. |
Do not necessarily go into deeper intricacies needed for a task. | Needs a detailed insight into the task. Planning is made after all the details of the tasks are jotted down accurately. | Depends on individual understanding of the task. | A semi-detailed understanding of the task is needed for making an average estimation. |
Less time-consuming in comparison to others. | Requires more time than all the methods mentioned. | Takes the least time, and it is least accurate among others. | The time taken is almost the same as the T-shirt sizing method. |
Let me help you with a real-life example of a T-shirt sizing approach in the popular software development collaboration platform Github.
GitHub is a leading platform for software development and collaboration efforts. The plan that Github employs is based on breaking down work into small, manageable user stories. GitHub uses both the T-shirt sizing in agile and affinity estimation techniques to enable work progression.
They additionally visualize the task completion and progression in Kanban boards, leveraging several metrics. These metrics generally comprise lead time and cycle time for task completion. Thus, T-shirt sizing is helpful for self-organizing teams to assess their capacity and have a feasible workload for each iteration.
In simpler terms, T-shirt sizing in agile comprises planning the task and estimating its requirements based on complexity. I would advise you to use T-shirt sizing whenever the task is moderately complicated, and you have a large team.
By assigning relative sizes (XS, S, M, L, XL, XXL) or using the Fibonacci sequence (1,2,3,5,8, etc.), you can prioritize tasks, communicate effectively among members, and estimate effort. Use this technique to streamline and address pending tasks or epics with confidence. you can enroll in our Certified Scrum Master Certification.
T-shirt sizing in agile estimation is a collaborative process that includes the entire team responsible for development. During the estimation period, each of the team members discusses the tasks, or story, or epics to share their perspective on size.
Implementing T-shirt size estimates simplifies the discussion of an epic or task with the team. It is also easier for a newcomer to grasp the concept and effectively communicate their perspective with the team.
Yes, assigning T-shirt sizes using agile methodology is virtually ideal for any kind of project. However, for a project that packs more complexity, using other project estimation techniques may prove fruitful.
professionals trained
countries
sucess rate
>4.5 ratings in Google