Agile, Scrum and Me
Wednesday, 3. November 2010 17:08
I have recently undertaken Scrum Master training in southern California.
“Scrum”, as per the Scrum Alliance, “is an Agile framework for completing complex problems … an innovative approach to getting work done.” Most often Scrum is applied, and has evolved from, the software development community. Its practices of fast iteration, sprints, daily communication (Scrum standups), transparency and team work are some of the parts leading to its blossoming success.
Why Scrum for me?
- I was first introduced to Scrum about three years ago. The framework I experienced in support of the creative process was so similar to what I had experienced in my own company and its creative processes years ago that I was overcome with wafts of déjà vu. Scrum mirrors in many ways the original collegial gatherings of old design and architecture charrettes, which most A&D firms have lost or abandoned over the years. The camaraderie, appreciative critique and inquiry and team participative creativity of those days I find can be present and emergent in the current practice of agile. Finally a vehicle for creativity in the corporate world!
- Having spent years creating workplaces for software and hardware engineers I have come to the conclusion that there is a huge mismatch, a chasm of incongruence, between the workplace delivered and the real workplace needed by the knowledge workers within them. Watching the systemic business process changes emerging from Scrum further cements my belief in its application and success. However, Scrum’s success is only as possible as it is fed, supported and under the umbrella of the larger concepts of Agile.
Agile has four overarching principles, paraphrased from the Agile Manifesto:
- Individuals and interactions over processes and tools
- Completed functionality over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a planThat is, while there is value in the items on the right, the items on the left matter more.
It is clear that without these principles Scrum would fail and that, conversely, the very adherence to the framework of Scrum is inherently enacts the principles. They are symbiotic concepts, one dependent on the other for success.
3.
I have come across emerging interest in Agile and Scrum in both of the traditional worlds of Organizational Development (OD) and Project Management (PM). OD comes at it from interest in the new organizational behaviors they represent that are seemingly compatible with trending in change and change management. PM’s interest is from the new project process perspective. Unfortunately I see each interest looking at it mostly within their current siloed points of view. Scrum is not interested in change per se and adamantly eschews the labels of process and methodology, favoring the term “framework” instead.
But Scrum is not perfect. My research and discussions inform my current thinking. Scrum and Agile are only successful when there is a marriage of:
- A change to partnering and collaborative behavioral skills
- Adherence to the Scrum structural framework, including having the roles Scrum Master – team facilitator and Product Owner/Manager embodied in two people, not in the same person.
- Respect and utilization of the Agile principles
There is a movement afoot within the agile community to take Scrum and Agile outside software development and into other parts and types of organizations, including non-profits. Stay tuned for my journey there.
Category:Business Process, Creativity, newworkplaces, Productivity, Trending | Comment (0) | Author: Catherine Adams Lee






