4 ms·
> [it] absolutely ruins my burndown charts any time they're not available. This is the one point where I'm very happy that my work committed to the (legally al
by ThePadawan 6y ago
> [it] absolutely ruins my burndown charts any time they're not available.
This is the one point where I'm very happy that my work committed to the (legally already obligatory) time tracking.
If you do 20h overtime, that just means you spent 20h extra on this sprint, and SP/h should be unaffected (thus also the burndown chart).
- onion2k 6y agoIf you do 20h overtime, that just means you spent 20h extra on this sprint, and SP/h should be unaffected (thus also the burndown chart). In my experience time isn't recorded, or isn't recorded very accurately, especially when it's unsanctioned and unpaid overtime. Burndown charts report the daily change rather than the hourly change. Consequently it looks like stories are moving quickly but really it's just that more effort is being put in every day, but the chart doesn't reflect that.
- ThePadawan 6y agoNow that you mention it, that was also what our burndown charts looked like (unaffacted). Our Scrum Master did use a factor of "actual hours worked vs. planned hours worked" to determine how accurate our SP totals per sprint were. I.e. if we did 100SP in Sprint 1 with no overtime, then 100SP in Sprint 2 with 20h of overtime, we underestimate the SP in Sprint 2. I am generally not a fan of time tracking (especially not down to minute accuracy or per-story), but I see sth. like "8.7 hours worked on Tuesday" as a useful but not misleading measure.