User Stories: Ready, Set, Go! part-2

No Comments |

We left the last post sharing some of Roman Pichler’s thoughts around readiness. Let’s continue… Another way of Describing Ready I personally like a checklist approach for describing teams’ readiness criteria for work.  Here’s an example of the sorts of checks that I’ve seen prove valuable for teams to leverage when maturing their stories: The […]

No Comments |

User Stories: Ready, Set, Go! part-1

No Comments |

Have you ever entered a Sprint taking on a User Story that you later regretted? For example:

- One that you should have broken down a wee bit more?
- Or one where the team had not a “snowball’s clue” how to technically implement?
- Or one where the value wasn’t clear from a business perspective?
- Or one where the estimate and the reality were not equal?
- Or one that, when you got it “Done”, you weren’t quite sure how to determine that it was done?

I’m guessing, of course you have. I encounter these scenes in teams I’m coaching all the time. And truth be told, it’s not a terrible event. Teams make mistakes…all the time. And they usually learn from them.

No Comments |

  • Recent Comments

    • Andrés Calviño: I guess David Hussman’s videos were moved here: http://devjam.com/coaching/...
    • Felipe Cardona: It’s a very interesting and coherent approach. I’ve seen a lot of companies excited with...
    • Israel: The presentation is very interesting. As a member of a distributed team I am sure that distributed agile work...
    • Adrian Moya: Great post Bob! I’ve seen a couple of these anti-patterns in real life. I really laughed at the...
    • Charlie: I can concur that attrition with Velocity teams is lower than one other South America-sourced partner....