20 Years of RGalen Consulting Group

1 Comment

20 Years of RGalen Consulting Group

I was reviewing LinkedIn one morning, as I often do, and I noticed a note from Myles Hopkins of Be Agile that he and his firm were celebrating 20 years of service. First, congratulations Myles! But second, it made me think about the longevity of my own firm—RGalen Consulting Group. And it hit me!

In August 2021, I’m going to be celebrating 20-years of consulting service to my clients. Holy Cow!

Happy Anniversary

I thought I’d share a timeline of sorts…

1 Comment

A Leader’s Prime Directive

Comment

A Leader’s Prime Directive

A leader’s primary job or Prime Directive is not to—

  • Find people to fill out the org chart; or re-org;

  • Get things done, predisposed to action;

  • Drive revenue, ROI;

  • Solve problems;

  • Connect to customers or create value;

  • Envision the future; develop strategy;

  • Grow their responsibility & impact.

Instead, it’s to be a catalyst in creating, building, and growing an organization that can do all of these things…and more!

Agile leaders out there, is that YOUR Prime Directive?

#itsnotaboutyou

#build, #grow, #create

Stay agile my friends,

Bob.

Comment

More?

Comment

More?

I was in a coaching conversation the other morning with another agile coach. They brought up a scenario at work where one of their key stakeholders (executives) had said something like—

I’m fully on board and bought into what you’re focusing on in the agile transformation…

And I stopped them.

As I thought about it, the thought that kept coming up was this—

  • Being supportive of;

  • Fully backing;

  • Having their buy-in;

  • Being on board with.

Isn’t good enough for leaders when you’re a coach in an organizational transformation. Sure, those words are nice and appreciated, but I was thinking they are just table stakes. That the coach needed MORE from the stakeholders.

Comment

Is experience the only thing that matters?

Comment

Is experience the only thing that matters?

Cliff Berg shared the following article on LinkedIn. It’s a view that to be honest, I’m struggling with. Why? I guess first, because of the privilege that Cliff has as an influential and leading voice in the agile community. And second, because I’m not sure my experience (and opinion) aligns with his…

Here’s a snippet from the article—

Let’s make this very tangible: If I needed to assemble a team to build a product, and I had a choice between ten inexperienced but smart programmers or five very experienced and equally smart programmers, I would pick the team of five, hands down. I would not hesitate one second.

And even if I had a choice between ten inexperienced smart programmers or five highly experienced but slightly less smart programmers, I would still pick the latter.

Let me put it another way: If I had a choice between five inexperienced and smart programmers, or five experienced and smart programmers who cost twice as much, I would pick the latter. In fact, if those experienced programmers cost three times as much, I would still go with them. Five times as much? Yes - I would still go with them.

While Cliff is absolutely entitled and privileged to this perspective, I passionately disagree with it.

Comment

Standish and other Oracles

1 Comment

Standish and other Oracles

I’ve been seeing these surveys and statistics reference around The Chaos Report for nearly two decades. Often, as in this article here, they are used as citations supporting agile ways of working. And since I’m an aglist, you’d think I would be in full support of them. But I have three core problems with the reports themselves and the incessant quoting of them to support some position.

Trust?

First, I’m not sure I trust the data. Where does it originally come from AND are the collections accurate?

For example, I used to fill in project timesheets at the end of each week. I filled them in with the best recollection I had and with my perception of time spent. I realized over time that I was probably only reporting at 50% accuracy. And that was as an individual contributor. Aggregate that data over 100 developers over 1-+ projects every week. Would you trust what that data was telling you?

So, rolled-up statistics collected from a wide variety of companies doesn’t always make me that trustful and confident in the data.

1 Comment

Culture Design Canvas

Comment

Culture Design Canvas

Based on a bit of a lark, I attended Gustavo Razzetti’s Culture Design Masterclass on March 19th. I’ve been wanting to get around to talking about it for quite some time, so here are some reactions…

https://www.fearlessculture.design/

First of all, the attendees were outstanding. It was a very diverse and eclectic mix of folks that were fare wider than my typical “agile coaching” colleague universe. I enjoyed and learned much from the diverse perspectives.

Second, I want to highly recommend the Culture Design Canvas as a very general-purpose tool for exploring, exposing, understanding, and potentially changing your culture. As an agile coach, I saw many applications of it in my Enterprise-level agile coaching activity.

