Bob's Blog
Bob is a prolific blogger who simply enjoys sharing his experiences with colleagues in the Agile Community. Topics revolve around Scrum, XP, Kanban, Project Management, Business Analysis, Testing, Leadership and General Musings.
Check back often as we've always got something to say...
There has been a drumbeat for many years that we need more diversity in the ranks of corporate leadership—particularly women. It’s been increasing in tempo, loudness, and duration, but we still struggle. In this 2021 McKinsey report, women make up only 24% of C-suite roles, and women of color, only 4%--while we’re making progress, indeed, there is much work!
1. Customers don't care if you're agile, waterfall or otherwise.
They care about their experience & that your product helps them. Focus on the quality and frequency of your interactions with customers.
2. It won't solve all of your problems.
Agile isn't a panacea. It'll just expose your problems quicker. The core of Agility is that it builds in feedback loops. It's up to you to learn from them and adjust from there.
3. Telling people, they have psychological safety isn't enough.
You need to demonstrate that people are ok to fail through action, not just words. Celebrate failure, be intentional about creating a safe environment.
I saw this point on LinkedIn from Leise Passer Jensen and it resonated with me… powerfully.—
No-one could have warned me about this prior to my first leadership job:
𝙄𝙛 𝙮𝙤𝙪 𝙝𝙖𝙫𝙚 𝙥𝙤𝙬𝙚𝙧 𝙤𝙫𝙚𝙧 𝙤𝙩𝙝𝙚𝙧𝙨 𝙮𝙤𝙪 𝙢𝙖𝙮 𝙡𝙤𝙨𝙚 𝙞𝙩 𝙤𝙫𝙚𝙧 𝙮𝙤𝙪𝙧𝙨𝙚𝙡𝙛.
This is scary:
Contemporary research now shows that…
… everyone is predisposed to abusing power. So that includes you and me.
The most dangerous threat for leaders is …power.
Power corrupts and may change your brain.
Its consequential behavior can harm ourselves and others.
Few people were told this before they accept an appointed leadership role. That can be dangerous for us as leaders as well as for those who are subjected to our leadership.Power changes the brain!
I just saw the announcement for SAFe 6.0. WoooHooo!
Just when I needed it, Scaled Agile anticipated my needs and delivered another, even more chock full of value scaling toolbox.
It inspired me to try and visualize how it’s become increasingly more helpful over time. So, here goes…
Anthony Mersino is a good friend and colleague of mine, and he asked the following question:
What are the disadvantages of using agile and Scrum?
And it made me think a bit. Not only about the question but what would be the best way to answer it.
At the risk of offending some, I kept thinking of a car. Putting the pollution aspect to the side for a second, cars are inherently good. They’ve provided transportation to humans for well over a century. They’ve also evolved, becoming safer, more efficient, and more intelligent. They’re even beginning to self-drive, which is an exciting development.
But then I think the primary disadvantages (or problems) are not in the cars themselves, but in the users—us. It’s how we use them that’s the more significant challenge. For example, driving recklessly or under the influence. Not maintaining them safely. Or allowing unlicensed/inexperienced individuals to drive them too soon.
We discussed the latest round of agile role layoffs at Capital One the other day in the Moose Herd. The news was that Capital One had laid off 1100 people, all with agile in the titles/job families. The public reason shared was that they’d sufficiently evolved their agile capabilities to a point where it made no sense to have independent roles. That (everyone) was now agile.
Of course, there was quite a passionate discussion about—
What are the fundamental driving forces behind the move?
Was this a perceived success / evolutionary step or a failure?
Since Capital One was such a bellwether, was this the beginning of a trend in the agile community?
What might happen to all of those people?
I was pretty struck by the turbulence that this one event created in our community, as the Herd reflected.
One of the things we got heated about was the intentions of the organizational leaders, particularly exploring whether they valued agile or not. And whether they valued people or not.
I forget when I first thought about this idea, but it’s been several years. It’s about taking a service-oriented view to agile coaching.
One genesis point for me was talking to an agile transformation director leading a team of coaches. He lamented that his coaches were constantly pulled in multiple directions well beyond their capacity and skills.
I brainstormed with him about whether a service-oriented mindset or approach would be helpful to him. And we defined that as—
Define a set of coaching services that his team would provide;
Define Service Level Agreements (SLA’s) or delivery agreements for each service;
Market the services to the organizational stakeholders;
Manage capacity (across services, across coaches, and unique skills);
Perhaps on an annualized basis, reevaluate service outcomes, needs, and rebalance the investment in the team.
One problem he was experiencing was the incredibly broad skillset assumed by his coaching team. That is—they can coach in any situational context. Which certainly wasn’t true. A service orientation would not only define what they would provide but what they would or could not provide.
The 2022 Agile Coaching Report sat in my inbox for almost two months until I finally reviewed it in detail a few days ago. Several areas were worthy of a deeper dive, but one particularly struck me. The report's preface reads: "Notably, coaches believe the biggest impact they are making is in shifting an organization towards an agile mindset and culture. Interestingly, they also find this to be the most challenging shift to make and one of the biggest impediments to agility if not achieved." This sentiment isn't surprising to most who have worked in an organization transforming toward more agility. It's an issue Agile Coaches, Scrum Masters, leaders, managers, and team members run into often.
It's not surprising this shift is difficult because a transformation of an individual's mindset requires an internal change in their value system, which is not only what they say they value but what they believe they value. Unfortunately, leaders, managers, and stakeholders often say they value the agile transformation or value delivering useful products or services to their customers but underpinning those statements is a desire for more money, more accolades, more acceptance, and more power. There's nothing inherently wrong with some of these underpinning values, but it's essential to understand the true driver of the desire to change. It's important because our job as coaches is to nudge them toward more agile ways of thinking. And to do that, we must understand where the individual's values are rooted.
2022 was a topsy-turvy, hold-onto-the-rails kind of ride for me. Here are just a few highlights—
I published my Extraordinarily Badass Agile Coaching book in January.
I followed up with an audiobook version in July (my first).
I delivered in-person coaching again at several organizations, and it felt strange but good.
From a revenue perspective, and this surprised me a bit, this was the second-highest year in the 20-year history of my consulting practice.
I spoke at many virtual conferences and events. Particularly in the areas of agile leadership and coaching. One of my favorites was a pair of Ask Me Anything sessions at Scrum Masters of the Universe.
I was fortunate to go on-site at the Denver Scrum Gathering and the Nashville Agile Conference. At the Agile Conference, Jen Fields and my session on agile coaching was standing room only, AND the EBAC book sold out at the bookstore.
I did more pro bono coaching and mentoring than in any previous year.
I granted over $25,000 to CAL students with my DEI discount program.
I closed the year by running an experiment called Badass Agile Coaching Day. It drew over 190 attendees and generated proceeds of over $6,500 which I split across Agile for Ukraine and Africa Agility (see below).
And that’s just a sample…
I saw this post on LinkedIn the other day from Julie Springer
“So… this all sounds great, but are you going to provide this same training to our leaders?”
I’ve heard this question multiple times, and the underlying message is clear.
Teams are being asked to work in new ways, without any confidence that their leaders are going to make changes in the way they lead or approach their work.
It’s unfair to train teams on how they are empowered to self-organize to deliver value if nothing around them is changing.
Start with a vision for the change at the leadership level and get clear on what structures, approaches and behaviors need to be in place to support agile teams, before providing training and inviting them to work differently.
There’s a nice dialogue of comments and reactions to the post that I recommend you read. That being said, I didn’t see a quick point I’d like to make…
