←back to thread

When did estimates turn into deadlines?

(domainanalysis.io)
318 points alexzeitler | 6 comments | 19 Nov 24 20:03 UTC | HN request time: 0.803s | source | bottom
Show context
nextworddev ◴[19 Nov 24 22:00 UTC] No.42188568[source]▶
Multiply your original estimate by 3, works most of the time
replies(6): >>42188708 #>>42188717 #>>42188735 #>>42188830 #>>42189092 #>>42189098 #
1. loloquwowndueo ◴[19 Nov 24 22:18 UTC] No.42188708[source]▶
Montgomery Scott recommends 4 instead.
replies(3): >>42188743 #>>42188747 #>>42189013 #
2. ◴[19 Nov 24 22:22 UTC] No.42188743[source]▶
3. ben_w ◴[19 Nov 24 22:23 UTC] No.42188747[source]▶
A friend suggests doubling the number and increasing to the next unit — hours become days, days become weeks, etc.

I've certainly seen some environments — plural — where a task that should take 1 hour actually takes 2 days, and one that should take 2 days takes 4 weeks.

replies(1): >>42207013 #
4. ikiris ◴[19 Nov 24 23:04 UTC] No.42189013[source]▶
By the book admiral, hours could seem like days.
5. mmcdermott ◴[21 Nov 24 18:14 UTC] No.42207013[source]▶
> A friend suggests doubling the number and increasing to the next unit — hours become days, days become weeks, etc.

I don't know. Going from 8 hours => 16 days seems like quite the markup.

replies(1): >>42208329 #
6. ben_w ◴[21 Nov 24 20:32 UTC] No.42208329{3}[source]▶
The biggest surprise to me was the project managers and leads who refused the opportunity for going from the big numbers to the small one by allowing a faster development architecture.