←back to thread

When did estimates turn into deadlines?

(domainanalysis.io)
324 points alexzeitler | 3 comments | 19 Nov 24 20:03 UTC | HN request time: 0.611s | source
Show context
ahallock ◴[19 Nov 24 22:20 UTC] No.42188722[source]▶
Working in smaller steps is how you should build software. Constantly get feedback and re-evaluate what you're working on with other members of the team. Instead of giving an estimate, use t-shirt size.

With constant feedback, the whole team is participating in the emergent complexity, instead of being passive and just annoying you with "is it done yet"?

replies(3): >>42188797 #>>42189335 #>>42191436 #
1. dijit ◴[19 Nov 24 22:31 UTC] No.42188797[source]▶
but what if I’m working on something meaningful?

I can’t MVP my way to a simulation physics engine, when each feature or partial feature requires weeks of planning, testing, iterating and tweaking- privately, before anything can be delivered to be used.

Feedback, implies a working widget.

replies(2): >>42188895 #>>42189409 #
2. ◴[19 Nov 24 22:46 UTC] No.42188895[source]▶
3. jeltz ◴[20 Nov 24 00:00 UTC] No.42189409[source]▶
Feedback does not need to be on a MVP, it can be given before that from your fellow engineers. That said there are tasks which really take a lot of research before even fellow engineers can give feedback.