prototyping and scrum

56
Memi Beltrame @bratwurstkomet Prototyping and Scrum Agile Experience Meetup Zurich April 3rd 2013

Upload: memi-beltrame

Post on 11-May-2015

1.900 views

Category:

Design


1 download

DESCRIPTION

This presentation is about the challenges faced when doing prototypes and to make sure that these prototypes are useful for the developers. It is about how the prototyping activity fits into the iterative implementation cycles (Scrum Sprints) and how the triangle of UX, development and visual design works together, in particular if external service providers are involved.

TRANSCRIPT

Page 1: Prototyping and Scrum

Memi Beltrame@bratwurstkomet

Prototyping and ScrumAgile Experience Meetup Zurich

April 3rd 2013

Page 2: Prototyping and Scrum

Less a MessContent Strategy

I Like Magic

UX Designer for Founder of

Page 3: Prototyping and Scrum

7 Challenges

1. Know your audience2. Make it interactive3. Make it testable4. Get the right data5. Get it done6. Work on your process7. Cope with 3rd party designers

Page 4: Prototyping and Scrum

1Know your audience

Page 5: Prototyping and Scrum

Knowing your audience means

Do your research!

Page 6: Prototyping and Scrum

QuantitativeQuantitativeHow many? How often?Why and how?

Contextual InquiryObservation

Analysis

InquiryWhat people say

What people do

What people didObservation

Focus Groups

Unstructured interviews Surveys

Structured Interviews

User Diary

Userstatistics

User Research Methods

Source: Moser, Chistian „User Experience Design“. 2012, Springer Vieweg

Page 7: Prototyping and Scrum

Research helps defining the relevant criteria to base

your prototoype on

Page 8: Prototyping and Scrum

Relevant Criteria =High impact on Experience• Age. • Devices. • Location. • Homogeneity.• Education / Professional background.

Page 9: Prototyping and Scrum

Age

Page 10: Prototyping and Scrum
Page 11: Prototyping and Scrum
Page 12: Prototyping and Scrum
Page 13: Prototyping and Scrum

• Single Page• No Chrome• No adds • No wrong

places

visit http://preview.liip.ch/zooon an iPad or iPhone.

Page 14: Prototyping and Scrum

Location

Page 15: Prototyping and Scrum

Züriwald App Educational Hiking

Planning Offline =Download

Closed Places

Weather

Page 16: Prototyping and Scrum

2Make it interactive

Page 17: Prototyping and Scrum

Jungfraubahnen Tourism

Scribbles HTML-WebPrototype

Balsamiq

Page 18: Prototyping and Scrum

Speed vs. Accuracy

Pick one.

Page 19: Prototyping and Scrum

Neue Zürcher Zeitung Webpaper

Page 20: Prototyping and Scrum
Page 21: Prototyping and Scrum

3Make it testable

Page 22: Prototyping and Scrum

The more interactive, the easier to test.

Page 23: Prototyping and Scrum

Testable prototypes anticipate behavior

(as well as possible)

Page 24: Prototyping and Scrum
Page 25: Prototyping and Scrum

Fake it.

Page 26: Prototyping and Scrum

4Get the right data

Page 27: Prototyping and Scrum

Do anything to get real data.

Does it exist?How does it look like?

Page 28: Prototyping and Scrum

Prototype Data:(Fonds in an application

for bankers)

VF - European Mid and Small Cap Equity B (Lux)Aberdeen Global - Emerging Markets Equity A AccUBS (Lux) Medium Term Bond Fund - CHF P-accUBS (Lux) Medium Term Bond Fund - EUR P-accUBS (Lux) Medium Term Bond Fund - USD P-acc

Real Data:

Page 29: Prototyping and Scrum

5Get it done

Page 30: Prototyping and Scrum

Pen and Paper or

Clickables

Page 31: Prototyping and Scrum

Extremely rudimentalAffordableFast and without electricity

What you need

Page 32: Prototyping and Scrum

Extremely rudimentalAffordableFast and without electricity

What you get

Page 33: Prototyping and Scrum

Design Studio

Quantity has its own quality

Page 34: Prototyping and Scrum

Design Studio

Page 35: Prototyping and Scrum

The Power of Pen & PaperDesign Studio• Fast and cheap.• Awesome to integrate

stakeholders• Scribble with external Designers• Impressive start to signal

„We get a lot done fast“

Page 36: Prototyping and Scrum

PoP - Prototyping on Paper

http://popapp.in

Page 37: Prototyping and Scrum

Protostrap

Code: https://github.com/liip/ProtostrapDemo: http://preview.liip.ch/Protostrap/

Page 38: Prototyping and Scrum

Protostrap•Based on Boostrap• Library with CSS and Javascript Files• PHP Files to hold templates and snippets together•Documentation and examples in the package•Optimized for Mobile:

- fast tap recognistion- iOS Tabbar for Prototyping of native apps- „Add to home“

•Basic PHP knowledge needed•Not pretty, but functional!•Can get messy.

Page 39: Prototyping and Scrum

6Work on Your Process

Page 40: Prototyping and Scrum

Crossfunctional Teams

Page 41: Prototyping and Scrum

Crossfunctional Teams help with:• Avoiding silos• Spreading knowledge• Making dialogue easier• displaying unity towards the client

Page 42: Prototyping and Scrum

Preparation

Page 43: Prototyping and Scrum

Prep-versions

Each Sprint has a preceding Prep version.

Page 44: Prototyping and Scrum

A Prep version for us is just a „Fix For“ version in JIRA.

Page 45: Prototyping and Scrum

If you can‘t prep ityou can‘t do it.

Page 46: Prototyping and Scrum

One sprint ahead prep

• User stories for the coming sprint• Prototyping:

Tasks in the user stories• Not only Prototyping has to

be prepped!• No commitment in Prep:

too many unknown variables

Page 47: Prototyping and Scrum

Board = Daily

Regular Board

PrepBoard

Board = Daily

Page 48: Prototyping and Scrum

Prototype - Demo

Page 49: Prototyping and Scrum

Demoing

• Show the interaction, not the elements(Prototypes are about flow)

• Go through user stories

• Show to devs & visual designers before demoto get feedback

• Make prototype available (web & git)

• Add „How to demo“ in story if necessary

• Make screencast if necessary

Page 50: Prototyping and Scrum

When are prototypes useful for devs?• When they help devs anticipate

the scope for implementation.• Prototypes have to be complete:

- realistic data- complete interactions

Page 51: Prototyping and Scrum

7Cope with 3rd

party designers

Page 52: Prototyping and Scrum

3rd party designers

• Demand a visual designer with experience in web.

• Communicate clear expectations.• Integrate them early. Scribble with

them and let them be part.• Say no. Seriously.

Page 53: Prototyping and Scrum

Things that don‘t work

• Design Briefings• Lists of deliverables• If they have to adapt to agile just

for you. (if they are waterfall, you are waterfall too)

Page 54: Prototyping and Scrum
Page 55: Prototyping and Scrum

Questions?

Page 56: Prototyping and Scrum

Thank you!I‘m Memi Beltrame

@bratwurstkomet on twitter