vault backup: 2026-02-04 17:41:43
This commit is contained in:
@@ -89,3 +89,75 @@ incentivize problematic (hare-hunting) behavior.
|
||||
Has such behavior been observed,
|
||||
or has chief strategy been organization-aligned
|
||||
in spite of the incentive?
|
||||
|
||||
## 2025-02-04
|
||||
|
||||
### 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]
|
||||
> * **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"
|
||||
>
|
||||
> --- [T-Shirt Sizing in Agile --- Project Management Pathways](https://www.projectmanagementpathways.com/project-management-articles/tshirt-sizing-in-agile-projects)
|
||||
|
||||
The buckets chosen should be wide enough
|
||||
that scale can be confidently estimated
|
||||
after minimal investigation.
|
||||
|
||||
## 2025-02-04 13:42
|
||||
|
||||
[[fire-alarm-takeoff]]
|
||||
|
||||
> [!quote] Art Baldwin 2026-02-04 (pp.)
|
||||
> Fire, smoke, and combination fire/smoke dampers
|
||||
> may require 120V power, and thus electrical takeoff,
|
||||
> or only 24V, in which case mechanical will own the scope.
|
||||
> Assuming 120V is a budget-conservative estimating convenience,
|
||||
> which is generally considered acceptable
|
||||
> in lieu of determining specified requirements,
|
||||
> but further investigation may be expected
|
||||
> if more than a few per floor are shown.
|
||||
|
||||
## 2025-02-04 17:02
|
||||
|
||||
While observing takeoff for
|
||||
[[electrical-takeoff#Unit Condensing Units|unit condensing units]],
|
||||
the project engineer expressed confusion
|
||||
at the process of calculating average horizontal length,
|
||||
expressing that it was more complicated than they expected
|
||||
considering takeoff procedure for similar processes.
|
||||
The PE asked why we would not simply use the maximum
|
||||
so that we would not risk having too little overall.
|
||||
|
||||
Their expectation surprised me,
|
||||
since it is intuitive to me
|
||||
that there must be some limit to the logic of "covering it"
|
||||
since it is always within our power to add contingency,
|
||||
and especially because, if anything,
|
||||
I feel that our procedures tend towards
|
||||
the upper end of reasonable ECI.
|
||||
(see [[value-of-information.jpg]])
|
||||
|
||||
My response was not well formulated.
|
||||
|
||||
Reference in New Issue
Block a user