Those Scrum Teams are Ruining Everything!
Large or small, experienced or new startup, started with Agile and Scrum already or not, the first step everyone takes is setting up Scrum Teams.
Follow the rules and it should just work: deliver software at least 4 times faster and not disturb the rest of the organization. Based on standard Agile and Scrum training materials, a reasonable expectation. But anyone who thinks they can get away with introducing Scrum, getting the benefits, while not disturbing the rest of the organization is in for a big shock.
I will share my experience with an Agile transformation in a 100-person subset of a large software project, in the context of a 27000-person worldwide software development organization going Agile. The good, the bad, and the ugly. What we did about it and what remained to be done.
If you're new at it, so that you won't be shocked. If you're already into it, to understand what that nagging headache is and how to start feeling better.
Outline/Structure of the Experience Report
How I came to Agile
What management at all levels thought when the Agile transformation started
What problems and surprises came up, how they were partially dealt with, costs & benefits
Why Scrum Teams ruin everything, and what to do about it
- Know what you're getting into with a transformation to Agile
- Understand that the Scrum Team does much more than develop software
- Open your eyes to why the organization transforming to Agile has so many "unexpected" problems, and what to do about them
Managers, Executives, Scrum Masters, Product Owners, Product Managers, Project Managers