Agile and Scrum

posted 04/04/08 by Rick Webb

Okay. Agile Development and Scrum. Terrifying. What the hell is that? What are you even talking about? What do those words MEAN?
This topic page will one day, hopefully, be a gateway into some serious information about the minutae and arcana of Agile and Scrum. About refining and enhancing our techniques. About sharing what we’ve learned. But for now, let’s start at the beginning.
For me, Agile and Scrum are almost a frame of mind. And they explain one of the biggest mysteries of web development that I encountered when I first started producing for the web. I’m selling them a bit short here – as we’ll learn over time, but I think the larger point is valid for someone who’s first considering Agile and Scrum from a production or marketing point of view. But perhaps a few illustrative examples are in order.
Have you ever run a project where you kept asking for things to be on the site, and your developers kept saying “no,” or your development house kept charging you for more and more work? Or have you ever had that singing feeling as you just finish “Phase 1” of your site when it seems like in the time you got one thing built on your site, your competitor made like five more improvements? Have you ever sat in a meeting with your developers and just thought “Why can’t they just make this thing awesome? Why am I paying for them to make me tell them everything to do?”
In this light, I think, Scrum and Agile are useful mental states. Scrum and Agile reset that conversation and viewpoint entirely. It’s all about working with you, showing you things, and finding out what’s most important to you at that moment. It’s a developmental methodology, but it also helps you figure out what’s most important to you, and, thus, where the developers can turn their attention to make the biggest impact on your needs.
For many first time Scrum and Agile participants, it’s a terrifying experience. “which is more important,” they ask? “All of them!” you want to say, over and over again. This website you’re viewing was, at the beginning, my first experience in Scrum, and part of the reason it took so long to deliver is because I wasn’t in the right headspace. I just kept saying “I want everything.” Which was even more impactful here, since the developers worked for me, and I wasn’t being mindful of budgetary constraints.
Flickr is always adding new features via an agile process
Flickr is always adding new features via an agile process
See? Here's another one!
See? Here’s another one!
I’ve learned over time, however, how to be a good client, thanks to the helpful staff here. I now am a stakeholder of various sorts on several Agile/Scrum projects and I love it. Circumstances change? No problem. Next sprint takes care of it. I change my mind, something’s not good enough, or one of my partners makes an offhand comment making me realize I hadn’t thought of something? All good. Agile and Scrum handles it with ease.
Where I think we need to be turning our efforts here at TBG is getting our clients into the mood for Scrum and Agile. Often the methodology is exactly what they need, but until we’ve gotten them in the right headspace, it’s kind of terrfiying. And really – how scary is it to pull the trigger on some six-figure development project where you can’t even rightly say, at the end, exactly what you’ll get. When you view it in that light it seems a little scary.
Of course, in reality, you never really know what you’re going to get anyway, and things will happen anyway. It’s a mental trick we play on ourselves, in planning, to remove those possibilities from a waterfall-style development, when evaluating different approaches. Because they will happen. That’s the old running joke, right? “The Schedule will slip. Project management is managing the slippage.”
So. Agile and Scrum. What’s what? Here’s the short hand: Scrum is the incremental, iterative process – “I do some work, we build something, look at it, evaluate it, check it, talk, and then we do some more work.” While this was indeed developed in terms of software development, it doesn’t have to be. You could scrum an oil painting I think.
Agile is the software development. It, too, is iterative. It’s Scum applied to software. There are people out there that would kill me for these simplifications, but that’s why I write introductory copy for marketing people, and they write software manuals. Agile is iterations, yes, but also other things. More talk, less writing. Each phase is a mini project: planning, requirements, design, coding, testing and documentation. I’m paraphrasing from Wikipedia here1. Such a bad habit. Professor internet, give me a demerit.

1 Agile Software Development Wikipedia Page, April 4, 2008.

Here are some recent posts from our employees about Agile and Scrum:

What I learned at camp this summer

I just finished up a long term project that floated in the fuzzy soupy place between a phased waterfall process, and a seat o’ the pants agile endeavor. The project was definitely not agile, and it was definitely not waterfall….

Hi. I'm TobyJoe.

Rick, our precious and beloved COO, has insisted that I post to the company blog.
I’m not at all opposed to that, but have a hard time finding the line between my voice and that of the company. After all, being CTO, everything I do reflects on the shop in some way (sorry, dudes!)
Things like showing up on time, going to bed by 10pm, having a baby, being married… All of this baggage really drags the reputation of this place down. I’m sure we’ve lost business due to my lack of cirrhosis or the fact that I’ve never tried a cigarette.
Hi. I’m TobyJoe, and I’m boring.
This post will serve as both an introduction (again – HELLO!) and a follow-up to my serialized biography and self-crit.

Geographical Biographical

I’m from Georgia. I totally hate Georgia. That’s why I don’t currently live in Georgia.
But, as with all rules, there’s an exception. I really like Athens. I spent many years there and still have lots of friends and contacts in that area. Aside from the time I was involved in a ~20 person line cook vs fratboy brawl and got my face smashed in by a guy in a ballcap, or the time two crackheads broke into my apartment and held my roommates and I at gunpoint (until one roommate – the son of a WWF wrestler – snatched the gun away and chased them outside), my memories of Athens are AWESOME.
I really dig college towns. Clean air, relatively smart and cultured folks, big houses, cheap everything, and almost zero stress… Ah, sweet college towns.
My wife is from State College, PA (JoePa!) and I adore the place. It’s got everything: the Amish, a bagel store, and some mountains. There’s a Quaker school for my son. There are even mobile meth labs!

