The Theory of Change & Why I Get In Trouble

organizational antibodies, agile, stock photo

organizational antibodies, agile, stock photo

As an agile coach that has been fortunate to work at a good number of clients over the years, you get an opportunity to experience some interesting similarities among clients. Some are tragic, some are funny and some are just downright intriguing. I recently spoke with another agile coach and I discovered one particular pattern that I have decided to refer to as organizational antibodies.

The talk in question was about the on boarding of coaches and things a coach tends to experience in the first few days on the ion. As we talked together and related our war stories I noticed that both of us had a something happen to both of us early in our engagements with companies. That common denominator was that both of us found ourselves in trouble with management in the new company within the first week or two of our gigs with our coaching ability or competence questioned or tested.

To hear that others shared my knack for getting into hot water early on was a relief to me. Of course, all of these early issues were resolved in short order, but it brought up a very interesting question of why this happened so frequently. As I look back on my personal experiences and after hearing the same from my colleague, a theory began to form in my mind. The end result is my Organizational Antibody Theory of Change.

The theory is this – there are many in any company who benefit from the status quo. Agile is about organizational change and those who prefer the status quo will find the agent of change as a threat to the corpus organizationus and will do their best to protect their system by attacking the agent of change. In other words, there are people in your company that perform the same role that antibodies provide in the human body.

At this point in my career I fully expect to have at least one of these reactions in every gig I start within the first couple of weeks. In the past it was quite disconcerting for me but now that I have experienced it and expect it, I worry less. The problem is always a tempest in a teapot, a minor annoyance that will fade away as my role is better understood and people realize that I am not a threat. Have you ever experienced organizational antibodies before?

The Difference Between True Rockstars & Pretenders

rockstar, guitar, rockstar team, agile team, larry apke agile

rockstar, guitar, rockstar team, agile team, larry apke agile

I’ve had the pleasure of working with hundreds of teams during my time as an Agile coach. I have loved and enjoyed working with each and every one of them. There are some though that are more memorable than others.

Frequently it is those teams that I coach first in any organization – in psychology this would be referred to as the primacy effect. Sometimes it is because of the nature of the team. Recently I found myself waxing nostalgic for one very particular team that was my first team and also memorable because they were “rockstars”.

Let me make it clear that the team name was not “rockstars”. I have had many teams in my time self-identify their team with the name “rockstars”, but, somewhat predictably, these self-proclaimed “rockstars” rarely lived up to their own press. The team I am thinking of was one that was hand-picked and put together because they were true high-performers within the organization. They were the best programmers, QA and management.

While the generally accepted belief is that creating a functioning team of rockstars is fraught with difficulties because many have over-sized egos, I did not find that to be the case with a true “rockstar” team. It was the pretenders to rock stardom who had egos and were difficult to manage. It did not take long to figure out the difference between true rockstars and pretenders. It all boiled down to one thing:

True rockstars listen.

(And, of course, they do not refer to themselves as rockstars).

As a coach, a big part of my job is getting people to change their behavior. The true rockstars became the way they are because they have listened, because it is more important to them to be the best then to appear to be the best. The true rockstars know that they will make mistakes from time to time but in order to be the best, they must try new things from time to time, to stumble and fall sometimes. Of course, the true rockstars always get back up, dust themselves off and work until they succeed.

That is not to say that true rockstars will not challenge a coach and take everything that is said without question. They are the best because they question everything, but they also accept that learning can happen anywhere at anytime and can come from any source, even from a coach whose programming chops would never measure up. Once they are convinced that you are not wasting their time, they will not only listen but they will readily adopt ways of implementing new ideas. My own group of “rockstars” were tasked with taking cutting-edge technology and delivering it to customers many times faster than ever before in their organization and they did, not just once, but on multiple occasions. I believe that their success hinged primarily on the fact that they were smart enough to listen, not only to me, but to any and all who might have something, no matter how small, to help them become better.

The pretenders are different. They are closed to new ideas because they have all the answers. They use their experience as a reason not to listen to others. Their ego is so tied with their “rockstar” status that change is a threat. To change would be to admit that they were not the experts, that they do not know everything.

Beware the pretenders.

Larry Apke

Deming, Agile and SAFe

W._Edwards_Deming
W Edwards Deming

This week was a big week in my quest for lifelong learning – one in which the learning should prove beneficial to my furtherance of agile values and principles; a week that I think I will think of a the week of Deming since I completed my reading of two of Deming’s books – Out of the Crisis and The Essential Deming – and I also completed my Scaling Agile Framework (SAFe) training in which I saw Deming’s face and quotes about a half a dozen times. SAFe itself can be thought of more of a homage to Deming’s work with systems than a software development framework or, perhaps more accurately, Deming’s systems thinking as it applies to software development.

