52 lines
1.4 KiB
Markdown
52 lines
1.4 KiB
Markdown
---
|
|
id: 2026-02-04T09:00:00-05:00
|
|
aliases: []
|
|
title: 2026-02-04 09:00:00
|
|
tags:
|
|
- authorship/original
|
|
- destiny/permanent
|
|
- status/draft
|
|
- topic/ergonomics/organizational
|
|
- type/timestamped
|
|
daily: "[[2026-02-04]]"
|
|
dg-publish: true
|
|
---
|
|
# 2026-02-04 09:00:00
|
|
|
|
%%
|
|
Exact time of writing unknown.
|
|
Between [[2026-02-04_08-07-00]] and [[2026-02-04_13-42-00]]
|
|
%%
|
|
|
|
## T-Shirt Sizing
|
|
|
|
"T-shirt sizing" or "T-shirt size estimation"
|
|
is a method of project estimation
|
|
characterized by the use of T-shirt sizes
|
|
representing project scale buckets.
|
|
|
|
> [!example] [T-Shirt Sizing in Agile --- Project Management Pathways](https://www.projectmanagementpathways.com/project-management-articles/tshirt-sizing-in-agile-projects)
|
|
> * **XS (1-2 days):** Simple UI changes or minor bug fixes
|
|
>
|
|
> Example: "Update button color on checkout page"
|
|
>
|
|
> * **S (2-3 days):** Feature enhancements with minimal complexity
|
|
>
|
|
> Example: "Add product sorting by price"
|
|
>
|
|
> * **M (5-7 days):** Features requiring moderate integration
|
|
>
|
|
> Example: "Implement basic search filters"
|
|
>
|
|
> * **L (8-10 days):** Complex features affecting multiple components
|
|
>
|
|
> Example: "Create shopping cart functionality"
|
|
>
|
|
> * **XL (2+ weeks):** Major features requiring breaking down
|
|
>
|
|
> Example: "Implement payment gateway integration"
|
|
|
|
The buckets chosen should be wide enough
|
|
that scale can be confidently estimated
|
|
after minimal investigation.
|