Communication is important…and it’s hard. How’s that for profound? I am loving working in an Agile environment. Of the multitude of kinks we need to work out, most of them center around the lack of consistent, effective communication. We all know these two:

And I think we all love them. But check this out:

1. BA does some analysis and gets a story up (the right way)
2. Story gets plopped in an iteration (the right way)
3. Story get chewed up a bit (you know, folks just responding to change per the manifesto)
4. Individuals start to interact in order to get the story right
5. Everyone is happy. But your comprehensive documentation (produced by BAs and Testers) is not so comprehensive anymore

Some folks can deal with this. Others cant. Others dont want to. Was the change communicated well and to the right people? They *were* happy. Hard to tell in this scenario. I can’t rightfully account for the “cants” and “dont want tos.”

This on a day that started with a deep dive into Acts 14. I found myself giggling on my way to the study. Imagine a bunch of semi-literate cavemen going nuts as your throw down the Gospel. You don’t know their language but they are clearly psyched. You are praising God but also shamefully patting yourself on the back for your masterful ability to communicate effectively.

That’s right about when the priest of Zeus shows up with the filthy stinking farm animals. You know the rest. Paul = Hermes. Barnabus = Zeus. It doesn’t say, but Paul may have enjoyed that mistake for just a second…

Hermes is generally known for his looks, a claim Paul can’t generally make. At any rate, Paul realized the communication issue pretty quickly. Response:

• Tear shirt (convey to your audience that they misunderstood the message)
• Start over (revise and redeliver the message to ensure understanding)

Maybe we need to start tearing our shirts more. Or…maybe it’s the other one.

Senour: Theoretically, these posts would be a mixture of professional and personal posts that would:

1. Establish a personal persona
2. Establish a professional persona
3. Provide a home base that links out to social media sites (FB, LinkedIN, etc.)
4. Highlight some photos/videos of interest
5. Highlight some web-based project
6. Do some other stuff

Additionally, it could be a place to promote the good work of other folks who are providing thought leadership in our areas of expertise.

As an example, I’d link to a particularly good post by a top notch BA thought leader like Jonathan Babcock:

Solid blog post by Jonathan Babcock. Photo from the post:

Would love to hear your thoughts on this, Mr. Reed.

TP

There should probably be a limit to the number of times that you an start and stop a blog. I’d probably be close to it. So here goes again. Lately, I’m quite smitten (and consumed) with these guys (no offense, Luke):

Perhaps you can see why.

I’m also trying to do a lot more reading this year. My newly acquired Kindle will theoretically make that easier. For now, it’s The Road on the fiction side. A bunch of Agile books on the work side (including Lean-Agile Software Development. Acts on the spiritual side (entering the eleventh chapter now). And one can never stop reading any output from Jay Nordlinger.

I’ve got some fun side projects on my plate for the year. Perhaps I’ll convince some folks to help me out.

Later.

Twitter: toddpollock

• Go Jabian! http://bit.ly/cReph5 01:59:07 AM August 26, 2010 from Twitter for Android