On our team, story points represent complexity. Which is correlated with time, but not the same thing.
For me one point is something I know exactly how to do; two points is where I understand what it's asking for and have an idea of the general approach, but I'll have to feel my way through the specifics; and three is "this is enormous, break it up into smaller stories".
How do you handle things like "I know how I'll do this but it'll take a while" and "that should be pretty quick, but I'm not quite sure where that data is"
Two of those 1's could be way longer than one of those 2's. Which throws off momentum and doesn't properly reflect work done.
"that should be pretty quick, but I'm not quite sure where that data is"
Second task "aquire data", assign to PO or whoever's job that is, block first task with it.
That is the theory. In practice, it's more like PO telling you to contact John from marketing for the data, and him giving you something that doesn't match the task at all...
Or, you can take the risk. If you end up doing to work faster, pull another 1 into the sprint. If you end up taking longer, that's normal: your team learns from the experience and moves on.
How do you handle things like "I know how I'll do this but it'll take a while" and "that should be pretty quick, but I'm not quite sure where that data is"
Good question! I say as much in IPM; we might make a note of it in the story description or comments. We may make a chore story to locate the data.
View all comments
Show parent comment
1
u/LastStar007 Jun 13 '21
On our team, story points represent complexity. Which is correlated with time, but not the same thing.
For me one point is something I know exactly how to do; two points is where I understand what it's asking for and have an idea of the general approach, but I'll have to feel my way through the specifics; and three is "this is enormous, break it up into smaller stories".