How to Scrum without a Scrum Master
Can Scrum Teams exist and operate at their best sans a Scrum Master? Maybe. Here are a few experiments you can try to get by without one.
Can Scrum Teams exist and operate at their best sans a Scrum Master? Maybe. Here are a few experiments you can try to get by without one.
How do you tell if your Scrum Team is broken? Here are 10 symptoms there might be something wrong…
This time on “More Agile Great Debates”: incomplete backlogs, improvements, “special” Sprints, people swapping, and cross-functionality.
Here are my latest five great agile debates: Story Points, Job Titles, Velocity, Project Managers, and Business Analysis. Join the argument!
In the fourth installment of my blog series on “More Agile Great Debates,” I dive into another five topics that people like to argue about.
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.
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?
There should be no “special” Sprints in Scrum. The goal of every iteration is to create a working increment that is potentially releasable.
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!