4 ms·
But sorting issues according to their rough size is precisely what makes at least basic sense. A scale of trivial (can make many of those in a day), simple (sev
by zoul 2y ago
But sorting issues according to their rough size is precisely what makes at least basic sense. A scale of trivial (can make many of those in a day), simple (several of those a day), medium (roughly a day of work) or large (days) makes it possible to have at least basic conversation around work planning. I’m not extra sold about calling those by shirt sizes, but I’m sure we’re on the better end of the absurdity scale here :)
- withinboredom 2y agoAt that point, you are estimating EFFORT, not time. Software engineers are REALLY GOOD at estimating effort. The fact that they translate to time (simple == several days) is ephemeral.
- lomase 2y agoI think that is how Agile is suposed to work. The programmer stimates how hard the task is relative to other task he has done.
- withinboredom 2y agoRight, but they were asked to estimate TIME, not EFFORT.
- kristiandupont 2y ago>Software engineers are REALLY GOOD at estimating effort. The most common problem with estimates is hidden or forgotten complexity, which makes both time and "effort", whatever that means, go up.