Open Agile Adoption Explained

The following is a brief executive-level summary of the Open Agile Adoption process.

 

Skip to short video interviews from people who have DONE this

 

Open Agile Adoption (OAA) is a repeatable technique for getting a rapid and lasting Agile adoption. It works with what you are currently doing, and can be added at any time. It incorporates the power of invitation, Open Space, passage rites, game mechanics, storytelling and more, so your Agile adoption can take root. A hypothesis of Open Agile Adoption is that increases in engagement drives increases in productivity, after a brief delay. The purpose of Open Agile Adoption is to increase levels of engagement on the part of everyone involved.

 

The core concept of OAA is the rite of passage, or “passage rite”. A passage rite is a cultural event (and a kind of social game) that helps people who have membership make sense of complex social transitions. Agile adoptions are complex social transitions.

 

These are the key events in the passage rite:

 

1/ The Opening: An Open Space meeting

2/ The Middle: With experimentation, play, and storytelling

3/ The Closing: An Open Space meeting

 

OAnA-fig1large

 Figure 1: The Open Agile Adoption Timeline; the Rite of Passage view

 

OAA implements a formal rite of passage of several months duration, which begins and ends with an optionally attended Open Space meeting. In between, in the middle, all work is framed as experimentation. It is framed as playful experimentation that will be inspected by everyone involved, in several months, at the ending Open Space event. In other words, in the middle phase, the teams are encouraged to “play” with specific Agile practices, and to “suspend disbelief”  and “act as if” these Agile practices can actually work.

During this phase they are reminded that another Open Space meeting is planned and that everyone is invited to attend,  and most importantly, to speak their mind.

 

The beginning and ending Open Space events are essential, and form the containing structure. This structure has clear boundaries and helps to reduce the anxiety generated by cultural change.

 

Inside the middle phase of the passage rite between the two Open Spaces, additional components of Open Agile Adoption are used. An Agile coach functions as the master of ceremonies throughout. Executive storytelling is employed frequently, to help define what is happening and to remind everyone about the goal of continuous learning. Game mechanics are used to help convey clear goals, rules, feedback mechanisms, and reiterate that participation in the Agile adoption game is optional.

 

This last point is essential: Open Agile Adoption is a technique based on invitation, not mandates. A hypothesis of Open Agile Adoption is that mandates reduce engagement, and that invitation and opt-in participation increase it. Another hypothesis of Open Agile Adoption is that engagement is essential, and that Open Space helps to increase it.

 

The end of the passage rite is punctuated with an event: the closing Open Space meeting. This closing meeting is the formal end-point in a “chapter of learning” in the life of the organization. It is also the opening of the next chapter.

 

In Open Agile Adoption, the coach assisting you plays an important role by providing guidance and teaching. The closing Open Space meeting is the place where the role of the Agile coach changes. At the closing the role of the coach must change. The coach may exit the organization, or move away from coaching teams and towards coaching executives. A new coach may replace the current coach. In any event, the status and authority of the coach must decrease. This reduction in coach status (and coach authority) is practical and symbolic.

 

In practical terms, the organization is now thinking much more independently, and is much more responsible for it’s  own learning. In symbolic terms, this change in coach status is essential, and emphasized throughout the passage rite process, to underscore the fact that the organization is in fact making progress towards actually weaving (integrating) Agile ideas into the cultural fabric of the organization. This progress is taking place with less and less reliance on the coach, with more and more self-reliance coming from the organization itself.

Cultural Integrations

The last aspect of Open Agile Adoption is the twice-yearly Open Space meeting event. Held in January and July, these events are important and essential. They are anticipated by the organization as a whole, and serve as a place of cultural initiation for new hires.

OAnA-fig2

 Figure 2. The Open Agile Adoption Timeline; Annual View.

 

By instituting these recurring cultural events on the organization’s calendar, the risk of dependency on any one leader is greatly reduced and might even be eliminated. So long as policy authorizes the Open Space events on the January and July calendars, Agile is integrated into the company culture and is not leaving anytime soon.

 

A typical failure pattern in the adoption of Agile occurs when a highly authorized sponsor and progressive leader exits the company. The ‘safe space’ necessary to do Agile well departs with him or her. By instituting these recurring, twice-per-year Open Space events, the process of Agile transformation can and will continue, regardless of who is currently occupying the formally authorized leadership roles.

 

