This week I’m speaking with my esteemed colleague Shaun Smith at an agile event.
Individuals and Interactions: The Forgotten Priority
We chose to focus on one of the agile oldies. The first thing we state in the manifesto. Because people and interactions are usually forgotten when we start to plan for change. We all too often dive into creating programmes and long term plans and BIG CHANGE.
Our session hopes to attempt to redress this balance, challenge some assumptions and make sense of why this is. Or maybe we’ll just tell some stories. Depends on the people present and what would be more enjoyable and useful for them.
See what I did?
We chose to put the people over the process (or in this case the powerpoint)
We won’t plan it to death and we have one simple outcome – to help people think about how they interact with people when planning and inspiring and managing change.
“I’ve learned that people will forget what you said, people will forget what you did, but people will never forget how you made them feel.”― Maya Angelou
I often work with other coaches and this is usually a good thing. Sometimes though I get dismayed at the number of “experts” who want to force people to change to doing things their way.
When I come across peers who want to do change “to” people instead of explore “with” them I often think of a story I heard many years ago. So long ago in fact that I can’t remember the details but here goes anyway.
Some volunteers arrived in a small village in Africa. Their aim? To tackle the childhood malnutrition that besieged the area. Of course there had been others before them. People who lectured, people who taught, people who tried their best to get the villagers to do things their way. But the people resisted and no-one knew why.
A smart young volunteer had observed that a few of the local babies seemed well fed. These families in general were not suffering in the same way. The volunteer decided to find out the secret of these well-fed babies. She proceeded to learn the language and communicate with the families of these children. As the trust grew in these relationships the volunteer discovered more about these parents. They would take a local worm or insect (ah my middle-aged memory) and grind it into the milk. They then fed the babies and young children this mixture.
Now the village knew that this particular form of protein was edible. Yet the villagers deemed it beneath them to eat and so many did not even consider it.
With this volunteers help the mothers of the well fed children stood up and told their neighbours what they had done. At first the villagers were not entirely enthusiastic. But some courageous first followers tried in secret. And soon the village had much less problems with malnutrition. Success in any language.
I love this story because it shows how simply taking time to see, and being open to the unthinkable, can make the difference between life and death.
Of course in our professions we are rarely faced with such choices. But even in our pedestrian world, it is just better to do things with the people involved. Not to them. Be open. Be courageous. Be wild.
He took “protecting the team” quite literally. So every time someone disagreed with the product owner, or had bad news or a question to share…he did it for them.
The battles between scrum master and product owner were painful. As a distributed team (UK/US) they needed to make the most of their opportunities to work together. But every time they tried to do some planning there would be many misunderstandings and disagreements. And usually people left the conference call feeling low. After a while the team just stopped delivering.
So, behind closed doors, the angry scrum master and I had our first coaching conversation. And much to my surprise the angry scrum master was a caring but frustrated individual. He was stressing and striving to do all he could for his team’s success.
Over the course of our chat he came to realise that “protecting the team” did not mean inflicting help on them. Or always doing it for them (whatever “it” may be). We spoke about how it had affected his relationship with the (influential) PO. We spoke about how that in turn had affected how the team felt and how if had affected their work. We spoke about how he felt at the end of each day.
He changed his outlook and made some resolution when that first meeting ended.
Encourage the team members to speak for themselves. If they can’t make the sprint commitment – speak up. If they had a question for the business or each other – speak up. And if there was something that the team just couldn’t agree as a sensible thing to do – speak up. He realised his job was to help them feel comfortable opening up and to help them be mindful when someone else was sharing.
In just a few short weeks the relationship between PO and scrum master recovered quite well. The team meetings became joyous, raucous exchanges of ideas, thoughts and personal commitments.
“Why do so many use trad methods to influence agile change? I prefer to talk to people, get their input, iterate and continuously publish…”
and it seems to have struck a chord.
The ever growing popularity of agile is creating huge need. Need for experienced people to help organisations start doing things better. Because of this emerging massive need we have a surplus of Agile methodologists all selling their own brand.
Often the drive to install the method means people forget people and interactions over and above process.
I recommend this post, It describes how an agilist sees the usefulness of methods…vs how traditional thinkers view it.
I have to be honest. There’s a wee bit of jealousy in me that Daniel wrote such an insightful and informative post. It can be hard to know what’s interesting for anyone who happens upon your musings. I could sit write about the mechanics of Agile methods. But that’s already out there (see Scrum Alliance, LeanKanban University, Scaled Agile Academy, amongst others ) . I never thought about writing about training I’d been on! But I will follow Daniel’s excellent example from now on and take better notes.
So I thought I’d share a less eloquent, but I’m hoping, somewhat informative run down of the training I’ve been on recently.
Problem Solving Leadership Workshop with Gerry Weinberg, Esther Derby and Johanna Rothman Albuequerue, NM
This week long residential look at yourself has to be the best investment I have ever made .
It’s tough going. You are often working from morning to evening and having one to one consultations with Gerry, Esther or Johanna. When I say work I mean experiential learning. In my case my biggest lesson was Gerry himself telling me to “Shut up or get out”. In the middle, when you’re already a little weakened, if truth be told, there is a complicated exercise. We were a proper little town for several hours that day.
Throughout there were tears and tantrums, crushes and friendships formed and deepened. In fact I find myself in the twelve months since wishing there were a regular way to reconnect with the group I went with. After lots of imparting of psychological knowledge, and treatment dare I say, the trio of wisdom task you with a few last things to ensure lasting effect.
No there were no drugs involved 😉 it was not a love in – it was about becoming a problem solving leader. Bugger the title, it was about helping people around you and being true to yourself doing it.
Today I can say I continue to learn more about others and myself every day thanks to Gerry, Esther and Johanna. They run PSL bi-yearly. Just go. You’ll also come away with tons of models and tools to use. But better still you’ll come away with more knowledge of yourself to offer.
I agree with pretty much everything Daniel says. And he says it better.
All I can add is I liked hearing the stories from Dean himself (although even his business tales were about tech upgrades). It adds a certain je ne sais quoi to the spaghetti throwing.
I had some confused looking tablemates throughout.
Coaching with Johanna Rothman, London
This was a one day course with Johanna that I booked during PSL. It was full of useful information although some of the exercises with stickies felt basic. I suspect this is because most peeps were there to learn how to start using coaching skills. As an experienced coach I came away with a few extra tools in my belt, and of course Johanna is delightful to learn from as always.
Kanban Coaching with David Anderson, Vienna
I went with some deep expectations and came back with a round tummy (sacher torte yummy) and lots of marketing materials. There was no experiential side. Although there was sumptuous food served every two hours. Not a lot of kanban theory or practice. Mainly stories, and mainly dev team focused.
David had some interesting stories to tell and this was lecture style teaching. A large part of the content was about marketing Kanban, commercial restrictions. On the last day David explains that we must fill out an case study style application. We must then attend (and pay for) a further event in order for a panel to interview you. After this you might receive a Kanban coaching certification.
My Scrum Alliance CSM was many years ago now, and I have to say as someone who knew Scrum already it’s hard to be a fair judge – although it may be interesting for y’all to know that CSTs are not subject to PDU or quality reviews once they’re certified.
A common one in recent years are the people who have been using Agile since the 90’s. My favourites are those who have been agile coaches for 15 years plus.
For one simple reason. The term Agile was coined in 2001. For more details on the back story have a look here. You could of course have been using one of the methods or frameworks that spring up in the nineties…but Agile it was not yet.
To find out if your consultant is using buzzword bingo instead of being specific about what they used, or are simply employing a marketing trick to make you think they are more experienced than they really are…read on.
When a resume says Agile pre-2001 ask for more details. What do they mean by Agile? Ask them to explain it – if they don’t use any of the principles and instead offer another explanation be wary – they might be the type who are really asking Psst. Wanna buy an agile? Ask what frameworks or methods they used. Ask them to get specific. Then look them up on the bodies that train, teach and have communities in those methods. There are often clues when you explore each role more with candidates. Try asking what a typical day was like at their pre-2001 coaching engagement, this will often produce clues to the real role they played.
All too often people forget what was learned in a training session or struggle to apply what they have learned to real-life. Coaching enhances and extends training by helping people to understand what they have learned and how they can leverage it to their advantage in a real-life situation. Coaches work closely with you and your people, pulling information from across the organisation and supporting you in defining what success looks like. An Agile Coach will help you set goals and support you in discovering the right way for your organisation to use Agile to your advantage.
Coaching can be effective for short and long term purposes. Short term coaching is usually focused on specific activities, for example coaching a team’s planning meeting or helping groom
I spend as much of my time reading and investigating the coaching side of my business, as I do in keeping up-to-date with Agile. I also spend a considerable amount of time learning about psychology, anthropologies and general management theory..and all of the above play an integral role in shaping how I chose to interact with teams or individuals I coach.
I am a CSM and CSP for 4 and 2 years now and I started my application to become Certified Scrum Coach about a year ago. The 25 questions and case studies scared me. I found some questions very odd – for example when did planning poker become a coaching technique? Isn’t that an Agile practice instead? And how can I define advisory and consultation skills vs facilitation skills vs leadership – aren’t these all facets of a good coach..i.e. the coaching skills asked about earlier.
In addition I suffer from acute procrastination when faced with documentation.
I picked it up again this year with fresh vigour and spent approximately 40 hours of hair tugging, brain dulling recantations of every Agile and Scrum experience over they years. I was then forced to distill these into the top three style question that permeates the CSC app. So far I have managed a grand total of 15/25 questions and the ubiqitous case study.
Still on high with the prospect of what I see as a valuable opportunity to get feedback from my peers I received an email prompting about my CSP renewal.. Read More