I am now a Certified Scrum Master -
as certified by the Scrum Alliance,
“a not-for-profit professional membership
organization created to share the Scrum
framework and transform the world of work …
Scrum is an agile approach to managing complex projects.”

The Scrum and Agile movements today are moving beyond the software development venue. Those involved, I included, see the need and application in many parts of the company and for any business type that wishes to be creative, innovative or just ensure that true collaboration is occurring.

For me, this has been a circular journey, having operated in a similar manner with my own design business. Much of its success was built on such things as fast track (scrum translation = sprints) and having my designers meet directly with the client (scrum = product owner and team interaction, backstory creation), just to name a few corollaries.

I was introduced to the word Scrum about 4 years ago by a client whose new style of workplace I was creating.  As a VP of Software Development, he wanted rooms for virtual daily scrums. Daily scrums are quick, fifteen minute meetings meant to set up the framework and context for the day’s work. The virtual part was to enable these meetings between team members in California and India.

As the project progressed, I found that this VP and I similar work philosophies. The project was fast, tasks given were completed in a timely manner, input supplied was relevant, prompt and appropriate and key stakeholders participated in the design process and solutions. Though there was heavy pressure from outside, we both worked hard to follow Agile principles and not become a tops-down, hierarchical, isolated process. Ideas abounded and positive creative tension resulted in innovation and a design strategy that supported the work of the business line, not singly the demands of finance or real estate.

I ran across the term Scrum later while attending an Organizational Development conference. Their emerging interest was as a new change management process. Seeing Scrum start to move beyond software development motivated me to dig further, which eventually led to my training and certification.

Upon critical reflection, I have come to realize that the success of that original project resulted from all parties, the business VP (scrum=product owner), me (scrum=master/facilitator) and the team (scrum=broad, cross-represtational, horizontal, non-siloed), being truly invested in:

• the real concept of team and team responsibility, both as a group and as individuals
• invention and out-of-the-box problem solving, even if it has not been done before
• people and the work produced first, process and tools second
• the courage to truthfully define the problem and a willingness to find real, workable solutions

All results supported and facilitated by Agile and Scrum and, as evidenced by the exploding growth of Agile in the  software development industry, hugely successful when allowed to work freely, unencumbered and supported.

I look forward to continuing my facilitation under this framework and to helping people, teams and company’s to capitalize on their internal creativity and innovate to make workplaces work.

I attended the Northern California 2010 Agile Open Conference in San Francisco last month.

For those of you who have not experienced an Open Space gathering, I highly recommend it. I have participated in many, each with a completely different type of group, and found self-organization and participation amongst intelligent people to be highly gratifying. I recently met Harrison Owen who founded the open space concept – a real treat. I’ll save that for another blog.

Basic to an Open Space, self-organizing conference is that the participants develop the agenda. They create and host sessions based on topics they want to discuss or learn about that relate to the general conference topic. I hosted a couple of sessions. Below is one I titled “Why Agile?” I wanted to know, to better understand why people were drawn to this way of working.

 Below are my notes on the discussion and “insights” from the session. Thanks Jim, Mark, Mike, Oluf, et al for your great participation!

 Why Agile?

Agile:

• Has a personality orientation. Parallels actual work of coder
• Is trying to address change, attrition, problem solving; managing business better
• Is expandable and scalable
• Has more communication, especially if you do the daily stand-ups, it can shorten the time blocks
• Has the ability to change more quickly to get excellence, less bugs.
• Employs common ownership that leads to visibility (like Open Source) and potentially better cross-collaboration.
• Ownership issues need to be overcome and can be stumbling blocs.
• Is a socialized form of programming, if all teams buy in.
• Raises the team to a higher level.
• Communication – having to verbalize ideas to others has value and brings the ability to evaluate.
• Egos break down, letting go occurs and supportive roles occur
• Brings more career opportunities vs. trapped, pigeon-holed employees/programmers in one spot or role
• More exposure to experiences and experienced people with other skills and knowledge
• Increases retention vs. risk management
• Goes in waves of creativity/productivity. Only so much people can take of constant group communication. People need down time between sprints/scrums.

Lots of interesting insights into the dynamics, people, pros and cons of working on an Agile team.

Thanks all for sharing!

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?

1.  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!
2. 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.