vault backup: 2026-02-17 17:04:56

2026-02-04_09-00-00.md

@@ -7,6 +7,7 @@ tags:
   - destiny/permanent
   - status/draft
   - type/timestamped
+  - topic/organization
 dg-publish: true
 daily: "[[2026-02-04]]"
 ---
@@ -24,28 +25,26 @@ is a method of project estimation
 characterized by the use of T-shirt sizes
 representing project scale buckets.
 
-> [!example]
+> [!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"
+>     Example: "Update button color on checkout page"
 >
 > * **S (2-3 days):** Feature enhancements with minimal complexity
 > 
-> Example: "Add product sorting by price"
+>     Example: "Add product sorting by price"
 >
 > * **M (5-7 days):** Features requiring moderate integration
 > 
-> Example: "Implement basic search filters"
+>     Example: "Implement basic search filters"
 >
 > * **L (8-10 days):** Complex features affecting multiple components
 > 
-> Example: "Create shopping cart functionality"
+>     Example: "Create shopping cart functionality"
 >
 > * **XL (2+ weeks):** Major features requiring breaking down
 > 
-> Example: "Implement payment gateway integration"
->
-> --- [T-Shirt Sizing in Agile --- Project Management Pathways](https://www.projectmanagementpathways.com/project-management-articles/tshirt-sizing-in-agile-projects)
+>     Example: "Implement payment gateway integration"
 
 The buckets chosen should be wide enough
 that scale can be confidently estimated