3 ms·
How many has your team completed on average in the past sprints? It's not pretense. WTF should an engineer care about time? An engineer has to care about Done
by ohthehugemanate 3y ago
How many has your team completed on average in the past sprints?
It's not pretense. WTF should an engineer care about time? An engineer has to care about Done Right. It takes as long as it takes. A PM cares about time, and they can looks at the past history of similar tasks to estimate it very accurately. The abstracted "effort" unit is a way to identify "similar tasks".
It's also very well demonstrated that human brains suck at estimating time. Estimating difficulty is way more consistent.
But if you hate thinking in terms of complexity you can do the same thing by making sure your tasks are evenly sized, and averaging task throughput over time. Or if you also hate your pm you could tag similar tasks and have them do the leg work without the math to help.
- OJFord 3y ago> How many has your team completed on average in the past sprints? In other words 'what is the average conversion from complexity to time'; in other words 'let us try to point time but call it complexity'. > WTF should an engineer care about time? An engineer has to care about Done Right. It takes as long as it takes. That's great, but then #points in a fixed-time sprint should be expected to be all over the place.