Your SlideShare is downloading. ×
0
Outcome not Output
A story of Lean UX Adoption
Codemotion Rome, Italy – 11/04/2014
CC BY-NC-SA 3.0 - http://creativecommon...
STEFANO MARASPIN
http://www.mvlabs.it/
ENTERPRISE DEVELOPMENT
REWIND
TEXTBOOKS
PROJECT DELIVERY
CUSTOMER REACTION
Moving to Agile…
11
http://popdigital.ca/2013/01/19/the-agile-drupalist/
HAPPY CUSTOMERS
IN TIME, WITHIN BUDGET
MEETING EXPECTATIONS
REALLY?
WHOSE EXPECTATIONS?
USER STORIES
18
19
CUSTOMER
CUSTOMERUSER
22
23
TOOLS VS GOALS
USERS PERSPECTIVE
UX Design Before Development
27
http://www.flickr.com/photos/magia3e/5990317864/
Done upfront
ANALYSIS TAKES TIME
SOMETIMES TOO MUCH…
UCD OR AGILE?
THE TYRANNY
OF OR
The Zero Sprint Approach
32
http://www.flickr.com/photos/magia3e/5990317864/
Week One Week Two
BEWARE OF HAND OFFS
BEWARE OF HAND OFFS
BEWARE OF HAND OFFS
BEWARE OF HAND OFFS
BEWARE OF HAND OFFS
US VS THEM
SHARED GOAL
Welcome Agile UX
40
http://www.flickr.com/photos/magia3e/5989772879
CROSS FUNCTIONAL TEAM
T-Shaped Professionals
42
Breadth of Knowledge
TechnicalDepth
USER
NEEDS
BUSINESS
GOALS
USER
NEEDS
BUSINESS
GOALS
PROJECT
COSTS
PARALYSIS
GROUPTHINKING
ABILENE PARADOX
THE LEADER ROLE
• Leader shall be impartial (at
least at first)
• Divide group, then reunite
to air differences
• Welcome outside feedback...
SUPER HEROES
COLOCATION
ARTIFACTS
Personae
Source: MV Labs Project – Images with Creative Commons License from the web
NOT JUST ROLES
PROTO-PERSONAE
VALIDATING USER STORIES
AVOIDING WASTE
58
MEET CARLA
60
WIREFRAMES
STYLE GUIDES
UBIQUITOUS LANGUAGE
WORK EXTERNALIZED
65
66
SPECIFICATION BY EXAMPLE
• Acceptance Criteria
• Documentation
• Regression
68
100% TEST COVERAGE?
Agile practitioners
don’t adopt processes.
They adapt according
to the current context
- A. Hunt
REQUIREMENTS
OR HYPOTHESIS?
what?
how
why?
features
features
outcomes
Outcome not output
Thank you for your attention
Stefano Maraspin
@maraspin
Resources
83
Resources
84
@maraspin
Photo Credits
• http://www.flickr.com/photos/stevedave/2975730348
• http://www.flickr.com/photos/pedromourapinheiro/234833...
Stefano Maraspin
@maraspin
Outcome not Output: A Story of Lean UX Adoption
Outcome not Output: A Story of Lean UX Adoption
Outcome not Output: A Story of Lean UX Adoption
Outcome not Output: A Story of Lean UX Adoption
Outcome not Output: A Story of Lean UX Adoption
Outcome not Output: A Story of Lean UX Adoption
Upcoming SlideShare
Loading in...5
×

Outcome not Output: A Story of Lean UX Adoption

4,885

Published on

This presentation shares our experience with Lean UX adoption and offers some hints on how to combine User Centered Design activities within an Agile development workflow.

Published in: Design, Business, Technology

