How big is your Story Point? No, I don’t mean in hours, we all know that a Story Point to Hours comparison is impossible. I mean, when you estimate how long a User Story might take, how do you decide on the number of Story Points? What’s your yardstick?
You get to the end of a sprint and find that you still have user stories that were not completed. Why does this happen? How should you deal with it? And how do you prevent it from happening again? This article addresses all of these questions.
In my daily work as a consultant Agile Coach / Scrum Master and also a Scrum Trainer, I regularly get asked this one question: Can Distributed Scrum really work? Recently, I had the great pleasure to discuss this same topic with a group of highly respected Agile Coaches and Scrum Masters and the outcome of that discussion might just surprise you!
I love a good analogy and on the way to work today I was struck by the similarities between my journey and the route to a successful Scrum implementation. As I thought more, I realized that there’s one skill you need more than any other to implement Scrum. Not only that, it’s a skill listed as one of the Five Principles of Scrum. Can you guess what it is yet?
Scrum is brilliant in theory but in everyday use, niggling little problems keep popping up. How do you deal with them? Welcome to the first in a series of articles discussing Scrum Implementation Issues. Today, we’re discussing the Daily Scrum time box.