Conflict of Interest

My big personal conflict here at The Barbarian Group is between my small/college town lust and my trendy almost-passion for agile development.
I’ve become quite the advocate of certain agile development methodologies over the past two years. One thing agile prefers is colocation of teams in order to foster better communication. It makes sense. That magical moment of standing over someone’s shoulder, helping them solve a bug or tweak a design makes a lot of the shitty moments (late nights, framework design flaws, Web services) more tolerable.
Here at TBG, we work in a way that only offers partial colocation. We split all projects across all of our offices as a way to ensure whole-company influence. We don’t have an “A Team” and a “B Team” and so on. We have one massive, terribly awesome team of folks who are cross-functional despite their classical titles (which some of our more stodgy clients demand). Every project here is touched or thought about or spoken of by nearly every person at some point in its life cycle.
It works really, really well. We produce amazing work. Nobody reading this can compete with us. We’re retarded good.
The only downside is that, occasionally, implementation tasks can feel a bit isolated. Chandler out in LA can’t easily ask me to take a peek at something without going through a whole SVN branch-commit-checkout process. It kinda kills some of those magic moments.
It’s a minor gripe. It’s an aesthetic gripe, at core. I like these folks, and like to collaborate in the flesh. For one, that sounds really filthy (YAY!). Also, online, I come off as a real dick. In person, I’m super cuddly and lovable. Sexy, even.
So, where’s my conflict, exactly?
The gist is this: I frequently push towards stronger colocation, despite clear proof that our current methods work very well. At the same time, I long to buy a farmhouse with a T1 and work remotely year-round.
I’m thinking I should shut up about colocation and just move to the country. At least then my boring lifestyle of child-rearing, book writing, team building, job selling, coding, cooking and going to bed early will be a novelty.
Maybe I’ll buy a huge Victorian and make it into a Barbarian Bed and Breakfast. I can fly project teams out and put them up in four-poster beds and cook them Berkshire bacon and eggs and make them work their asses off and choke on the clean air.

You know your parents are nerds when...

...they have decided to take an agile approach to child development.

A little about our site: The People

Hi, I’m Kenji. I do some front-end development around here, and I thought I’d help you get to know your new barbariangroup.com!
It’s been a relief to get this site finally out the door and in front of all you nice internet people. As Rick said (to some perhaps-deserved derision), it took over six months to bring barbariangroup.com version four (internally codenamed Merrimack) to fruition. That’s a crazy long time, sure. But we’re a small, busy shop, and couldn’t blow through this in a month. Not while continuing to pump out high-quality projects for Kashi, CNN, Adobe, TAP Project, Motorola, etc etc. We approached the barbariangroup.com version four redesign as seriously and as carefully as we would any content-rich client site, and as such, it took some time. And some people.

Crowd Surfin' the Internet

So having watched the industry grapple with the participatory, user-led, web 2.0 nature of the internet for awhile now, I have been heartened by a few positive themes that have emerged over recent years.
While many marketers want the kind of success that can be had with user-generated content and/or a successful viral campaign, they struggle with how to do that without losing control over their brand.
However, the savvy ones have decided to embrace a policy of brand transparency and experienced a moment similar to a stage dive, throwing yourself on the mercy of the mosh pit, and praying that you’ll end up crowd surfing rather than flat on your face on the floor. But now there are many stories of brands who have managed to engage their audience in a dialogue that has actually contributed to the success of the brand.
This dynamic also has marketers realizing the need for brand authenticity and to not try to be something that they’re not. Even the entertainment world, who has been quick to tap into user-generated content and social network communities, has had to be careful when creating “fake” blogs or site properties in support of a film. While there is certainly an opportunity to create an online experience of the entertainment property (or even expand the narrative, providing a deeper experience), even having the characters interact with social network communities, it has to be done in the right way. Audiences are willing to suspend their beliefs online in the same way that they do in-theater, but not if they ever feel tricked or lied to.
So all that said, it was especially great to join TBG and see that these very same principles were at the core of every discipline within the agency. From user-centered design, to a user experience strategy, to agile development methodologies—all of these involve the user in the beginning, listen to them and adapt accordingly. While it might make for a different process than a client is normally used to, it’s definitely much better than the unknown predicaments of a stage dive, and pretty much ensures that by launch you’ll be crowd surfing like the best of ‘em.

Adobe Photoshop Express

We’ve had our heads down for a while working on some SERIOUS BUSINESS, as well a new website, for a while now, but one of the projects we’ve been working on for months now made a debut on the internet today and we thought we should poke our heads up and let you know.

Today Adobe launched Photoshop Express an online, web app version of the venerable Photoshop. Except it’s cooler than that. Like it does more. Online stuff. Galleries. Hosting. Sharing. That sort of thing.

We’ve been working with Adobe on this for months now, and there’s more to come, but this marks the auspicious beginning of an extended friendship. Congratulations, Adobe, on your launch and thank you for being such a good partner.

And feel free to become a fan of this fine product on Facebook! The app is integrated with your facebook photos and can edit and stick them back in your album, which is seriously hot.