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.
Part 2 is here! Enjoy 10 more signs and symptoms that your Scrum Team has gone astray and is broken (and a few hints on what to do instead).
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!
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.
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?
Technical Debt is often neglected, but it’s like building a house of cards – eventually, something will give, and it will all collapse.
Ideally, your Scrum Team includes full-time people with the right cross-functional skills; but if you have part-timers, you’ll have problems.
There should be no “special” Sprints in Scrum. The goal of every iteration is to create a working increment that is potentially releasable.
For agile transformations to succeed, they must have top-down support from executives who really understand what it means to be agile.