Beth Snapp
Team Lead, Web and Data Solutions, Ohio State University, Arts and Sciences

She wins on the longest title so far :)

Rapid Iterative Minimalist Agile!

Or, Rapid Iterative Design.

• More time writing code. Less time writing documentation.
• Manifesto for Agile Software Development: Working software over comprehensive documentation
• Just enough documentation is just perfect.
• Collaboration is Key – Creates less need to write stuff down.
• And then get to something real right away.

Personas

You probably only need 3-5  short personas.

• Composites of your users.
• They become virtual members of your team.
• Need backgrounds and motivations.
• You need to be able to feel empathy from your users.

Scenarios

• Narratives of real situations.
• What does the system need to do with the user?
• What questions arise?

User Stories

Put together Personas and Scenarios

• What not how.
• Short statements of functionality
• As a <persona> I want to <task>, so that <goal> (on sticky notes)

Paper Prototyping

More then a sketch.

• Not at all about the interface.
• It’s about building the full system (on paper)
• User must be able to simulate the tasks.
• Good demonstration:  http://www.youtube.com/watch?v=Aa-svs5mQD8

If you sit me down in front of a done system – it means that you really don’t care about my feedback.

Build the system completely, but only a few features. Then go back and add more features.

Paper prototypes ARE the documentation!