The document discusses challenges with combining agile development processes and user experience (UX) design. It notes that agile values iterative development and close collaboration over documentation, which can be difficult for traditional UX work. The document explores different strategies for integrating UX into agile projects, including conducting ongoing and targeted user research within sprints, crafting better research questions, and using personas and task analysis. It provides examples of staggered development cycles and mixing strategic and tactical UX work. The overall message is that with the right approaches, UX and agile can be successfully combined to deliver user-centered, agile projects.

1. Agile
Plus
UX?
Madness!
April
20,
2010
Regular
Joe
Consul.ng
RegularJoeConsul;ng.com
AgileCharlo2esville
agilecville.org
Joe
Sokohl
joe@regularjoeconsul.ng.com
@mojoguzzi

2. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
Agile/Scrum
iterative software engineering process
culture of close collaboration
face-to-face communication (less documentation)
deliver well-crafted, working code in short cycles
challenging environment for traditional UX

3. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
Agile Manifesto Tenets
Individuals and interactions over processes and
tools
Working software over comprehensive
documentation
Customer collaboration over contract
negotiation
Responding to change over following a plan

4. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
Manifesto: agilemanifesto.org
12 principles: agilemanifesto.org/principles.html
Global organization: agilealliance.org
Yahoo! Agile UX group: tinyurl.com/4vrwpd
Scrum: www.controlchaos.com

5. Agile Plus UX? Madness! AgileCharlottesville – April 20, 2010
“
Design
is
not
just
what
it
looks
like
and
feels
like.
Design
is
how
it
works.
”
Steve Jobs

6. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
hHp://seman;cstudios.com/publica;ons/seman;cs/000029.php

7. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
hHp://seman;cstudios.com/publica;ons/seman;cs/000029.php

8. So what’s the problem?
8

9. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
Theory
User Centered
Design
Business Process &
Agility Focus
Services-Oriented
Architectures/
Web Services
Enterprise Data Integration

10. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
Theory
Agile
Project
UXers
Coaches
PMs
Developers
Stakeholders

11. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
Practice
UXers
Agile
Project

12. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
No DBC *
* Design by committee

13. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
No DBD
*
* Design by developer

14. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
Everyone has a rice bowl--they
worry about their place in a team
hHp://www.flickr.com/photos/kalleboo/3346341189/

15. So how do we x it?
15

16. Agile Plus UX? Madness! AgileCharlottesville – April 20, 2010
• Make agile about “appropriate alacrity”
• Avoid arti ciality of time boxes
• Each iteration lives by itself
• The team makes the decision
• User stories ≠ user-centered design
• Base stories on research & real people
• Research ≠ slow, ponderous process
• Ongoing: look around for sources
• Speci c: research interactions for the current
sprint

17. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
David Farkas’ Strategy-to-Tactical
hHp://johnnyholland.org/2009/12/14/how-­‐ucd-­‐and-­‐agile-­‐can-­‐live-­‐together/

18. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
Anthony Cofelt’s Mix
hHp://www.boxesandarrows.com/view/bringing-­‐user

19. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
Desiree Sy’s Staggered Cycles
Adapting Usability Investigations for Agile User-centered Design, Desirée Sy, Journal of Usability Studies, Vol. 2, Issue 3, May 2007, pp. 112-132

20. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Guerilla Research

21. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Crafting Better Research
Questions

22. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Interviewing Research
Participants

23. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Personas

24. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Tell us about Alice...

25. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Task Analysis

26. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Sketching and Rapid Design

27. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Teaching the Design Studio
Method

28. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Presenting Sketches

29. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Design Review

30. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Critiquing the Design

31. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Critiquing the Design

32. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Paired Programming

33. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Paired Programming

34. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
From Prototype to Production

35. Agile
User
Experience:
Two
Tales
and
a
Conversa;on
RUX
+
AgileRichmond
–
January
10,
2010
Collaborative Work

36. Agile Plus UX? Madness! AgileCharlottesville – April 20, 2010
What makes Agile agile
• Real user information
• Don’t guess, don’t postulate: observe
• Realistic timelines
• No “iteration -1” or “iteration 0”
• Design provides business value
• Optimal ration: 2-3
• Focus on competencies, not roles or tools
• UX people do user requirements, because UX people
focus on users
• Listening and assigning responsibilites work best
while avoiding dogma
• Don’t covet tools; value thought

37. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
Agile
Manifesto User-­‐experience
Design
Research-based
Individuals & interactions
requirements
Working software Prototypes & IxD
Customer collaboration Knowing your users
Usability testing to inform
Responding to change
design

38. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
Communities of practice
Agile Experience Design: www.agileexperiencedesign.org/
Boxes and Arrows: boxesandarrows.com
UX Matters: uxmatters.com
Usability Professionals Association: upassoc.org
Information Architecture Institute: iainstitute.org
Interaction Design Association: ixda.org
Johnny Holland: johnnyholland.org
Konigi: konigi.com
People
Don Norman: www.jnd.org
Anders Ramsay: andersramsay.com
Jared Spool: www.uie.com
Luke Wroblewski: functioningform.com
Lou Rosenfeld: louisrosenfeld.com

39. Agile
Plus
UX?
Madness!
AgileCharlo2esville
–
April
20,
2010
What’s
your
story?