Transcript of "Outcome not Output: A Story of Lean UX Adoption"

  1. 1. Outcome not Output A story of Lean UX Adoption Codemotion Rome, Italy – 11/04/2014 CC BY-NC-SA 3.0 - http://creativecommons.org/licenses/by-nc-sa/3.0/
  2. 2. STEFANO MARASPIN
  3. 3. http://www.mvlabs.it/
  4. 4. ENTERPRISE DEVELOPMENT
  5. 5. REWIND
  6. 6. TEXTBOOKS
  7. 7. PROJECT DELIVERY
  8. 8. CUSTOMER REACTION
  9. 9. Moving to Agile… 11 http://popdigital.ca/2013/01/19/the-agile-drupalist/
  10. 10. HAPPY CUSTOMERS
  11. 11. IN TIME, WITHIN BUDGET
  12. 12. MEETING EXPECTATIONS
  13. 13. REALLY?
  14. 14. WHOSE EXPECTATIONS?
  15. 15. USER STORIES
  16. 16. 18
  17. 17. 19
  18. 18. CUSTOMER
  19. 19. CUSTOMERUSER
  20. 20. 22
  21. 21. 23
  22. 22. TOOLS VS GOALS
  23. 23. USERS PERSPECTIVE
  24. 24. UX Design Before Development 27 http://www.flickr.com/photos/magia3e/5990317864/ Done upfront
  25. 25. ANALYSIS TAKES TIME
  26. 26. SOMETIMES TOO MUCH…
  27. 27. UCD OR AGILE?
  28. 28. THE TYRANNY OF OR
  29. 29. The Zero Sprint Approach 32 http://www.flickr.com/photos/magia3e/5990317864/ Week One Week Two
  30. 30. BEWARE OF HAND OFFS
  31. 31. BEWARE OF HAND OFFS
  32. 32. BEWARE OF HAND OFFS
  33. 33. BEWARE OF HAND OFFS
  34. 34. BEWARE OF HAND OFFS
  35. 35. US VS THEM
  36. 36. SHARED GOAL
  37. 37. Welcome Agile UX 40 http://www.flickr.com/photos/magia3e/5989772879
  38. 38. CROSS FUNCTIONAL TEAM
  39. 39. T-Shaped Professionals 42 Breadth of Knowledge TechnicalDepth
  40. 40. USER NEEDS BUSINESS GOALS
  41. 41. USER NEEDS BUSINESS GOALS PROJECT COSTS
  42. 42. PARALYSIS
  43. 43. GROUPTHINKING
  44. 44. ABILENE PARADOX
  45. 45. THE LEADER ROLE
  46. 46. • Leader shall be impartial (at least at first) • Divide group, then reunite to air differences • Welcome outside feedback 49
  47. 47. SUPER HEROES
  48. 48. COLOCATION
  49. 49. ARTIFACTS
  50. 50. Personae Source: MV Labs Project – Images with Creative Commons License from the web
  51. 51. NOT JUST ROLES
  52. 52. PROTO-PERSONAE
  53. 53. VALIDATING USER STORIES
  54. 54. AVOIDING WASTE
  55. 55. 58
  56. 56. MEET CARLA
  57. 57. 60
  58. 58. WIREFRAMES
  59. 59. STYLE GUIDES
  60. 60. UBIQUITOUS LANGUAGE
  61. 61. WORK EXTERNALIZED
  62. 62. 65
  63. 63. 66
  64. 64. SPECIFICATION BY EXAMPLE
  65. 65. • Acceptance Criteria • Documentation • Regression 68
  66. 66. 100% TEST COVERAGE?
  67. 67. Agile practitioners don’t adopt processes. They adapt according to the current context - A. Hunt
  68. 68. REQUIREMENTS OR HYPOTHESIS?
  69. 69. what?
  70. 70. how
  71. 71. why?
  72. 72. features
  73. 73. features
  74. 74. outcomes
  75. 75. Outcome not output
  76. 76. Thank you for your attention Stefano Maraspin @maraspin
  77. 77. Resources 83
  78. 78. Resources 84
  79. 79. @maraspin
  80. 80. Photo Credits • http://www.flickr.com/photos/stevedave/2975730348 • http://www.flickr.com/photos/pedromourapinheiro/2348331422 • http://www.flickr.com/photos/wallyg/2421926775 • http://www.flickr.com/photos/seemsfinehamburg/4514890993 • http://www.flickr.com/photos/gary_dunaier/2404403331 • http://www.flickr.com/photos/gary_dunaier/2404402271 • http://www.flickr.com/photos/whartz/1404593421/ • http://www.flickr.com/photos/midatlanticbulldogrescue/2143620643 • http://www.flickr.com/photos/manicstreetpreacher/3725005364/ • http://www.flickr.com/photos/jakuza/2728096478/ • http://www.flickr.com/photos/lucasvieira/2551532145/ • http://www.flickr.com/photos/dlp/6097111286/ • http://www.flickr.com/photos/captain-k/3872566862/ • http://www.flickr.com/photos/bk1bennett/2969083199/ • http://www.flickr.com/photos/sunnyuk/3240916291/ • http://www.flickr.com/photos/practicalowl/4098547561/ • http://www.flickr.com/photos/marksinderson/6973804350 • http://www.flickr.com/photos/altgnjoey/9614493371/ • http://www.flickr.com/photos/cdevers/5770961200 • http://www.flickr.com/photos/unitopia/3179070407 • http://www.flickr.com/photos/chubbybat/1751149642 • http://www.flickr.com/photos/themichaelsmith/4399654643 • http://www.flickr.com/photos/jpartogi/4131283193 • http://www.flickr.com/photos/tomcarbone/2817253412/ • http://www.flickr.com/photos/singapore2010/4903325071/ • http://www.flickr.com/photos/mikecogh/8698837600/ • http://www.flickr.com/photos/markusthorsen/3091394736/ • http://www.flickr.com/photos/szene/4763604492/ • http://www.flickr.com/photos/jordoncooper/79555741/ 86
  81. 81. Stefano Maraspin @maraspin
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×