4 ms·
I think this comes down to the idea that estimates are really for coordination. At least, I think that’s the best reason for using estimates. I wrote somethin
by bobm_kite9 7y ago
I think this comes down to the idea that estimates are really for coordination.
At least, I think that’s the best reason for using estimates. I wrote something about this here:
https://riskfirst.org/Estimates https://riskfirst.org/Estimates
- bobm_kite9 7y agoActually I don’t really understand why all the HN posts on agile just devolve into a discussion about the difficulty of estimating. Surely there’s more to it than that?
- ahelwer 7y agoWell, standup is also terrible. In addition, there's the general agile assumption that developers are capable of consistently producing X hours of work per day. Maybe it's just me, but I'm a bit more burst-y with my work habits than that.
- majikandy 7y agoI wouldn’t say Standup is terrible but one where you go round the room giving updates is almost useless. It’s not just you, most developers can do 8 hours work in an hour if they aren’t interrupted with meetings.
- Aeolun 7y agoShouldn’t it average out over 2 weeks?
- ahelwer 7y agoNot if you're doing standup every day and expected to report daily progress.