|
|
|
|
|
|
by xwdv
1067 days ago
|
|
|
This is only a guideline, don’t treat it like a hard rule. There could easily be good reasons why a 2 point story took three weeks. Also gotta stop the negative bias. People will want to complain easily if your 2 point story takes you three weeks, but no one will be singing praises if your 5 or 8 point story is done in a day. |
|
|
If it was an estimation failure, that really needs to be looked at and learned from.
I find that this is typically a problem with management and/or process, not the engineer. We as an industry typically do not respect the time it takes for engineers to produce an accurate estimate. This time itself needs to be treated as a first-class concept and time needs to be allocated to it which, in practical terms, often means it needs its own task/card/story/ticket/whatever in the framework of one's choice.
There are nearly always unknowns (typically some kind of externality or legacy code) to explore before we really know how much time something will take.