In the final phase, the organization moves to mastery. In this phase the culture is open, and being in the culture feels like being in an Open Space meeting.  In the open culture, the organization values and understands how to sense and respond. When this phase arrives, the Open Space meetings are no longer scheduled on a regular cadence. Instead, Open Space events are arranged as needed.

Only a few enterprises actually reach this phase.

 

Skip to short video interviews from people who have DONE this

 

Related Posts:

On Invitation

On Liminality

On Communitas

On Passage Rites

On the book, “SPIRIT: Development and Transformation in Organizations”

 

 

***

 

 

 

 

 

 

 

On Communitas

Agile adoptions thrive on strong feelings of communitas. Communitas is “the spirit of community”. When the spirit of community is “up”, the space is open, and the feeling of communitas is strong. When the spirit of community is “down”, the space is closed, and the communitas is weak.

And you know exactly what I am talking about. If you love going to work, the spirit is “up”. If you cannot wait till Friday, the spirit is “down”.

With respect to Agile adoptions, communitas is essential. It comes from clearly understood and uniformly applied rules. It comes from a sense that everyone is engaged. It comes from a sense that we are going through this together.

During Agile adoptions, everyone is being triggered. What is my role? What are the rules? When does this end? What does this mean for my status in the group? Executive leaders are triggered. Managers are triggered. Team members are triggered. A new game with new rules is stressful. In a no-mans land of new rules, new roles and unfamiliar ways of working, is it any wonder Agile adoptions routinely fail?

Passage rites can help generate communitas– the very spirit of community. Cultural anthropology says that people going through a passage rite do in fact have the same status during the passage. Participants have widely varied status, going in.

Then the communitas kicks in: all are coming from a known place, and going to an unknown place. All of them make the difficult and even dangerous passage, together. And after it is over, all have changed from what they were, to what they now are. Passage rites can help manage the liminality of transition.

Passage rites are intentionally designed cultural experiences. Repeat: intentionally designed cultural experiences. They are cultural-experience designs. Passage rites are designed to create feelings of community.

Agile adoptions generate a steady stream of stressful liminality, because the learning in Agile is constant. “Continuous improvement” is the goal. That generates a ton of stress on your culture. Learning is change, and change is stressful because it produces liminality. The passage rite is a cultural device for managing liminality.

Passage rites bring communitas, and communitas brings comfort. All the participants going through the passage rite experience a beginning, a middle, and an end. They experience it together. As a community. As a tribe.

This structuring of the unstructured is very comforting, and reduces worries– and stress. Passage rites are extremely useful devices for helping you obtain a rapid and lasting Agile adoption.

Open Agile Adoption is a repeatable technique for getting a rapid and lasting Agile adoption. It works with what you are currently doing, and can be added at any time. It incorporates the power of invitation, Open Space, passage rites, game mechanics, storytelling and more, so your Agile adoption can take root.

Related Links:

Communitas

Liminality

Passage Rites

Open Agile Adoption

Back to Open Agile Adoption home

***

 

 

 

 

 

 

 

 

 

 

 

 

 

What’s Your Open Space Story?

As you may know, I am grateful and honored to be keynoting the Global Scrum Gathering on September 24 in Paris France.

The theme of the conference?!? CULTURE.

It’s sold out! However, you can expect to receive lots of  news after the event. People will be Tweeting there in a big way. You can learn more about the event via this link.

Now: Have you, or has ANYONE you know, used Open Space in some way inside an Agile adoption? ANY Agile adoption, EVER? If so, I am very keen to learn more.

 

What’s Your Story?

If you have a great story, I am here to help you TELL it. If you have a great story, I am eager to tell the world about it, at the Global Scrum Gathering on September 24 in Paris France. The use of Open Space in Agile adoptions is an idea whose time has come.

The Paris Scrum Gathering event is the place where the party gets started!

 

The Facebook Group

Story or no story, if you are a fan of Open Space, you are invited to join the Open Agile Adoption group on Facebook. Here the link:

Explore (and maybe join) the Open Agile Adoption group on Facebook

This group is set up as the place for all of us to post questions, provide answers, post case data and experience reports, tell stories, innovate, and have fun learning with others, in service to rapid and lasting Agile adoptions using Open Space.

 

