Scrum’s use in spreading in product companies and engineering
organizations. These organizations hope that Scrum will :
them more productive
risk management capabilities
the value of products in the marketplace and systems in the organization
the morale and pleasure of the developers, product managers, customers and
However, when they use Scrum, they run into ScrumBut’s.
ScrumButs are reasons why they can’t take full advantage of Scrum to solve the
problems and realize the benefits.
A ScrumBut has a particular syntax:
An example ScrumBut is (The Daily Scrum meetings are too much
overhead) (because the team members don’t need to meet so often) (so we only
have them once a week, unless we need them more often).
In this workshop, people who
are accumulating ScrumButs will work with Ken Schwaber and other selected Scrum
guru’s. They will identify their highest priority ScrumButs and learn how to
systematically address and resolve them.
While doing so, the attendees will learn how to assess the impact of a
ScrumBut on the organization and quantify its damage. Attendees will also learn
how to turn ScrumButs into actionable user stories that can be resolved using
Attendees are expected to bring some of their highest impact
ScrumButs to the workshop. Several will be worked on, including identifying how
they were identified by Scrum, measuring their impact, and creating plans and
techniques for resolving them. War stories of what these ScrumButs have done to
other organizations will be shared.
At the conclusion of the workshop, attendees will know how to
identify, write-up, and resolve ScrumButs.