Agile Humor – Agile Billboard Top 10

XP Can’t Handle Me – Flo Rida featuring David Guetta
Teenage User Stories – Katy Perry
Take It Off (Debug That Mess) – Ke$ha
Like UAT Test07 – Far’East Movement featuring Cataracts & Dev
Love the Way You Scrum – Eminem Featuring Rihanna
Cooler than Marketing – Mike Posner
Just the Way You Code – Bruno Mars
F*** You, Forget You (Waterfall Remix) – Cee Lo Green
Scrum Master Got Us Fallin’ In Love (Pair Programming Remix) – Usher Featuring Pitbull
If I Had Requirements – Adam Lambert

A Marketer’s Guide to Agile Development – 3 Lessons from Today’s Workday

Lesson: Even if you have a Dremel rotary tool hanging in the garage, sometimes that old putty knife in the drawer can still come in handy.
Today I took my department offsite to grok out a complicated analytical task. It had a lot of moving parts. After examining all the analytical and sharing tools at our disposal, SPSS, SQL, Meetingplace, Sharepoint, Wikis, KJ technique….I confidently selected the right tools for the tasks. The winner: MS Excel and a screen projector. With the addition of some comfy chairs and quality snacks, it got the job done.

Lesson: Know the difference between minutiae and details. You can probably get away with ignoring minutiae – not so much on the details.
The facility at which we held the session failed again and again to sieze opportunities to help us work efficiently. They sent us up to a room they said was open and wasn’t. Fifteen minutes lost there. The whiteboard and phone were there as promised, and the comfy chairs too. Good. Uh oh, electrical outlets 12 feet from the table, no power cords anywhere. Twenty minutes lost there improvising a new set-up. Tasty lunch, all the orders gotten right, on their seventy-five minute pacing instead of our forty-five. How many times have I seen my beloved Red Sox hit the ball well enough, but rack up enough errors to lose the game? It felt a little like that today.

Lesson: The most unlikely things can make the difference between victory and defeat. Despite the challenges, we got it done. Why? We’re professionals. We’re motivated. We genuinely like each other. We kept the process simple enough so we wouldn’t get lost in the weeds. And we had snacks. One place this facility overdelivered on was the cookies. Okay, they overdelivered them twenty minutes after we finished lunch, but they were better than… a lot of things in life. They injected the sugar rush that got us to the finish line. Who knew? Well, I did. Cookies and Excel. Sometimes it just works.

A Marketer’s Guide to Agile Development – Top Five Reasons Agile Teams Hate Marketers

In a previous column, we reviewed some reasons why some marketers give Agile the stink-eye. Let’s review why developers may be sending that stink-eye right back at ’em.

They’re annoyed – by short attention span theatre.
Marketing is all about the art of the possible. Brighter, shinier, cooler possibilities assail marketer’s brains constantly – it’s relentless. Those deep thoughts surface at inopportune times – like when their original, slightly less cool vision is in testing phase. Intellectually, they may know the enhancement should wait for the next sprint. But emotionally, this new cooler version becomes their vision of the finished project. So they become serial badgerers, imploring the PM and the developers to make “this one little change” here, “a small tweak” there. Hey marketers – a little discipline please. If you catch yourself uttering a sentence that begins with “keep it exactly the same, except….”, snap the elastic on your wrist and go back to your desk.

Sure, some marketers argue that Agile environments are supposed to welcome changing requirements. They do, in theory. The GOP welcomes healthy bipartisan debate in theory too. Theories are like that. Unlike the GOP, Agile doesn’t filibuster – it simply pushes the change to backlog. Or depending on the rank and title of the badgerer, stays late and does it, and harbors resentment.

They’re misunderstood – most marketers are clueless about sprint process.
Many marketers do actually think that if their request is not yet in production, they can still make changes, even if it’s 3 in the afternoon and the release is at 5:30. They’re not really trying to be jerks, they simply don’t know better. But they should. Responsible marketers, with the help of the project manager and/or scrum manager, learn the rhythms of the development organization that brings their ideas to life. When they do, they understand that recalcitrance isn’t the only reason behind a refusal to accept a change. But development teams take notice – once a marketer has taken the time to understand and honor your process, you’ll have to stick by your process too. No more blue smoke and mirrors.

They’re resentful – they’re the ones staying til 8:30 on Friday night.
Let’s just say it. Marketers have a reputation of not working very hard. Full disclosure, I’m in Marketing. That Dilbert cartoon with the sign that says “Marketing – 2 Drink Mininum” hangs on my wall. But trust me, most of us work our share of nights and weekends – usually individually instead of communally. Maybe because we’re not visibly toiling away night after night as a department, development teams can sometimes assume that they’re doing all the heavy lifting while Marketing lounges on divans eating bon bons while watching Oprah. That’s a myth. We only eat bon bons if the mailhouse vendor sends them at Christmas. And we only watch Oprah when we’re home sick. Some of us not even then.

They’re apprehensive – Marketing can declare all their work a failure.
A pet peeve of mine is when I’m in a meeting where someone justifies a decision with “well, I think users would want…” I just want to cut off that sentence with an air horn. Good marketers test. Good marketers declare success metrics for their initiatives, and Agile teams should abide by the same set of metrics. In my experience, when Agile teams reject Marketing’s analytics in favor of their own metrics, usually their own analytics tell them they don’t need to change their code. Objective, dispassionate measurement makes continuous improvement possible. It doesn’t matter if a developer missed his high school reunion to code the new product page, or the Angel Gabriel handed the style guide down from the sky to the CMO on an iPad. If Marketing Analytics results show that it’s decreasing rather than improving conversions, that page is going bye bye until they figure out why.

They’re jealous – Marketing gets all the cool swag.
The new branding campaign launches. Marketing gets the leather bomber jackets with the new logo on the sleeve. The developers get logo coffee mugs that can’t go in the dishwasher. Marketing celebrates the launch at Le Chateau Tres Cher. The developers stay back at the office with a Quizno’s platter to code the hot fixes. This dynamic is actually changing in some organizations. Marketing budgets aren’t what they used to be. And IT executives can order swag too.