Tell Me Your Story

Do you have a great story about using Open Space in your Agile adoption? Please consider posting it to the Facebook group, and contacting me if you are interested in having me tell the world about your experience.

Interested? You can find ways to reach me (email, phone, etc)  at: www.DanielMezick.com

 

Related Links:

Description of the Paris Keynote

Open Agile Adoption Facebook Group (anyone can join)

Open Agile Adoption Explained

Back to Open Agile Adoption home

***

 

 

 

 

 

 

 

 

 

People, Then Practices

There is quite a stir these days about enterprise Agile frameworks. There’s a sudden rash of them with various names: Disciplined Agile Delivery, Scaled Agile Framework, and so on.

Any set of practices is fine, including those named above, assuming the people who actually do the work are choosing to use them, and they are not imposed.

So says Martin Fowler, in 2006, in the essay, “Agile Imposition” [2]:

“A team may choose a totally waterfall, un-agile process. In that case, clearly the process is no more agile than apples taste of strawberries. But agile methods aren’t the best for all situations, and personally I’d rather have a team work in a non-agile manner they chose themselves than have my favorite agile practices imposed upon them.” -Martin Fowler, Agile Manifesto signatory. Written 2006, the “Agile Imposition” blog post

Question: Have we asked the folks who do the work what they actually think? No, we have not. Instead, we routinely accept the idea that issuing a mandate can work to motivate highly intelligent, creative, problem-solving knowledge workers.

Has this actually ever worked well?

The poor results of imposing a mandate are predictable. I’ve described this previously in the essay, Mandated Collaboration [1]. That essay is based on thinking that Martin Fowler explained in 2006 in his essay, “Agile Imposition”.

At the time, apparently no one was listening:

“Imposing an agile process from the outside strips the team of the self-determination which is at the heart of agile thinking.” -Martin Fowler, Agile Manifesto signatory. Written 2006, the “Agile Imposition” blog post

 

We Are Done With Mandates

The era of mandating specific Agile practices is probably over.

The new wave is probably based on sociology and invitation, rather than methodologies and mandates.

SAFe, DaD, MOM, YourFramework, Scrum, FrameworkDuJour and Kanban (et al) are all perfectly OK, provided the people who do the work get a legitimate INVITATION to discuss with everyone else….

a) …what the business problems to solve actually are, and
b) …what Agile techniques and tools might actually help, and
c) …what experiments are next, to see what can actually work.

If the folks are invited into that wider conversation, and invited to help write the story about solutions, and invited to experiment, great. Otherwise, WE ARE ISSUING AN AUTHORITATIVE MANDATE which we know does not even remotely associate with anything good, or with anything even remotely Agile.

“… imposing agile methods introduces a conflict with the values and principles that underlie agile methods.” -Martin Fowler, Agile Manifesto signatory. Written 2006, the “Agile Imposition” blog post

 

We need to be done with mandates. Can we stop right now, please?

Mandate-of-practices is the culprit here– not any one framework. Mandates reduce happiness by eliminating the freedom to choose. No one wants to play the “mandate-game”, precisely because it is not fun [4].

The mandate-of-Agile-practices wave, now over 10 years old, is probably peaking right now. This cresting of the wave may hard to see right now. That said, it is probably quite over. The results are in and they are not great.

 

The Next Big Wave

The next big wave is based in the sociology of INVITATION. The next wave puts people first, rather than practices.

“You know as well as I do that if the team really doesn’t want to use a methodology, IT WON’T WORK. (emphasis added.) Let them make their own assessment.” -POWER OF SCRUM book, page 31 (page 37 in earlier versions)

 

OpenSpace Agility

OpenSpace Agility [3] is a sociological technique that uses invitation instead of mandates to get a good and lasting Agile adoption. It focuses on people, THEN practices. It incorporates invitation, Open Space, game mechanics, storytelling and most importantly, a “rite of passage” structure to help actively manage the substantial fear and anxiety that comes with new ways of doing and being.

Any technique you want to use is OK, provided you show respect for the people who do the work. That usually starts with an invitation. If you issue mandates, you are asking for trouble.

If we mandate SAFe, you are asking for trouble.

