Project Management

Scaling Scrum

Craig Larman and Bas Vodde
linkedin twitter facebook print Request to reuse this   Agile   Scrum   ProjectsAtWork  

Too many organizations confuse doing agile with being agile. They force adoption through command-and-control thinking combined with predictive planning. That won’t work. In this series of excerpts from their new book, Craig Larman and Bas Vodde share best practices for adopting and scaling lean and agile development.

 
We have worked closely in a few enterprise-wide lean or agile adoptions over the years, and have collected experiments. Some focus on scaling and multiteam coordination (such as a Joint Retrospective); many others focus on organizational design and culture. First, a story...
 
We were coaching in Europe and met with a manager who had been assigned the agile transformation responsibility; he wanted to show us his plan and ask for feedback. He presented a Gantt chart of his planned transformation: many stages of precise duration all in sequence, milestones, specific managers assigned to tasks along the way, cost estimates, and more. According to the plan, in twenty-seven months the group would have transformed to 'agile.' The detail was impressive — it was also the wrong approach.
 
Our colleague had confused doing agile and being agile. And he was applying command-and-control management thinking combined with predictive planning — in essence, traditional management 'agile' adoption. …

Please log in or sign up below to read the rest of the article.

ADVERTISEMENT

Continue reading...

Log In
OR
Sign Up
ADVERTISEMENTS

"Nobody can make you feel inferior without your consent."

- Eleanor Roosevelt

ADVERTISEMENT

Sponsors