While I will shortly take the SAFe examination test, I am certain that my recent completion of two of Deming’s books will serve me well when I take the exam. In fact, I am inclined to wonder if a healthy knowledge of Deming and deep knowledge of Agile and Scrum may be, while not enough to pass with flying colors, at least enough to merit a passing score. If for nothing else, there is a big value to SAFe training in that it will expose a huge number of people to Deming than might otherwise not find him, though in all candor I cannot imagine that anyone truly interested in creating high quality software would not find Deming on their on quest for knowledge and improvement. I find it somewhat sad the number of people in management who I have personally had to introduce Deming to over the years. Then again, if the folks I help become agile had prior knowledge of Deming would they have a need for me?

Managers from Hell and Agile Transformation

larry apke, whiteboard, agile

larry apke, whiteboard, agile

“Here’s something they’ll probably never teach you in business school: The single biggest decision you make in your job — bigger than all of the rest — is who you name manager. When you name the wrong person manager, nothing fixes that bad decision. Not compensation, not benefits — nothing.”

Jim Clifton, Chairman and CEO, Gallup – State of the American Workplace

A few months back I stumbled onto some research done by Gallup on employee engagement quoted from above. I would like to say that their findings were shocking, but having been an Agile Coach at many large organizations, I find the statistics (and conclusions based on the statistics) to track quite close to my own experiences.

For example, Gallup found that only 30% of all employees in the United States are “engaged and inspired at work” and about 20% are what have been defined as “actively disengaged” employees who “aren’t just unhappy at work; they’re busy acting out their unhappiness. Every day, these workers undermine what their engaged coworkers accomplish.” The remaining 1 out 2 workers are defined as “not engaged” and “essentially ‘checked out.’ They’re sleepwalking through their workday, putting time — but not energy or passion — into their work.”

And take a wild guess what the number one indicator of employee engagement is. You got it – their manager. In another article, Gallup estimates that “companies fail to choose the candidate with the right talent for the job 82% of the time” (Why Great Managers Are So Rare). In other words, next time you are in a meeting with five managers, it is safe to assume that only one (maybe two) were the result of good hiring decisions. If you are a good manager meeting with other managers chances are good that everyone you are speaking with was the result of a poor hiring decision!

The fact that management hiring decisions are so poor should be of some comfort to you the next time you are passed over for the management job you know you can do well, but is little comfort to active agile coaches like myself who are actively trying to help a company get agile and stay agile. On the other hand, knowing this goes a long way in explaining why most companies have so much trouble with the transformation.

Without the support of managers, lasting agile transformation will not occur. The fact that the bulk of your managers are poor leaders just makes it that much harder. Gallup estimates that only 1 in 5 current managers have the abilities to “naturally engage team members and customers, retain top performers, and sustain a culture of high productivity.” Agile is all about engagement. It demands leaders who can engage developers.

So you say you want to be agile? Why don’t you start with hiring better managers? Stop relying on third-party vendors to find your talent. Grow your talent. Recruit your own talent. Find CIOs, VPs, Directors, Managers, Coaches who understand agile, can truly lead agile teams and engage developers.

Go ahead. I’ll be waiting for your call. Of course, it may be a long wait.

“Are You Crazy?!” – Project vs Product Focus

eco-data, larry apke, agile doctor, product focus

eco-data, larry apke, agile doctor, product focus

When You Have A Project Focus

Coach: If we take some time to learn and adopt excellent software development practices like BDD/TDD, CI and refactor some our code to remove some technical debt, we will be able to development higher quality software and deliver it to our customers faster.

Project Manager: Are you crazy?! We are already behind schedule! We cannot take on anymore work. This would increase our risk of delivering desired functionality!

Coach: But fixing some of these issues will allow the team to create better code and reduce the cost of delivering in the future.

Project Manager: Future. I am concerned with the delivery next quarter. After this project is completed, we transfer the code to the maintenance team. Let them do this work, I don’t want it charged to my project. Besides, the development team on this project will be disbanded at the end of the project.

Coach: Are you crazy?! Disbanding the team? All the progress we have made as a team is lost as soon as you disband the team. You cannot build a quality product when you keep shuffling teams! Keep them together and bring the work to them.

Project Manager: How much are we paying you? We need to save some money.

When You Have A Product Focus

Coach: If we take some time to learn and adopt excellent software development practices like BDD/TDD, CI and refactor some our code to remove some technical debt, we will be able to development higher quality software and deliver it to our customers faster.

Product Owner: That sounds awesome! I will work together with the team to understand the long term return on investment of doing these things, we will create some stories to handle this work and prioritize appropriately.

See what I mean?

Larry Apke

Story Points Revisited – Presentation

story points revisited, larry apke, agile

If you missed it, here’s my newest presentation about story points that I gave to the Phoenix Scrum Users Group yesterday.

Here is also a cool video of the meeting that Alan Dayley shot using the new Hyperlapse app.

Thanks for everyone who came out! I had a lot of fun.

Larry Apke