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.
In Scrum, Agile Retrospectives performed at the end of each Sprint represent THE key inspect and adapt opportunity for the team. Don’t let it get boring.
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.
Mystery stories? No points, no details, no naming conventions, technical tasks, ad hoc requests… Help! My Sprint Backlog is out of Control!
This time on “More Agile Great Debates”: incomplete backlogs, improvements, “special” Sprints, people swapping, and cross-functionality.
Hear five more agile great debates: time-boxes, Scrum Masters, Managers at Retros, Scrum Teams staying together, and is Scrum for everything?
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.
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.
Not delivering a “done” increment at the end of a Sprint can cause many negative consequences. It’s a bad habit and won’t make anyone happy.
There should be no “special” Sprints in Scrum. The goal of every iteration is to create a working increment that is potentially releasable.