If we mandate Kanban, you are asking for trouble.

If we mandate Scrum, you are asking for trouble.

“[A leader’s] responsibility is to make clear to the team that THEY should be in control of there own work processes, and show them how to do that.” -POWER OF SCRUM book, page 31 (page 37 in earlier versions)

You might be thinking I am off by a mile. If so, realize that these quotes are coming from Agile Manifesto signatories. Just saying !

The OpenSpace Agility technique [3] can be used at any time to improve your Agile adoption results. It can be used with any and all practices and practices frameworks. It’s based on the hypothesis that engagement & good results are correlated, and that ENGAGEMENT is the name of the name.

We can use it for free, get good results now, improve it, and make it better.

We can choose to avoid mandates, because they are in conflict with genuine Agile thinking.

“So I hope I’ve made clear that imposing agile methods is a very red flag. ”-Martin Fowler, Agile Manifesto signatory. Written 2006, the “Agile Imposition” blog post

Mandates

Let’s focus on people, and then practices. Any set of practices are OK to try… unless we are mandating them.

Related Links:
[1] Mandated Collaboration http://newtechusa.net/agile/the-recipe-for-botched-agile-adoptions/

[2] Agile Imposition (Martin Fowler) http://martinfowler.com/bliki/AgileImposition.html

[3] OpenSpace Agility http://www.OpenAgileAdoption.com

[4] Gaming Happiness http://www.GamingHappiness.com

Back to OpenSpace Agility home

***

 

 

 

 

 

 

 

 

 

 

 

 

 

On Passage Rites

Transitions are tough, and serve as a kind of bridge from here to there. Adopting Agile is a big transition that always means lots and lots of new learning. And learning is stressful, because it generates liminality.

(NOTE: If you are new to liminality, please examine this link first.)

All genuine learning in adults creates instability- liminality- until that learning is integrated. The primary way to manage liminality in a social system is to institute a passage rite.

A rite of passage provides a structure. This ritual has a structure that provides a beginning, a middle and an end to a transitional experience. Designing a passage rite is an exercise in experience design.[3] Passage rites contain and thereby reduce the highly destabilizing feelings of liminality. This is important, because liminality causes stress that can lead to all sorts of problems, including deep anxiety, fear, panic, depression and even various forms of neuroses.

When you study passage rites, you learn that they usually include at least one very scary experience. For example: a member of a tribe in Africa going through a passage rite from boyhood to manhood might have to kill a dangerous animal, like a lion or a hyena. You might be wondering if this passage-rite notion is a such a good idea. Do we really want to put people though super-scary experiences?

Here is something to think about: culturally speaking, what comes first: the highly stressful transition, or the passage rite?

Passage Rites for Handling the Liminal State of Being

The highly stressful transition comes first. Passage rites are a cultural response. Passage rites serve to contain the scary experience of transition. They are established by a culture in response to the need for the handling of the highly stressful liminality. The transition comes first; the creation of a passage rite comes later, as a cultural mechanism for defining and smoothing the transition from here to there.

In other words, a passage rite does not produce liminality. Instead a passage rite handles the liminality that shows up during key transitions in the life of the group…and its members.

The stressful and necessary transition- for example, the transition from childhood to adulthood- is present BEFORE a passage rite was instituted.

The primary task of of a passage rite is to help smooth out the stressful liminality created by a transition.

The primary task of an Agile adoption is to produce a cultural transformation. This is a huge transition that in theory never ever ends, because it is focused on continuous learning and improvement.

We currently do not manage this very HUGE transition as well as we might. Passage rites can help.

And that is what Open Agile Adoption is all about.

Key Points:

  • Big transitions in the life of a group produce liminality;
  • Liminality is stressful. It can make you anxious and fearful;
  • Passage rites do not produce liminality, instead passage rites are cultural devices that handle the liminal state of being, so the participants can get through… and go where they need to go.
  • Agile adoptions are transitions and produce considerable anxiety, worry and the liminal state;
  • A formal passage rite– a certain kind of cultural ritual– can help;
  • Open Agile Adoption works because it acknowledges these dynamics, and institutes a rite of passage that helps all the participants in an Agile adoption get from where they are… to where they need to go.

Related Links:

[1] Blog Post: Liminality 

