4 ms·

Furthermore, and I find it odd that us smarty pants math people keep forgetting this. Numbers make decisions easily justifiable. Those story points, those days

Furthermore, and I find it odd that us smarty pants math people keep forgetting this. Numbers make decisions easily justifiable. Those story points, those days tracking roadblocks. All that data, weather it's wrong or right, allows people to make decisions where they would otherwise have to justify with nebulous reasoning. The down side is, our point keep doesn't explain the reasoning behind delays and other bad numbers. Hopefully, we get better at quantizing this shit, but it's not going to go away. Their is something like a gravitational force in accountability. Those who can shirk it, to others or to numbers, must shirk it to have more power. And honestly I'd rather blame numbers rather than people, the impersonality of bad numbers allows you retro without personal attacks and defensiveness, which allows more rapid improvement.

runawaybottle 7y ago
So here’s a question for you. I notice that during our sprint planning, some team members create almost 50 user stories. I probably create 1/6 of that. Do you think it would bode well for me to create more user stories so that I can mark it as ‘done’, so when the numbers are rolled up I can look great and avoid the mass culling that seems to be a forgone conclusion given the system that encourages this kinda nonsense?
- deanCommie 7y ago
  That's not how...any of that works. 1 - their stories are likely smaller than yours. 2 - you estimate TOGETHER, in a shared common estimation system 3 - what is meant to be tracked is the total collective TEAM velocity, not the velocity of an individual team member
- rumanator 7y ago
  > Do you think it would bode well for me to create more user stories so that I can mark it as ‘done’ User stories are only a way to gather requirements for a feature and set a definition of done. They have nothing to do with productivity.

runawaybottle 7y ago

So here’s a question for you. I notice that during our sprint planning, some team members create almost 50 user stories. I probably create 1/6 of that. Do you think it would bode well for me to create more user stories so that I can mark it as ‘done’, so when the numbers are rolled up I can look great and avoid the mass culling that seems to be a forgone conclusion given the system that encourages this kinda nonsense?

deanCommie 7y ago
That's not how...any of that works. 1 - their stories are likely smaller than yours. 2 - you estimate TOGETHER, in a shared common estimation system 3 - what is meant to be tracked is the total collective TEAM velocity, not the velocity of an individual team member
rumanator 7y ago
> Do you think it would bode well for me to create more user stories so that I can mark it as ‘done’ User stories are only a way to gather requirements for a feature and set a definition of done. They have nothing to do with productivity.