Transforming Using the Scrum Framework


What about transforming into using the Scrum Framework?  One of the most common questions, we at Collaborative Leadership Team (a Certified Agile Consultancy in Minneapolis, MN receive when coaching or training clients on Scrum is, “We’d like to do Scrum, but avoid doing this or that” In this case, “this” or “that” refers to any of the simple artifacts, ceremonies or roles that make up the Scrum framework.

You can’t transform half-way.

Scrum is fundamentally about changing the way that people work.  In fact, the Vision of the Scrum Alliance, the certifying body for Scrum, is to “Transform the World of Work”.  One interesting aspect of this vision, beyond its scope, is the word “transform”.

“Transform” is defined by Merriam-Webster’s as “to change in composition or structure”.  This word implies that something who has undergone transformation is fundamentally different than it was before the event that transformed it.  While a butterfly is born from a caterpillar following metamorphosis, it bears little resemblance to the furry, little larvae from which it came as it flies away on a summer night.

So too do the organizations that adopt Scrum.  While their value proposition remains unchanged, how they approach delivering on that value proposition is remarkably different with Scrum.  It’s not just the few artifacts, ceremonies or roles, it’s a different set of values that cause how the organization delivers value to the market that changes.  This is the crucial difference that the people asking the question that began this blog entry miss.  Just as a caterpillar can’t become half a butterfly, an organization that seeks to fundamentally change cannot do so half-way.

If you’d like to learn more about Scrum and how you can help change the structure of your work by becoming a Certified ScrumMaster, Click here for our June 13th Certified Scrum Master (CSM) Course