Comment

Achieving Critical Safety

Comment

Achieving Critical Safety

As a leader, you want to hear the truth from everyone.  

I can hear what many of you are saying. No, I don’t. I want to hear thoughts that align with mine. My plans, my strategies, my ideas, and my approaches. And I’m here to tell you…

NO! You Don’t! You want the Truth!

Getting critical feedback is a skill and habit exemplified by the best of leaders. They are adept at creating an organizational ecosystem where feedback, all types of feedback are welcome and encouraged. Even critical feedback. No. Most importantly, critical feedback.

The point being, we want to be told when the Emperor (the leader, we/us, Me) Has No Clothes.

But the challenge is creating that ecosystem. One where it’s safe to speak truth to power. And not just stipulated safety, but tried, true, real, and absolute safety. Where the most critical of feedback is welcome, embraced, and even celebrated. With no immediate or later ramifications to the giver. 

Kim Scott, the author of Radical Candor, wrote a post recently entitled 11 Ways to Get Feedback from Others. I’ve long been a proponent of Radical Candor and this complemented the ideas in it so nicely.

Here are four of her TIPS that resonated the most with me around the topic of safety. I’ll add a bit of my own color commentary to each, but please read her article first.

TIP 4: Reward Criticism to get More of It

I think this starts with thanking folks for the critical feedback. Honestly and genuinely thanking them.

Another aspect is rewarding it in your coaching conversations. Noticing it and sharing how much you value the courage it takes for individuals to “speak truth to power” when that power is you.

I’ve often given people that feedback in your reviews. Of how much I value their opinions and thoughts even when they contradict my own. Emphasizing that I’m not looking for “Yes, persons”, that tell me what they think I want to hear.

Another great way to reward feedback is to actually…do something with it. Consider it, tell people what conclusions you’ve come to around it, and take action based on it. You don’t have to take immediate action on all feedback, but you don’t want to be a receiver who never takes action.

TIP 5: Ask for Public Criticism

I love this idea. That is, ask for out in the open criticism. In hallways, meetings, conferences, wherever.

But the important thing here is not the ask. While that takes quite a bit of courage, it’s not that hard. No, what’s challenging is how you respond to public criticism.

  • Do you embrace it or deflect it?

  • Do you thoughtfully consider it or argue against it?

  • Do you thank the person for it or attack them personally?

Remember to stay sharp in how you receive your feedback, knowing that if you don’t receive it well, it will certainly stop. 

TIP 6: Criticize Yourself in Public

One great way to support Tip #5, is to criticize yourself in public. No, not overtly or artificially, but in a self-deprecating way. I’ve found that one of my Super Powers is my self-deprecating humor. I found this definition of self-deprecation on Wikipedia

Self-deprecation is the act of reprimanding oneself by belittling, undervaluing, or disparaging oneself, or being excessively modest. It can be used in humor and tension release.

Don’t be afraid to criticize yourself in public and look for frequent opportunities to do so. How you show up to others can work wonders in creating the space for the critical feedback you need to be a better leader.

TIP 8: Relish Being Wrong and TIP 11: Get Theatrical

I enjoy being wrong. I didn’t start out that way though.

Early in my leadership career, I was under the false assumption that I needed to always be right. In my thoughts, decision-making, approaches, literally everything. And when I wasn’t, I kicked myself. But over time I’ve learned that it’s normal to make mistakes and to be wrong. In fact, I’ve learned to relish those times, to celebrate them as the learning experience they are, and to sometimes go over the top in my storytelling of those events.

And there’s a point to be made here. There’s criticizing when the going is easy. For example—low risk, low impact, everything is going fine, no pressure or stress. Then there is criticizing when the going is tough. When the shit is literally hitting the fan. I want to appreciate the criticism and relish being wrong under both conditions, the latter being the most powerful.

Wrapping Up

I often use Steve Jobs as a leadership example. Sure, he had many failures and weaknesses as a leader. But there were things he was really good at.

Here are two videos that I would recommend you view as a way of closing this post. The first is an example of how Jobs handled VERY public and HARD criticism - https://www.youtube.com/watch?v=oeqPrUmVz-o

I really think it’s an exemplar for this sort of thing and worth a look.