[2] Wikipedia: Passage Rites

[3] Wikipedia: Experience Design

Back to Open Agile Adoption home

***

 

 

 

 

 

 

 

 

 

On Liminality

The liminal state is a transitional state of being. The root Latin word- limens– means “threshold”. The liminal state is a no-mans land of transition, confusion, stress and vagueness. It is lacking in definition. No longer where you were, and not yet where you are presumably going, liminality has the potential to drive you and your organization crazy.

 

Learning and Liminality

Adopting Agile always means lots and lots of new learning. Learning is stressful, because it generates liminality. All genuine learning in adults creates instability- liminality- until that learning is integrated.

We know the world through our models. Mature adults hold a model of reality. Genuine new learning challenges the validity of that model. This invalidation of your previous assumptions produces the very unstable,  liminal state, until you integrate that new learning.

The introduction of Agile into an organization definitely creates liminality. In my coaching, I notice that the introduction of Agile is usually quite triggering for most participants. This “triggered” behavior is based on fear, and is a natural reaction to entering the unstable state of liminality.

Before Agile, everything was well understood. Then: …new roles, new ways of interacting, and a new mindset are all required of you. The learning is constant, and stressful. Agile can be very triggering.

Uncomfortable in the transition, the natural and safe thing to do is turn around and go back to where you came from. And people in organizations routinely do exactly this. We backslide on Agile and return to where we came from. This “going back” reduces the worry, the fear and the anxiety, the core emotions evoked by the liminal state of being.

 

Rites of Passage

Various tribal societies, throughout the world, across different periods of time, and coming from different places, have all come to the exact same conclusion: liminality must be carefully managed, and the best way to manage it is to institute a passage rite.

The purpose of a passage rite is to manage the transition from one state of being… to another.  Tribal societies have been doing this routinely, for thousands of years.

In the modern day, we routinely introduce Agile into organizations, while blissfully ignoring the essential human dynamics of liminality.

This is probably a very serious error.

 

Stability in the Liminal State

The hypothesis of Open Agile Adoption is that introducing Agile into typical organizations creates liminality at the group level. If this liminality is managed with a passage rite, there is potential for a rapid and lasting Agile adoption.

The core idea behind Open Agile Adoption is that the active management of liminality reduces worry, anxiety and fear, creating at least the potential for a rapid and lasting Agile adoption. The primary way this is accomplished is by leveraging the ancient practice of the passage rite. A passage rite creates a structured experience for participants….with a beginning, a middle and an end.

Open Agile Adoption is a repeatable technique for getting a rapid and lasting Agile adoption. It works with what you are currently doing, and can be added at any time. It incorporates passage rites, game mechanics, Open Space, storytelling and more, so your Agile adoption can take root.

 

Related Links:

Quick Overview: Liminality explained

Detailed Essay: Navigating the liminal state

More Information on: Open Agile Adoption

Back to Open Agile Adoption home

***

 

 

 

 

 

 

 

 

 

 

Why Good Agile Adoptions Go Bad

Why do good Agile adoptions go bad? The reason is very simple.

Someone or a group of people with enough authorization decide to create a genuine Agile adoption. And they do.

They create a “space” where it is safe to tell the truth, to say what you feel & think. Safe space.

The result is absolutely awesome Agile. Big “A” Agile. Loads of group learning is the result.

Shortly after that, great business results ensue.

This goes on for awhile.

Then, most of the people who created it, the highly authorized “champions”… the people with enough authorization to create this “space” and keep it “open” and “safe” ….they leave the company.

For any one of several reasons.

Then everything unravels.

What is the solution?

This is a riddle.

The answer to the riddle is found inside the book SPIRIT: Development and Transformation in Organizations. An amazing book. From an amazing author, Harrison Owen.

The book is a free gift; you can download it for FREE. Right now.

If you examine this book carefully, you can solve this Agile riddle…and many more.

Back to Open Agile Adoption home

***

 

 

 

 

 

 

 

 

 

Aug 29 DOWNTOWN Meeting: Jean Tabaka on DESIGNING EMPATHY IN

About the Speaker:

JEAN TABAKA

