Start with the manifesto
I recently shared my thoughts on becoming a more Agile agency over on Medium. Here at Plank, we’ve been introducing
some new practices over the past few months that are bringing us closer to that goal. We’ve switched out Basecamp for Trello, and are tweaking our processes for stand-ups and communication in general. If you’re interested in putting Agile principles
into practice, read on.
“Often you’ll hear that in order to be Agile you need to find a way to suddenly turn every designer and developer into rule-abiding ceremony-attending participants. But what happens when you’ve got four projects on the go at various stages of production,
and team members with ingrained habits and personal process preferences?
If you’re waiting for a panacea for these problems I’m sorry to say I don’t have one to provide. What I can say however, is that it’s not a bad idea to start with the original Agile manifesto. That may not be the most exciting answer (and it’s certainly
not the latest and greatest with the manifesto having just celebrated its 15th anniversary), but the best solutions are often the simplest ones. (I think it even says something to that effect in the manifesto’s principles…)
I wish I could say I came to this conclusion before trying a lot of other things and trial and error experimenting, having mastered ‘the art of maximizing the work not done,’ so-to-speak, but that’s not the case. At the agency where I work, it wasn’t
until we were on our third incarnation of stand-ups (company weekly, company daily, project-specific daily) that I realized we were effectively applying an Agile approach to implementing Agile. And sure, that sounds a bit meta/cute, but I also think
it makes complete sense. If you want to transform into a company that works around Agile principles, why would you then go and make a Waterfall plan to do so?”