Skip to main content

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.
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.

Popular posts from this blog

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.

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 applicable) and your analysts at the beginning of the project, as always, b…

The Agile Business Case

Many agile teams have never seen a business case, ever, and they may even be proud of it.

Our mantra is that we deliver "business value," not just "software," quicker, better, and faster, but if so, we certainly don't spend a lot of time reporting on value delivery, and in fact we may be scornful about "analysis paralysis."  As software developers, we consider ourselves to be doing quite well if we can deliver the software every two weeks (or continuously).  And this is particularly if we've enabled this frequent high-quality delivery through automated testing and automated build-and-release techniques.  We've reduced business risk by making results visible more often, and allowing the business to change direction more frequently.  We assert that along the way of course we're also delivering value.  But how would we prove it?

I've recently posited that we shouldn't even think of doing agile projects without capturing and recording s…

Requirements Traceability in Agile Software Development

One of the grim proving grounds for the would-be agile business analyst (henceforth "WBABA")  is the "traceability conversation."  Eventually, you will have to have one.  You may have seen one already.  If you haven't, you may want to half-avert your eyes as you read further.  It gets a little brutal.  But if you close them all the way, you can't read.
WBABA: in summary, we complete analysis on each story card, and then we support the developers as they build it that same iteration!Corporate Standards Guy:  but how do you do traceability in agile?  You have to have traceability.  It's broadly recognized as an important factor in building rigorous software systems. These software systems permeate our society and we must entrust them with lives of everyday people on a daily basis. [The last two sentences are an actual quotation from the Center of Excellence for Software Traceability website!] WBABA: [cowed silence]Corporate Standards …