The second is short and sweet. It shows Jobs’ position on being wrong - https://www.youtube.com/watch?v=kBlc4UX9vZI

I think it’s something we all need to grapple with around criticism. Around our ego, our intentions, our perceptions, our goals, and our intentions.

Stay agile, be safe, and be critical my friends,

Bob.

Comment

Revisiting Pareto and You

Comment

Revisiting Pareto and You

I haven’t thought of the Pareto Principle in quite a long time.

It was a central theme to my 2004 Software Endgames book because of the implications of Pareto and software defects (trending, clustering, resolution, complexity, etc.) It was a rich and interesting way to view defects at the time. Still is.

Then I wrote a blog piece entitled Pareto and You – Separating the Wheat from the Chaff in 2013, where I explored the implications of Pareto beyond software testing and defects. At the time, I saw the principle as something that could potentially have broad implications beyond software and into life itself. That is, could we view it as something as reliable, consistent, and law-like as the law of gravity?

I had been thinking the answer to this was yes. That is, as long as we view it as a lens for guidance rather than a law that strongly drives our behavior, measurement, and reactions. Consider it a Pareto Compass that would guide you towards True North in your understanding of complexity.

We were chatting about agile coaching the other morning in the Moose Herd and the principal came up again. I mentioned it as a lens that an agile coach could leverage in their assessment of and navigation thru Agile & Digital Transformations. Afterward, I put on my brainstorming hat to envision scenarios in my agile coaching journey where I might be able to look at the world through a Pareto lens—

Comment

CoP and the LACE

Comment

CoP and the LACE

SAFe LACE Alert

In my last post, I shared some ideas around the value of a Community of Practice and how to re-energize it if it’s lost a bit of momentum. Please read that one if you haven’t before reading on here.

Now I want to contrast things a bit between CoP’s and CoE’s. Specifically of the LACE kind… 

Contrasting between a CoP and a Center of Excellence?

There’s another notion you’ll often hear when discussing this area. It’s a Center of Excellence or CoE. My bias is going to shine through a bit here, but please bear with me.

A CoE is a more formal, top-down mechanism whose primary goal is the consistency of practice. That is, it’s focused on regulation and governance. Often metrics and agile performance metrics are tied to it as well. A good example of this idea is the Scaled Agile Framework’s – Lean-Agile Center of Excellence or LACE[1]. And you can also see the idea often marketed or aligned with the Agile PMO or PMI’s Disciplined Agile[2].

I’ve already alluded to the two problems I have with generic CoE’s. First is the prescriptive top-down nature—where the organization tries to mandate practices. I think that’s a non-starter in agile contexts and particularly not aligned with the agile mindset. So, implementing a CoE can actually do harm to your culture you’re trying to instill or support.

The second is that it disengages from the people doing the work. Which are the very people who are part of the “community” you’re trying to create. Typically, the teams and individuals only engage with the CoE because they’re told to. Not because they’re inspired to or are invited to participate.

In my opinion, you don’t create an agile culture by top-down mandate. It’s just doesn’t work. Instead, the organic nature of building a community of practitioners aligns so much better with our agile mindsets.

And the third challenge with creating a balanced and effective CoE relates to the agile maturity of the leadership team. If they’ve not evolved to an agile mindset, across leadership, then the CoE often becomes a mechanism for reinforcing controls and measurement.

All of these lead to problems if your goal is to truly develop and mature as an agile organization. So, approach LACE and all Centers of Excellence with caution and care.

 Stay agile my friends,

Bob.

 

 



[1] https://www.scaledagileframework.com/lace/

[2] https://www.pmi.org/disciplined-agile/people/centers-of-excellence

Comment

Community of PRACTICE

Comment

Community of PRACTICE

Dare I say it, it’s a—Community of…

PRACTICE!

I was in our Moose Herd the other day, yes, you’ve herd me say that more than a few times in blogs ;-)

And we were talking about Communities of Practice (CoP’s) as a phenomenal way to “raise the bar” in agile organizational contexts.

Everyone was aware of the practice and had participated in them. But there was a general feeling that most organizations don’t have a good recipe for a great CoP. So, we started brainstorming some of the tactics or patterns for a Good-to-Great Community of Practice. Here are some of the ideas we explored—

Comment