Friday, September 23, 2011

Indiana Gorilla and the Artifacts of Agile

"Okay and Eric, you were working on the shopping cart ordering story, right?"

Eric nodded, but remained silent.

"And tomorrow you should be done and moving on to the Wish List story, right?"

He nodded again, still silent. He was a good engineer, never spoke unless he really had something to say.

"Any impediments?"

Eric looked around the table at the other seated engineers. None of them met his gaze, intent on their own computers. Then he shrugged and turned back to me. "No."

"Ah, excellent!" I gave a thumbs up sign to the assembled team. "Great stand up, guys, I'll see you all again tomorrow."

I happily began entering data into my uber status report spreadsheet and didn't notice the engineers talking quietly amongst themselves as they filed out.

I was cheerfully humming away five minutes later, when Hogarth wandered in. I looked up and pointed at my uber sheet projecting on the wall screen. "Man, this Scrum stuff is great! I love the daily standups. Just great to have everyone giving daily reports on their status. Can you imagine? A year ago I had to hound them for their slide decks every week and I almost never got a full report."

Hogarth cast a glance at the screen, before he flopped down near the window. Reaching out the window he pulled a branch from the tree outside. After a careful examination of the branch, he used it to point at the screen. "Pretty picture, but you know its completely wrong, right?"

"What!?" I turned to stare at him. "What on earth are you talking about? The project is going great! Look at that burndown! I just cross referenced it with my detailed MS Project file and we are at least a week ahead of schedule. We're doing AWESOME!"

Hogarth shook his head. "Nope, all an illusion. Take Eric for example, he's got a massive database integration issue that's going to end up making all of his stories crash and burn. He's stumped on how to solve the problem and it is going to cascade into a total failure of the storefront in about two sprints."

I blinked. "What on earth are you talking about? Eric just walked out of here and he didn't say word one about any issues."

Hogarth nodded, pealing a long strip of bark from the tree branch. "Course he didn't, no point saying anything if you're not going to listen to him."

"What?" I said incredulously. "We just had our stand up! I was sitting right here! I didn't set up all these Agile meetings just to have things be the same as before!"

"Just because you have the magical artifact, doesn't mean you have a clue how to use it."

"What?" I hated it when Hogarth spoke in riddles.

Hogarth rolled his eyes. "You remember in the original Indiana Jones, the Germans had the Ark of the Covenant?"

I stared at Hogarth, "I don't have time for movie quizzes, Hogarth." He gave me a "humor me" look and I sighed in surrender. "Yes, I remember. It ended pretty badly for them."

Hogarth nodded. "Ayup, they had the artifact. But they didn't know how to use it. If you put a MacDonald's fry cook in the Iron Chef kitchen, he's not magically going to become a great chef. The tools don't make the chef, the chef does."

I stared at him for a long minute.

"Ah, crap…"

Agile Artifacts vs. Agile Values: Holding Daily Standups, planning work in two week iterations, and tracking progress on a burn down chart are all excellent tools for the Agile team. They are not  Agile. Agile is a set of values and principles. It's more about the how of team and not the what of the product.

You can't take a handful of engineers, start having them meet once a day, and declare yourself Agile. Like Hogarth's examples from above, having a tool (A Daily Standup is a Tool/Artifact) and knowing how to use it are two entirely different things. And the more advanced that tool, the more knowledge you need to use it.

Back in college I got a part time job at a little coffee shop/deli (Back before Starbucks took over the world). The owner was a quiet Turkish man who wouldn't let me touch the espresso machine until after I'd learned not only the history of coffee but the why's of exactly how the machine worked (this was an old manual style machine, no automatic buttons or anything). I must have frothed gallons of milk before he let me pour a single ounce into a customer's cup. He told me, "To make good coffee, one must first understand coffee."

Success in Agile requires a look beyond the tangible of meetings, code drops, requirements documents and into the heart of how the organization runs. The values and principles are as much, if not more about the team and not the product trying to be made. Make a better team and you make a better product.

Throw around a bunch of Agile Artifacts, like a five year old using a Ginsu Steak knife set, and you just replace one bad process with another.

Joel Bancroft-Connors
The Gorilla Project Manager
Want me to talk to your gorilla? Send me an email
You can follow me on twitter, @JBC_PMP

Thursday, September 1, 2011

Death by PowerGorilla

C… O… C… L… S… I… O… N…

The typewriter sound as each letter flew onto the screen gave me a satisfied grin. Nothing like great sound effects to go with some killer slide animation. It had taken me the better part of a week, but I was done with the quarterly report. It was my first report and I was determined to make it memorable.

I hit save and sat back to wait for status bar to creep towards complete.

"You misspelled 'conclusion."

"What?" I spun around so fast I nearly spilled my coffee.

Hogarth was perched in on the window sill soaking in the late afternoon sunlight. He pointed a half-eaten fichus branch at my computer, "you misspelled 'conclusion.' Easy to do when you put spaces between each letter."

