Skip to main content

T-Shirt Sizing for project estimation

 T-Shirt sizing is a simple yet effective technique used in Agile project management to estimate the effort or complexity of tasks. Instead of using precise numbers, teams categorize tasks into T-shirt sizes (such as Small, Medium, Large, etc.) based on their relative size or complexity. Here’s how it works:

  1. Assigning T-Shirt Sizes:
    • Each task or user story is assigned a T-shirt size (e.g., XS, S, M, L, XL, XXL).
    • These sizes represent a range of effort or complexity.
    • For example:
      • Small (S): Quick and easy tasks.
      • Medium (M): Moderate effort or complexity.
      • Large (L): More involved tasks.
      • Extra Large (XL): Very complex or time-consuming tasks.
  2. Relative Estimation:
    • T-Shirt sizing focuses on relative estimation rather than precise numbers.
    • Team members compare tasks to each other and decide which size best fits.
    • It allows for multidimensional thinking beyond just time estimates.
  3. Benefits of T-Shirt Sizing:
    • Simplicity: Everyone understands T-shirt sizes (like the difference between an XS and an XL shirt).
    • Clear Communication: Team members can express their bandwidth and priorities clearly.
    • Capacity Planning: Project leads can gauge team capacity effectively.
  4. Example:
    • Imagine a content team estimating the effort for writing articles:
      • Writing a short blog post: Small (S)
      • Creating a comprehensive research article: Large (L)
      • Developing an extensive whitepaper: Extra Large (XL)

5.      Here are some examples of t-shirt size ranges:



o   X-small: 0.5 to 1 days

o   Small: 1 to 2 days

o   Medium: 3 to 5 days

o   Large: 5 to 8 days

o   XL: 8 to 13 days

 

Comments

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .