This document discusses improving the UX design process by adopting agile principles. It recommends designers work directly with development teams during sprints to address edge cases as they emerge, rather than fully designing prototypes before development begins. This embedded approach builds trust between teams and allows designs to evolve incrementally in response to new information. The key is for all team members, including UX practitioners, to have a servant leadership mindset focused on collaboratively solving problems rather than individual agendas.

1. BACK TO THE
DRAWING BOARD
a ga in
a nd
a gainand
again

2. Luke Walter

3. Kevin Schumacher

6. UX of Yesteryear
y back in 2005)
(wa

7. 2005
.PHP
.ASP
C++
UX?

9. Point of Friction:
“ [we recommend...]
working software over comprehensive
“
documentation and responding to
change over following a plan
The Agile Manifesto

10. UX?
FINAL
PRODUCT
FINISHED DEVELOPMENT
PROTOTYPE

12. Gull-Wing Doors

13. UX practitioners would often mistake
their complete vision through their
prototype as being -
'all the developer would need'

14. Unforeseen edge
cases can kill final
development

15. What we did before:
We would design the moving car and
then panic about how to change the
tires while it was moving.

17. We want the result
to be this:

18. Scene from Tucker

19. not this:

20. Scene from Gung Ho

21. USER EXPERIENCE
-out
at won t be edged
Th
by edge cases

22. SCOPE
CREEP
Design
Details
Sprint

23. EDGE CASE
CREEP
Edge
Cases
Design

24. When to pay attention
to edge cases

25. Edge
Cases
Design

26. New design!

28. Either the world adopts
and changes to your
design
or the world rejects
your design and it fails

29. Find where your
design fails...
before the
world does.

30. we need to get over
ourselves

31. Typical Designer

32. the reality

33. You re all equally worthless!

34. Alone, you re all equally worthless!

36. Agile is not a
fad
and Design
is behind the
curve

37. UX of the future

38. TRUST

39. Getting beyond the old
Design vs. Programming
antagonism

41. Engineer Designer

42. Manager

43. Shared commitments,
Shared successes, and
perhaps most importantly,
Shared failures build trust.

44. let s examine this:
Who is the biggest
influence on your work?

45. YOU

46. We must overcome our
inflated sense of what
we know

47. BECOME A UX LEADER FIRST

48. UX leadership starts with understanding
what questions to ask in order to understand
what the problems really are

50. “ The first step in learning to
be a great teammate is to
earn your teams mutual “
respect and acceptance.
Johnny Holland

51. RESPECT = SINE QUA NON

52. The five values of Scrum:
• Courage
• Transparency
• Commitment
• Respect
• Focus

53. TEAM
CROSS-FUNCTIONALITY
INDIVIDUAL
CROSS-FUNCTIONALITY

54. T-SHAPED PERSON
subject matter subject matter
deep understanding

55. Shared swarming and
collaboration lead to
shared knowledge and
work
breadth of skill
project
work
work work

56. problem
work
project
work
work work

57. M-SHAPED PERSON
subject matter subject matter
deep understanding

58. SERVE THE VISION BY
SERVING THE TEAM

59. “
The key is to approach each interaction
with a servant s heart. When you truly
focus on contributing more than receiving
Mike Myatt you will have accomplished the goal. Even
though this may seem counter-intuitive,
by intensely focusing on the other
party s wants, needs & desires, you ll
“
learn far more than you ever would by
focusing on your agenda.

60. how?

61. JUMPING INTO THE
MOVING CAR

62. UX MOCKUPS
sprint 2 mockups sprint 3 mockups sprint 4 mockups
sprint 1 sprint 2 sprint 3
SPRINTS

63. “ One of the common patterns you ll see in
successful agile/UX combinations is having
the UX designer embedded with the rest “
of the product development team.
- Janet M. Six
UX Matters

64. UX MOCKUPS
sprint 1 sprint 2 sprint 3
SPRINTS

65. UX MOCKUPS
sprint 2 mockups sprint 3 mockups sprint 4 mockups
sprint 1 sprint 2 sprint 3
SPRINTS

66. When to Design:
Pre-Sprint or In-Sprint?
Large, Encompassing, Small, Discrete,
Amorphous (Epic) Resolved (Story)
?? ?
????
A
Phased Emergent
(AKA Pipelined, (AKA Piecemeal?)
AKA Waterfall)

67. Building great stuff is a
team effort that s hard...
and possibly dangerous!

68. Climb down from
your towers and get
into the mud with
everybody else.
It s gonna be dirty
good fun.

69. BE CAREFUL OUT THERE!
ange rous
aget d
it s gonn