I turned back to my computer and groaned in realization. He was right. To make a better visual impact I'd put each letter in their own text box and had them spaced across the screen. I was missing the U. "Okay," I said, "thanks for the catch. Soon as this is done saving I'll fix it."

"Done saving?" Hogarth's voice showed a level of genuine confusion I wasn't used to in his voice.

I nodded. "Yeah, should be another twenty seconds."

"How big is your file?" He asked. By now it was starting to dawn on me that he was really confused and I tried not to smile at that. For once I was in the position of knowledge over him. This was great.

"About seventy slides, but the file itself is around twenty-five megabytes."

A fine spray of chewed fichus leaves showered across my back, with no small amount of spray coming over my shoulder to coat my screen. "HEY!" I yelped. Turning about in my chair I looked at Hogarth. He had somehow managed to fall off his perch and was on his hands and knees wiping plant matter from his lips. "What the heck was that for?"

Picking himself up, he recovered the, mostly-eaten branch and looked at me. "I'm sorry did you just say twenty-five megabytes?"

I nodded, "yeah, animations take up a lot of memory."

"Any seventy slides? Don't you only have twenty minutes to present?"

I nodded again, not seeing where he was going.

Hogarth did some math on his fingers. "Let's see, that's an average of 3.5 slides per minute or one slide approximately every 17 seconds."

I shrugged, "Yeah, that does seem like a lot, but the project is miserable shape and we have a lot to cover."

"And you think if you bludgeon the execs over the head with a twenty-five meg file they'll be too senseless to ask question?"

"Huh?" I replied.

Hogarth sighed. "Slides are there to make a point, not to bludgeon your audience into a stupor."


Hogarth looked heavenward with a "why me" look. Returning to look at me he said, "You do not really understand something unless you can explain it to your grandmother."

"What?" I stared at Hogarth as if he'd grown and second head. "What kind of poppycock water cooler wisdom advice is that? That's got to be from some arm chair TV shrink, right?"

"Albert Einstein" 


Sometimes it can be so very easy to make your point. And sometimes it can be so very, very hard. Unfortunately it seems that, all to often, the way we try and explain something is to throw more words at it. I'm certainly guilty of this one. Why try to explain something in ten words when one hundred will do?

Because by the time I get to thirty words, my listener is asleep, tuned out, moved on or made up their answer.

Man spent centuries practicing the art of communication. Great orators could empower a speech with nothing but their words and body language. When you think of famous speeches names like Kennedy, Caesar,  Churchill. These great speakers used their words and their gestures to communicate everything they needed to say.

Visual aids of course factored into even famous speeches and the advertising industry grew up around iconic images that conveyed an incredible amount of words, in single images. The crying Indian, the Marlboro Man, the hungry child, the oh so appetizing looking TV Dinner. But these were individual images. They were there to support the words being spoken, to anchor our minds to those words. They were not there to be the message.

Then suddenly it was as if man had forgotten the power of speech. The universe handed us  PowerPoint and we said, "this is good." We started putting everything into these mighty slide decks. Why show one table, when we could show twenty? Why memorize anything when we could put all the text on the slide. Heck, why even bother to present, just send the slides to your audience and ask for questions by email. And so came to pass the terms "eye chart" and "death by PowerPoint."

Did you know that Sweden has a political party right now who's sole platform is the desire to outlaw the use of PowerPoint in government?

PowerPoint is a visual aid. An aid, as in "to help or give assistance." Assistance, not to be the subject, but to assist the subject.

Manager Tools has a great podcast on slides for business presentations. They recommend no more than one slide for every five minutes of presentation time. Like many experts they recommend no more than five bullet points.  Don't use animation. They also stress that the slides are to support the conclusion not to present information. You don't show a graph of population data to let the viewer decipher. You show the specific result that supports your point.

These are great tips for a business slide deck and good starting guidance for a speaker deck. Speaker decks are more focused on backing up the physical speech and the rules are not as strict, you can even get away with some animations. Within reason. I recall Manager Tools describing a truly awful sales presentation. The woman had every single letter flying in, one at a time. And to make it worse, she had her computer piped into the auditorium speakers and every letter made a typewriter sound.

When I think of greater speaker decks, I really like one I saw recently by Bernie Maloney on building Rabid Rapport. It's  48 slides, which breaks the MT rules on one every 5 minutes, but the entire deck is focused on backing up the words Bernie spoke. Honestly I think the best speaker decks are the ones that make nearly no sense if you just look at the slide decks. Bernie's does a great job of that.

I'm currently working on an hour long speech for the PMI Silicon Valley annual Symposium. For a 9000 word speech, I have a slide deck with less than 550 words. Many of these are repeat words and only two pages exceed twenty-five words and only one exceeds 50 words. The animation consists entirely of replacing one image with another or with adding another, large image to an existing slide.

You can make your point with out bludgeoning your audience to death with your slides.

Joel Bancroft-Connors
The Gorilla Project Manager
Want me to talk to your gorilla? Send me an email
You can follow me on twitter, @JBC_PMP