Drunken PM

Click here to go straight to the podcast.

A few weeks ago I had the opportunity to interview Ron Lichty, Agile throught leader co-author and of Managing the Unmanageable: Rules, Tools, and Insights for Managing Software People and Teams. One of the great things about the books is that Ron and his co-author Mickey W. Mantle have culled their collective experience and offered up a set of tools they have found useful over the years in working on software projects.

Ron and Mickey take the approach that software developers are a unique group within the knowledge workforce and that they require an adjustment in how we treat them, how they treat each other and what we can do to help them work with non-developers.

One of Ron’s current areas of focus is rooted in the question of “Why do we need managers if Agile teams are supposed to be self organizing?” Ron’s has found that only about 5% of software managers have had actual training in how to manage people. We basically just expect developers to be able to move into a managing role and just know how to do it based on their experience in not being a manager. Ron looks at the critical role that management can make in helping companies transform to Agile and the importance in making sure that they are trained both in management AND in how Agile works so that they can be better prepared to help, rather than impede the Agile teams as they are getting off the ground.

• You can learn more about Ron, or the tools he and Mickey have put together, you can find them on his website RonLichty.com
• You can find the podcast interview here.
• Ron’s book “Managing the Unmanageable: Rules, Tools, and Insights for Managing Software People and Teams” can be found here.

A few weeks ago I had a chance to interview Kamal Manglani for Projects at Work. Kamal is an Agile coach who has written a book, The Apprentice and the Project Manager,  that was recently released on Amazon and HappyAbout. 

(check out the interview here)

The book includes a narrative based in the past and the present. Stories from earlier work experiences as an apprentice mechanic and current experiences working as a technology project manager are used as a metaphor to explain some key concepts that factor into Agile and Lean. 

Explaining an Agile process/framework as a call and response narrative is not a new approach, but what is unique and refreshing about Kamal's book is that in taking a practical approach to getting work done and coping with very specific situations, the author has made a choice to steer clear of promoting one method over another and just kept it to a very pragmatic, straight up approach. 

If you are new to Agile and/or Lean, this book would be a great starting place to introduce some of the key concepts without drowning you in jargon and trying to sell you on having found "THE WAY". 

For me, as someone who has spent a lot of time working in both traditional project management and in Agile, my favorite section of this book was the chapter on Financial Health. It is great to see a book for people who lead projects include an easy to understand explanation of why it is so important to factor finance into our decision making process and how to go about doing that in a responsible manner. 

You can check out the Apprentice and the Project Manager at Amazon or HappyAbout.

In December I wrote about how I was going to start experimenting with adopting Non-Violent Communication. And I am, sort of. I’m finding that this is probably going to be an ongoing effort and one I will need to keeping coming back to. What I have been doing so far has helped me check in with myself and come to this:

When I see that__I am not making good on my commitment to practicing NVC_

I feel _bad/frustrated/anxious_

because my need for _trying to figure out if I can actually do it_ is/is not met.

Would you (I) be willing to _man the hell up and give it a frigging chance__?

To be fair, I do spend an inordinate amount of time pondering it each day – especially when I’m driving… and get cut off by someone who very clearly has a more urgent need to get someplace than I do.

When I see that__ some &*%^%!! has cut me off_

I feel _like I wish my car came with a rocket launcher_

because my need for _deleting him/her from the road/universe_ is/is not met.

Would you be willing to _oh nevermind__

My intent in writing about this is, in part, to express that while I am working on it, I am honestly struggling with adopting NVC. A lot of how I have learned to communicate seems to be at odds with NVC practices. It is important to me, in writing about this, that I be as transparent and honest about how it is going as I can because if there are other people like me who are struggling with this (read: grew up in Philadelphia), I would like to make sure they know that they’re not alone. And to consider that maybe having trouble with this is not necessarily a bad thing, but is perhaps more about letting the dissonance from the conflict reach a level where change happens. My experiment is to see if I can adopt NVC as a practice of (initially) communicating and (ideally) of approaching other aspects of my life.

My practice (or not) so far has basically involved me noticing how I react to things, like being cut off while I’m driving or some other social injustice, which has been done to me by someone. Typically, the social injustice has very little to do with the other person and is really just me spazzing out in my reaction to something I have decided is a great crime against all things good in the universe. But, if I did have a rocket launcher, I’m pretty sure that by this time, very few people would be willing to cut in front of me in line at Walmart.

Because I have decided to don my cloak of self imposed guilt for not automatically laying down the communication habits I’ve developed over the past 40+ years in favor of a non-violent approach to life, the universe and everything, I have become hyper-aware of how non non-violent my speech actually is. This has led me to wonder if perhaps I am not more suited for a new approach called UVC – Ultra Violent Communication.

I do believe that this awareness, is very important. I do not know yet if I will be able to adopt NVC. I do know that while I am able to understand that it is more than just a communication pattern, I have trouble internalizing that. (Much the same way some people respond to the idea of a team being self organizing by winking at me in class and whispering “Yeah, but really… who’s really in charge?”). I also have observed that letting myself freak out about someone cutting me off on I-35, or having the insane gall to try and get past TSA with a bottle of water in their backpack (Whiskey Tango Foxtrot) gives me a bit of an adrenaline rush. Yelling a string of obscenities from within the safety of my car at some motorist I do not know, helps no one, but the release of anger is a boost, and I have become aware that a) the outburst does nothing to change the situation in any way and b) the pull of the boost can be a wee bit habit forming. The more aware of this I become, the more I am finding that when I recognize an of an event and become aware of my emotional response, there is an increasing delay now before my reaction triggers. More and more, that delay is becoming large enough that I have the time to make a deliberate decision about what is going to come out of my mouth.

So, in on the whole transparency front, I’m not really delivering on my intent with non-violent communication yet, but in my continuing efforts to get there, the awareness is helping me cultivate a slightly less-violent communication… at least most of the time.