Scrum leads to change or change incorporates scrum?

While preparing to work with the exec team of a client I had to make a tough decision. While convinced of the idea that Scrum is part of the organizational change process, I could not create a talk that would present that perspective. The client is wrestling with Scrum concepts (good) and expects answers to their problems (also good). I'm fearful that they're missing the bigger picture, the full change process incorporates more then the early wins created by Scrum. John Kotter is my hero here, reading his books "Our Iceberg is Melting" and "Leading Change" brought me passion about change and the role of an exec committee in the change process. Yet how hard can you push a client towards the big picture. I'm going to try, using Kaizen as the entry point to the conversation. Scrum has feedback at it's core - product feedback through the demo and process feedback through the retrospective. If I can expand that concept to the whole process of delivering products to market then I may achieve two goals. I'm lifting the team out of the small and into the larger concept of continuous improvement. And they may see that Scrum is an important step to achieve that nirvana. One step is the start of a journey.




Our Iceberg is Melting (John Kotter, Holger Rathgeber)


A Sense of Urgency (John P. Kotter)


Leading Change (John P. Kotter)


The Heart of Change(John P. Kotter et al)