3 ms·
End of the day, because the estimates are used to figure out what fits in a sprint, which is a unit of time, they’re time estimates. Just all in team-specific c
by quantified 5y ago
End of the day, because the estimates are used to figure out what fits in a sprint, which is a unit of time, they’re time estimates. Just all in team-specific currencies that have a fuzzy exchange rate with time.
- phone8675309 5y agoManagement wants to extract maximum labor from their workers they encourage this fuzziness and second guessing as a way to manipulate their teams into thinking it's their fault or working extra hours to satisfy unreasonable management demands. This is true for all parts of agile as practiced - it's micromanagement by another name.
- lloydatkinson 5y agoYes, perhaps I should have been harsher in my article. I strongly agree with you.
- fatnoah 5y agoI don't think that's the intent, but that's definitely how I've seen it implemented, either through spending lots of time comparing velocities, trying to optimize burndowns, or making equivalencies like 1 point = 1 day (that company also allowed estimating at the 1 hour granularity). That said, when done well, I think there are benefits to elements of Agile, but one really has to buy in to the fact that average velocity or similar metrics far more useful for looking at what might be delivered in several months, not what will be delivered in 2 weeks. It _can_ be done right, but I think that's the exception and not the rule.