10 tips on user driven development

The 10 tips are…
Explore and get user empathy:
1. If you don’t go, you wont know
2. Free work from computer
3. Visualize user experience
Prioritize and agile development
4. 10 minutes morning meeting
From functional specs to ABC culture
6. Holy Friday
Try it out and fail fast:
7. Rapid prototyping  rapid production
8. Failure is not an option – it’s necessary
Continuous learning
Trust  Google Analytics
10. Simple evaluations
Examples follow! Click next !

If you don’t go, you won't know 1 Multiple (team) eyes on the audience observes more… Quick and dirty observations over scientific research… How do they talk? How do they walk?

Free work from computer 2 Avoids “I’ll show you when finished” syndrome Facilitates early and honest feedback Communicates progression

Visualize aimed user experience
Anchor in physical objects
Ex: box, paper, moodboard, picture
Describe in one sentence
Ex: “we will create your best friend online”
Simple interpretation
Positioning schema, spider chart, video persona etc.
3

Project manager: Status please? Project member: You are annoying! Project member : Listen up... Project manager: Great, so are you! 4

From functional specs to ABC culture… A B C 5 Critical to user experience Supports user experience Nice to have = Not to have

Functional specs VS. abc culture Functional spec (B+C+A) Deadline € Prioritised functions (A+b) Deadline € Fantasy!

My calender is ABC’ed!

ABC Poker for projects Engineer: Complex! Business girl: Important Project Manager: Seach engine? B. Search engine

ABC Poker round two Engineer: Easy! Business girl: Important Project Manager: User uploads? B. Search engine A. User uploads

ABC Poker finish Lets cash in! Lets cash in! Lets cash in! B. Debat A. Comments C. Something C. Something C. Something B. Search Engine A. User uploads

ABC Poker Tour ‘09

Poker Manager

Engineers folding cards

Customers evaluating

C’s… R.I.P.

Who is ABC’ing what? Hours  Project members Days  Project members + project manager (10 min. meeting) Weeks  Project manager + Head of department (weekly meeting) The project  Project members + stakeholders + project manager (Poker) Portfoleo  Project manager + head of department + Board of directors A B C

Holy friday
From: disturbing maintenance (bugs and small features)
To: lots of small victories and love to internal customers
+ + 6 1 week = 4 days project work + Holy Friday for victories and love

Rapid prototypting  production 7

Failure is not an option…
… it is a nessesity !
Fail fast and often + quick & dirty user testing!
8

Trust is good... …Google Analytics is better Techie: Everybody is like me… Marketing dude: Everybody wants to be like me... 9

Simple evalutions
Stop: What should we stop doing?
Start: What should we start doing?
Continue: What should we continue doing?
10

So the 10 tips are…
Explore and get user empathy:
1. If you don’t go, you wont know
2. Free work from computer
3. Visualize user experience
Prioritize and agile development
4. 10 minutes morning meeting
From functional specs to ABC culture
6. Holy Friday
Try it out and fail fast:
7. Rapid prototyping  rapid production
8. Failure is not an option – it’s necessary
Continuous learning
Trust  Google Analytics
10. Simple evaluations

For more fun…
[email_address]
www.kragelund.dk
+ 45 28 14 30 12

http://kragelund.dk	617
http://www.slideshare.net	11
http://webcache.googleusercontent.com	2
http://translate.googleusercontent.com	1

10 tips on user driven development

by Anders Kragelund on Jul 10, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

4 Embeds 631

Statistics

10 tips on user driven development — Presentation Transcript