A Meeting of the Worlds
When I came aboard as the designer at Rabid, I was thrown straight into an Agile development workflow without much warning. I was a bit overwhelmed, as one generally is at a new job, but it was exacerbated by the fact that:
I didn’t know Agile. At all.
Agile and design != instant success.
As a designer I was massively outnumbered by developers.
Eek! Not to worry, I’ve gotten to a good place with all three of these things and I’m happy to share my findings.
My context is interesting because Rabid is a fairly unique group, in the sense that their developers are all very open to design input and generally welcome good design as a help rather than a hindrance. This made the transition to working across multiple projects in an Agile fashion much easier. However, as I’ve been going along, I’ve run into some interesting general gaps between what Agile supports and where design happens.
I also held a group discussion with @kellective and @amandadorrell at the Gather conference in Auckland a few months back, with a room full of designers and developers. We got a pretty resounding consensus about where tension points lie and also where people have found benefits: