Over the past few of months, Scrum has taunted me.
It started with two excellent Thirsty Developer Podcasts – The Thirsty Developer 14 with Ed Chaltry talking about “an Agile process” that can be used to manage and control complex software and product development using iterative, incremental practices and then The Thirsty Developer 28 with Sean McCormack talking about how Scrum and Agile principles can be applied to the enterprise. These podcasts provided such a detailed overview of Scrum that I couldn’t help but get excited.
Next, a co-worker did an excellent presentation on Scrum after successfully introducing Scrum into an organization where he was consulting. The presentation both piqued my interest and left me questioning the merits of Scrum. Actually, it had a lot of folks in my group asking questions. Maybe-not-so-coincidentally this was right around the time Martin Fowler’s Flaccid Scrum article was published.
Shortly thereafter we started using Rally Software to help manage a couple of our in-house projects and I found myself in the role of Scrum Master. The Rally tools are great. Scrum or no scrum, I’d recommend the product.
Since I was now a “Scrum Master” and under-qualified, I figured I should learn more about the role so I finished up Agile Software Development with Scrum (Series in Agile Software Development) by Ken Schwaber and Mike Beedle which I had been working on for a couple of months. I also read Head First Software Development by O’Reilly Media. Though it is an awesome resource which touches upon a number of Scrum-like processes and I recommend it to any developer (especially a junior developer on their first week on the job) it mostly through me off track as it didn’t truly define Scrum.
Which brings us to last week….last week I watched Uncle Bob Martin’s presentation at Chicago ALT.NET on XP: After 10 years why are we still talking about it? Though Uncle Bob paces in and out of camera throughout the entire one hour presentation, he’s one heck of a speaker and the presentation is a gem. He provides a really nice overview of why Scrum has hit the mainstream whereas XP certainly has not. He talks about Scrum being a subset of XP – Scrum took all the project management aspects of XP and left all the technical processes like continuous integration and TDD behind – and why this, Flaccid Scrum, ultimately fails over time. The heart of Uncle Bob’s talk is craftsmanship which is a powerful message in it’s own right but it really brought my learning of Scrum full circle.
I had my half-yearly review last week. Under the goals I listed for the next evaluation period, I included my desire to become Scrum Master certified. I’m not sure there’s much merit in this certification; however it certainly is a means to better learn the Scrum way of doing things. Perhaps surprisingly, Scrum certification was one of the easier goals for the next six months. I think I’m going to be busy. Wish me luck.