Less Scorn, More Listening

I got a tweet this morning about the new VersionOne "State of Agile Development Survey" in which the re-tweeter used hashtags like #shocking and #fail. Looking for a good laugh, I clicked on over to the survey, and realized I #liked the survey and I thought it was #interesting and #helpful to me. I didn't find anything that jumped out to me as a #failure in a particularly #horrifying way. Then for a moment I thought maybe I am not one of the #Agile Cool Kids. Of course the moment was brief and I bounced back quickly--please don't worry.

But as I thought it over, I realized I myself used the phrase "that's CRAZY" yesterday for a perfectly reasonable management reaction to a difficult personnel situation on a team.

http://www.triumphtheinsultcomicdog.com/

Have you ever thought about how much elitism and scorn we carry around with us in the Agile world? Every question becomes a target for someone to poop on, as Triumph the Insult Comic Dog would say. Do you use written requirements? Aren't you collocated? Do you still have silos? Do you still have a PMO? Does your firm have management? Are you working for The Man? How many Agile Manifesto signers do you know? Do they think you're cool? Are you still using Sharpies with caps instead of the ones that click? It goes on and on.

On the other hand, one thing we do too infrequently is stop to listen to each other and to our clients. By "listen," I mean more than just "waiting until the other person stops talking before getting to say what you are dying to say." You may be surprised if you actively listen to what other people are saying, rather than thinking you know what they are saying, because they've said it 1000 times before. Did you know--stay with me--that people only hear between 25-50% of what you say? (You skipped that, didn't you?). Listening is a good skill to have, and being agile doesn't make you exempt from having to do it. In fact, the fast pace of most agile projects and their reliance on spoken communication make real listening vital (at least until you know your fellow team members well enough so that you really do know what they're going to say all the time). (KIDDING!)

Just stop. Listen.

It's okay to feel distress on behalf of others who don't share your point of view, but it's not ever going to be productive to poop on them.

Comments

How Do You Vote Someone Off of Your Agile Team?

One of the conundrums of agile conversion is that although you are ordered by management to "self-organize," you don't get to pick your own team. You may not have pictured it this way, but your agile team members are going to be the same people you worked with before, when you were all doing waterfall! I know I wasn't picturing it that way for my first agile team, so I thought I should warn you. (I thought I was going to get between six and eight original Agile Manifesto signers. That didn't happen.). Why "warn" you (as opposed to "reassure" you, say)? Because the agile process is going to reveal every wart, mole, quirk, goiter, and flatulence issue on the team within a few hours. In the old days, you could all be eccentric or even unpleasant in your own cube, communicating only by document, wiki, email, and, in extreme situations, by phone. Now you are suddenly forced to interact in real time, perhaps in person, with written messag

A Corporate Agile 10-point Checklist

I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today. Some of these might even apply to you if you're in a smaller place. So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else. From http://www.yogawithjohn.com/tag/yoga-class/ Here's what you should think about: 1. Your staffing pattern. A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios. So as you provision the project, check to see whether you can arrange this staffing pattern. If not, you will encounter risks because of missing people. Concretely it means that: a. You need your user experience people (if a

Your Agile Transformation Needs to Start with a Quiet Phase

From a really great blog post on agile adoption: http://smoovejazz.wordpress.com/2011/02/16/an-agile-approach-for-adopting-agile-practices/ I've observed some different agile transformation patterns, and maybe you have too: Just Do Standups (Shoot, then Aim): some people feel that since you're "agile," you should just start doing stuff, like daily standups, and then build more of the the plan as you go. Find a team and start doing some agile with them! Start a revolution one practice at a time, one team at a time. Pros: you're very busy from the start. Cons: what exactly are you doing and why? KPI-Driven Change (Aim, then Shoot) : some people who have worked in large corporations for a while will tell you that to get the respect of the people, you need to start with a plan, support the plan with awesome printed and online collateral. Then you "kick off," tell teams what to do, and measure them using "Key Productivity Indica

Pragmatic Agilist

Search This Blog