I’m an Agile Fellow with Rally Software in Boulder, CO. I love coaching others about Agile software development. My passion in this realm has led me to concentrate on practices in collaboration and leadership. I’m also now reaching into systems thinking, Lean, and Kanban (you can read blog posts I’ve written about these topics). I see a strong interdependency among these various processes and practices. This has led me to also look outside of software and IT to our larger community about sustainable and restorative practices within our physical world. I graduated Magna Cum Laude and as a University Scholar from the University of Missouri. I hold a Masters in French Literature from Michigan State University and a Masters in Computer Science from Johns Hopkins University.  I’m a a Certified ScrumMaster and Practitioner, a Certified Scrum Trainer, and a Certified Professional Facilitator.

Session Description:

DESIGNING EMPATHY: A DISCIPLINE FOR GREAT BUSINESSES

You are a Product Owner working hard to maintain a value-driven product backlog. That means you continually check in with what you mean by value. For me, that means checking with what your customers in new heartfelt ways. What adds value to them? What provides them function, commodity and delight? How can you act in love and service to them? Designing empathy into your product feature sets brings you into a deep relationship with your customers. Design from your head and heart to your customers’ head and heart. Fortunately for all of us as product owners, George Kembel and his team at the d.School at Stanford University have been working for a number of years on approaches to help us develop customer empathy and to act on it. Having had the good fortune of working with George and his brother John, I have worked with my colleagues at Rally Software to create a design empathy approach that draws from the d.School work while adding in some of our own brainstorming divergence and convergence approaches for data collection and knowledge massaging. This session affords you the opportunity to learn the full spectrum of empathy activities: from empathy interviews all the way through to possible points of view for designing subsequent experiments. Interactively in a workshop setting, we’ll first complete an overview of the overall design thinking approach within which empathy practices fit. We then move to interactive work in small teams. Each team will create one component of the set of items that design the full empathy experience.

REGISTER:

http://www.brownpapertickets.com/event/445699

Meeting Agenda:

6:00 pm Introduction

6:30 pm Food, beverages, and socializing

6:50 pm Main event

7:50 pm Done

8:00 pm Done Done

 

Meeting Location:

PAYPAL
1 International Place (6th floor)
Boston, MA 02110

 

REGISTER:

http://www.brownpapertickets.com/event/445699

Aug 28 WALTHAM Meeting: Jean Tabaka on THE AGILE ART GALLERY

About the Speaker:

I’m an Agile Fellow with Rally Software in Boulder, CO. I love coaching others about Agile software development. My passion in this realm has led me to concentrate on practices in collaboration and leadership. I’m also now reaching into systems thinking, Lean, and Kanban (you can read blog posts I’ve written about these topics). I see a strong interdependency among these various processes and practices. This has led me to also look outside of software and IT to our larger community about sustainable and restorative practices within our physical world. I graduated Magna Cum Laude and as a University Scholar from the University of Missouri. I hold a Masters in French Literature from Michigan State University and a Masters in Computer Science from Johns Hopkins University.  I’m a a Certified ScrumMaster and Practitioner, a Certified Scrum Trainer, and a Certified Professional Facilitator.

 

Session Description: THE AGILE ART GALLERY
Very often, when we try to describe Agile to people, we tend to use words, technical words. Or we may add in a sketch of a Scrum process or how releases fit with programs and teams and cadences. But I think Agile is more than this. And I think that there is a part of our brain that is being under utilized as we describe Agile to others. In fact, perhaps we ourselves are not fully embracing Agile if we don’t move beyond these technical words. In this session, we explore Agile through a new lens. We apply are artistic sense of what Agile means by reaching into terms that we might not readily associate with Agile. In the end, we will share our interpretations and debrief about what this means to our views on Agile. Agile is truly expansive. And it is continuing to be so. My hope is that through this very interactive session and through fun, participants will be willing to delve into some of the Agile depth.

 

Register:

http://www.brownpapertickets.com/event/445686

 

Meeting Agenda:

6:30 pm Introduction

7:00 pm Food, beverages, and socializing

7:20 pm Main event

8:20 pm Done

8:30 pm Done Done

 

Meeting Location:

WALTHAM PUBLIC LIBRARY

Phone: 781 314 3425
735 Main St  Waltham, MA 02451

Directions:  http://waltham.lib.ma.us/hours_directions.php

 

Register:

http://www.brownpapertickets.com/event/445686