My Scrum Team Doesn’t Want to do some Events
Each event of Scrum has a specific audience and purpose. While skipping some might be tempting, you might want to read this before doing so.
Each event of Scrum has a specific audience and purpose. While skipping some might be tempting, you might want to read this before doing so.
In the second part of my blog series on “Agile’s Great Debates,” learn about five more agile topics that people argue about and disagree on.
My previous “Great Agile Debates” have proven extremely popular, so I thought I would add to this body of knowledge with a new blog series.
Nothing in The Scrum Guide says you can’t pick a specific purpose for a Sprint, but is it a good practice? Are there special types of Sprints?
Scrum Teams without formal training are apt to make tons of mistakes because they don’t have experience or guidance. Here’s what can happen.
One critical decision when starting a new Scrum Team is the length of the Sprints. The Scrum Guide says “one month or less.” So, what’s ideal?
The right way to write User Stories is from a user’s perspective, taking a thin vertical slice through all the horizontal system layers.
While Scrum is a flexible framework, it isn’t Scrum unless you have all the components, so NO, it’s not okay to skip some Scrum events!
I can’t tell you how many organizations I have worked with that had employees who confused the Sprint Review with the Sprint Retrospective.
What’s the purpose of a Sprint Review? I’ve seen tons of confusion about the reason for this critical agile event. Let me help clear this up.