Things You Wish You Shared With Your Team Before They Agreed on That Deadline
summary
Claims specific enough to act on: a year has about 250 working days, a month is under twenty days and a week is often under five useful days because meetings and interruptions cut time; juniors estimate seven days for a week while experienced people use five; “I’ll do it in the meantime” trap kills estimates (Bluetooth tests take hours of waiting but daily setup time adds up); manufacturing can halt for Chinese New Year two-week shutdown, prototypes promised in 9 days may arrive in 14.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:32Three things your team needs to know
- 1:00How many days are there
- 1:48When was the last time
- 2:24Play football
- 3:02Its a trap
- 4:06Mean time
related talks
20mHow long is a piece of string? Solving the conundrum of software estimation
24mCycle Time is the only metric that counts
12mDates and deadlines...it's complicated
47mCreating efficient, accurate, software estimations
36mThe Development Metrics You Should Use (but Don’t)
24mAre You Really Delivering Customer Value?
21mFrom 0 to 60 in 2,592,000 seconds
26mHelp! We have a QA problem