Why Weekends Matter
summary
A vendor asks to exclude weekends from lead-time metrics so a team’s performance review looks better and the proposal claims reduced cycle time; the concrete counterclaims are threefold: questioning assumptions (which hours, holidays, sick days, actual hours), measurable gaming of timesheets and resource allocation (people claiming 100% of time on one project), and customer-facing duration harm — lead time predicts delivery probability, e.g. 95% of work in 15 days, so include weekends for credible, usable metrics.
AI-written summary · about
chapters (9)
- 0:00Why Weekends Matter
- 0:25HADJOB PERFORMANCE REVIEW
- 0:55Metrics are based on assumptions
- 1:41YOU HAVE A 40 HOUR WORK WEEK?
- 1:57The numbers will be gamed
- 2:58People will do everything to meet the target
- 3:13Customers care about duration
- 3:59Lead Time doesn't do start-stop-start-stop
- 4:30There will always be variability
related talks
01h 32mPNSQC 2014 - Hillel Glazer
20mEvangelizing the SRE mindset
54mManaging Misaligned Stakeholders
29mNot All Minutes Are Equal: The Secret behind SLO Adoption Failure
46mCracking the cadence of your software engineering 1:1s
05mNo estimates? Try Flow Metrics.
06mDelivery Metrics: the good, the bad, and the totally ridiculous
51mThe astonishing value of speed