The Agile Tipping Point
The Agile Tipping Point
Agile consultants often take on the responsibility of helping an organization adopt Agile Methodologies. This is a challenging task to say the least. Introducing new ideas into an organization requires social intelligence, advanced communication skills, and persuasiveness, not to mention a sound grasp on Agile principles and practices. In many large organizations, the Agile consultant must also contest the deeply embedded mentality of traditional waterfall. The software industry changes constantly, but people's habits and minds aren't always amenable to change.
Influencing in an organization is certainly not easy. But is being knowledgeable about Agile, having lots of experience, and being persuasive the keys to success? Are there other more effective ways to make an idea spread?
Malcolm Gladwell's The Tipping Point
Malcolm Gladwell's book, "The Tipping Point: How Little Things Can Make a Big Difference," examines the issue of how ideas spread quickly and become a social phenomenon. Gladwell analyzes interesting issues, and his writings are based on documented research and science. While his conclusions are often surprising, they are based on sound reasoning. His books are simply fascinating. The Tipping Point focuses on the notion that "ideas and products and messages and behaviors spread like viruses do." The concepts in his book can be readily applied to implementing Agile ideas within organizations. The principles illustrated in the book can help the Agile consultant effectively spread his message.
The Tipping Point describes three "agents of change":
- The Law of the Few
- The Stickiness Factor
- The Power of Context
This article will apply these agents to the software environment with the aim of making Agile a successful methodology in organizations.
Law of the Few
The Law of the Few is the rule that large differences are made by only a few select people. Any type of social change or epidemic is dependent upon the involvement of a few extraordinary individuals that have the gifts of coercion, influence, knowledge and connectedness. Gladwell's theory is a derivative of the Pareto principle which states for many events, roughly 80% of the effects come from 20% of the causes. The Law of the Few enumerates three different types of individuals: Connectors, Mavens and Salesman. How does this apply to Agile? In order to make the ideas of Agile effective in an organization, we have to enlist the help of these three types of individuals.
Connectors are people who connect us with the world around us. They have "an extraordinary knack for making friends and acquaintances," while staying connected with these people. In a software group, the Agile consultant must find the Connector and get that person on board. This individual could be one of several different positions in an organization. Initially, you may think it’s the Director of IT, because after all he is in charge and makes all the decisions. Or you may think it's the IT manager because she is involved in day to day decisions.
While these individuals have authority, it's not the position that counts the most for a Connector. It's the social traits. The connector is the individual who is friends with various members of the team and interacts with them in the workplace and in social settings. The connector is the person who has true respect and rapport with team members, the business, management, and the testers.
The Connector will disseminate the Agile message on your behalf and the message will catch fire. It will become part of the everyday lingo. Find the Connector and the Agile mindset will seep into the organization.
Mavens are information specialists. They have deep knowledge of specialized topics and are willing to share that information with others. They are the people we rely on to keep us informed and connected with the world around us.
In his book, Gladwell references Mark Alpert, a professor at the University of Texas, McCombs School of Business. Alpert is a market Maven, perpetually tracking the prices of products, analyzing the best deals for houses, cars, or household items. In addition, he has a remarkable and compulsive urge to help other with this knowledge. He is a Maven and Mavens want to educate, not to sell.
In a software group, you must identify and enlighten the Maven in order to spread the word of Agile. Agile concepts will excite the Maven who will relentlessly learn about the topic. At the same time the Maven will be motivated to pass that knowledge onto other team members. They are the first ones to investigate the newly introduced Agile trends and report their findings to teammates. The maven could be a manager, a senior developer, or a business analyst. Get the Maven on your team on board and success will be more likely.
The Salesman is an individual who builds and instant connection with people. Their mannerisms, personality, and presence are socially contagious. Unlike, the Connector, they need not be well connected with everyone in the organization. Due to their social persuasion, Salesmen have extremely effective negotiating skills. Their positive non-verbal cues entice others to follow their lead. They are just plain likable.
For an idea to spread on a software team, enlist the Salesman to help you out. This person doesn't have to be an expert at Agile. They just have to be excited about it. Their personality and positivity for the idea will be caught be others. In fact, you may have to play the role of Salesman!
The Stickiness Factor
The second agent of change identified by Gladwell is the Stickiness Factor. We all believe that the inherent quality of the ideas we present is the key factor in determining adoption. Often this is not the case. There are many documented instances where Agile has failed, and we all stand to believe that the main concepts of Agile are not the problem.
The Stickiness Factor is not the content of the message, rather a "subtle but significant change in presentation that makes the content memorable." The essence of the Stickiness Factor is best illustrated by Gladwell's example of the children's show Blue’s Clues, which for a short period of time, was wildly more successful than Sesame Street. Blue's Clues cut out all the contemporary references and sophisticated jokes that Sesame Street often delivered. Thus kids' attention for the show did not wane due to comments that were over their head. Kids paid closer attention to Blue's Clues for the duration of the show, and thus the show received better ratings than Sesame Street. This was the Stickiness Factor for Blue’s Clues.
So what is the Stickiness Factor for implementing Agile practices? There are probably many, but here are a few ideas. Deliver the concepts of Agile in story form. Stories are a powerful mechanism to organize and deliver information in such way where others can identify with your perspective. Give an example of how an Agile practice brought success in a past project. Illustrate how the practice of continuous integration helped keep the code base clean for an entire month straight and eliminated petty defects arising just before a release. Offer a storied scenario of how Test Driven Development (TDD) helped drive the design of a component, while providing a set of regression tests to conserve the quality of the code. The story format can be more effectively absorbed by the minds of team members than just an abstract academic lecture describing the concepts of Agile.
Another idea for getting hold of the stickiness factor is to introduce Agile practices incrementally. Start small and try to gain traction as you make progress. For example, introduce a daily standup and allow it to be successful for a few weeks. Then introduce iterations and iteration planning, followed by TDD. Entice the business with regular releases to a test environment to increase their involvement. An incremental approach can ease the transition to Agile for a development team and each small success can build on the Stickiness Factor for Agile.
The Power of Context
The final agent of change described by The Tipping Point is The Power of Context. Human behavior is sensitive to and strongly influenced by its environment. Gladwell says, "Epidemics are sensitive to the conditions and circumstances of the times and places in which they occur."
A transition to Agile has to be supported by the right environment. If you want to introduce Agile practices and methodology, there must be evidence that the organization is ready for change. You can’t force ideas on those unwilling to listen. In my experience, there are three key elements that determine the potential success of an Agile conversion :
- Senior management must embrace Agile and sufficiently understand its principles.
- There must be a business need to make a process change in the organization. Continuing the same route must cost more than making some kind of change.
- The team must have a majority of members open to learning new ideas and willing to change. They must also have an inner drive to be successful.
These three points serve as the context for Agile change. Of course, if a resounding "No!" is the answer to these three questions, then you are flowing against the current and your efforts may turn fruitless as an Agile consultant.
The Tipping Point is an analysis about how ideas catch fire and spread through society. We can apply these concepts to our own field. Individuals can make a difference in an organization. By applying Tipping Point principles, you can ignite a grass roots movement toward from within. All that is required is a little determination, heart, and knowledge of the social interactions at play between people. Change can happen and hopefully you can find the right Agile Tipping Point.
* Thanks to Jacob Orshalick, partner at Solutionsit, for his review of this article