Are Personas & Prototyping Agile?

Jurgen Appelo in the .nl has conducted a survey on agile practices. 341 people responded, solicited via Jurgen’s blog and twitter. Read more at blog posts 1, 2, & 3. Participants were asked about the agility of different software development practices as well as their importance and degree of application.

At VersionOne, we do a regular survey on agile practices, with a focus on outcomes. Jurgen’s work is interesting in that he inquired about some user-centered design practices. Here’s an excerpt from the nifty info-mixer tool.

I’ve excerpted key measures from the requirements and design sections.

The Big Agile Practices Survey (www.noop.nl) AGILE IMPORTANT
Area Practice level of agility agreement on agility agreement on importance
Requirements Use Cases 28.2% 43.6% 4.3%
Design Design by Contract 32.2% 35.7% 5.9%
Requirements Usage Scenarios 37.9% 24.2% 21.6%
Requirements Personas 47.3% 5.4% 12.0%
Design User Interface Prototyping 49.4% 1.1% 71.6%
Design Domain Driven Design 53.9% 7.9% 58.5%
Design CRC Cards 63.0% 26.1% 18.6%
Requirements Product Vision / Vision Statement 69.0% 38.0% 79.8%
Requirements Minimum Marketable Features 71.1% 42.2% 57.9%
Design System Metaphor 73.6% 47.3% 23.9%
Requirements Defer Decisions / Real Options 76.6% 53.2% 79.8%
Requirements Requirement Prioritization 82.4% 64.7% 96.5%
Design Architectural Spikes / Spike Solutions 89.0% 77.9% 82.4%
Design Emergent Design / Evolutionary Design 92.5% 85.1% 81.7%
Requirements Planning Poker 93.4% 86.8% 43.3%
Requirements Product Backlog 95.6% 91.3% 96.5%
Requirements User Stories / Executable Requirements 95.6% 91.2% 90.6%

Walking through the results, I’ll start with use cases - strongly rejected by the survey participants. In the most extensive form, these are clearly not agile but I do appreciate aspects of the use case model. Primary and secondary actions and rigorous specification of the user audience are important drivers of a good design. These are also captured in usage scenarios which gets at least a sprinkling of support. Agilists are presumably focused on revealing these aspects through iterative design and the conversation that happens while building a system as well as in product management dialogues.

I was suprised to see how contentious personas and user inteface prototyping turned out to be. The 1% and 5% agreement for these factors shows an almost even split among respondents about the agility of these practices. Personas can be challenging to do well and are buttressed upon solid user research, something often missing from agile endeavors. On the other hand, user interface prototyping is almost guaranteed to produce a better end result assuming the prototype is regarded as a starting point for dialogue rather than absolute design directive.

I’ll be talking this over with fellow UX specialists at the Usability Professional’s Association 2009 Workshop on Best Practices of UCD in Agile. We’re working to make personas productive at VersionOne, but prototyping is core technique practiced continuously to good affect.

On the other hand, I’ll never push the use case model after the response I got from the rest of the product ownership team the first time I mentioned the word at V1!

Leave a Reply