Flowcon - Mixing Lean UX & Agile Development

715 views

Published on

Mixing Lean UX and Agile Development - How to minimize risk, maximize flexibility, and create a loved product. Updated and enhanced for Flowcon November 1st, 2013!

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
715
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
8
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Flowcon - Mixing Lean UX & Agile Development

  1. 1. Mixing Lean UX & Agile Development How to minimize risk, maximize flexibility, and create a loved product. Wednesday, October 2, 13
  2. 2. Courtney Hemphill @chemphill courtney@carbonfive.com Wednesday, October 2, 13
  3. 3. We used to design and build applications. Wednesday, October 2, 13
  4. 4. Now we design and build: Products Companies Experiences Services We used to design and build applications. Wednesday, October 2, 13
  5. 5. Disappearing Boundaries Wednesday, October 2, 13
  6. 6. Disappearing Boundaries brand strategy information architect experience design interaction design front-end development backend development database development data analysis system operations visual design Wednesday, October 2, 13
  7. 7. Emerging Technology Wednesday, October 2, 13
  8. 8. Emerging Technology rapid prototyping living style guides in browser design responsive design client side scripting offline apps websockets real time updates mobile html5 and canvas Wednesday, October 2, 13
  9. 9. www.evolutionoftheweb.com Wednesday, October 2, 13
  10. 10. How do you keep up with all that? Wednesday, October 2, 13
  11. 11. you don’t have to... Wednesday, October 2, 13
  12. 12. we get by with a little help from our friends... Wednesday, October 2, 13
  13. 13. Some stories about how we help our clients find their cadence. Wednesday, October 2, 13
  14. 14. A little about this we ... Wednesday, October 2, 13
  15. 15. Carbon Five Wednesday, October 2, 13
  16. 16. Roles & Responsibilities developer + designer + product owner Wednesday, October 2, 13
  17. 17. One team Everyone participates Wednesday, October 2, 13
  18. 18. Conflicting perspectives are required for creative solutions. Wednesday, October 2, 13
  19. 19. MIT Building 20 The “Magical Incubator” Wednesday, October 2, 13
  20. 20. Pixar Headquarters The legacy of Steve Jobs Wednesday, October 2, 13
  21. 21. Cadence Wednesday, October 2, 13
  22. 22. Techniques Wednesday, October 2, 13
  23. 23. Sprints as Experiments Wednesday, October 2, 13
  24. 24. What is your highest risk, highest reward feature? Wednesday, October 2, 13
  25. 25. Costs vs. Benefits Draw a cost vs. benefits hipster cross and place your epics or stories in it as a mechanism for prioritization $ !!! $$$ ! $$$ !!! $ ! Wednesday, October 2, 13
  26. 26. Get your stories straight Wednesday, October 2, 13
  27. 27. Deliverable whole Always try to prioritize using a path to a full deliverable whole. Wednesday, October 2, 13
  28. 28. Just in Time Design Wednesday, October 2, 13
  29. 29. Cards? Wednesday, October 2, 13
  30. 30. Case Studies nib.ly from Wednesday, October 2, 13
  31. 31. Week at a Glance Monday APRIL MAY week 18 Tuesday Wednesday Thursday Friday reflect & define specify build & refine build & refine customer feedback! Wednesday, October 2, 13
  32. 32. Kickoff Wednesday, October 2, 13
  33. 33. Monday Wednesday, October 2, 13
  34. 34. Retrospective Wednesday, October 2, 13
  35. 35. Capture Customer Feedback Stickies Audio Video Notes stickies.io Wednesday, October 2, 13
  36. 36. Whiteboard Wireframing Wednesday, October 2, 13
  37. 37. Hypothesis Definition Wednesday, October 2, 13
  38. 38. Clean Up and Prep Wednesday, October 2, 13
  39. 39. Tuesday Wednesday, October 2, 13
  40. 40. The Art of Story Writing Wednesday, October 2, 13
  41. 41. Title (one line describing the story)   Narrative: As a [role] I want [feature] So that [benefit]   Acceptance Criteria: (presented as Scenarios)   Scenario 1: Title Given [context]   And [some more context]... When  [event] Then  [outcome]   And [another outcome]... Story Template Wednesday, October 2, 13
  42. 42. Story Breakdown, Estimation & Prioritization Wednesday, October 2, 13
  43. 43. Pair Sketching Wednesday, October 2, 13
  44. 44. Story Mapping http://storymapper.io Wednesday, October 2, 13
  45. 45. Wednesday & Thursday Wednesday, October 2, 13
  46. 46. Feature Development Wednesday, October 2, 13
  47. 47. Whiteboard Wireframing Wednesday, October 2, 13
  48. 48. Living Style Guide & Visual Assets Wednesday, October 2, 13
  49. 49. Designer/Developer Pairing Wednesday, October 2, 13
  50. 50. Designer/Developer Pairing Wednesday, October 2, 13
  51. 51. Story Acceptance (yay!) Wednesday, October 2, 13
  52. 52. Friday Wednesday, October 2, 13
  53. 53. Customer Feedback Prep What are you testing? What methods will you use to test? Broad or specific? Wednesday, October 2, 13
  54. 54. Feedback Session Wednesday, October 2, 13
  55. 55. Five on Friday Wednesday, October 2, 13
  56. 56. Hybrid Prototyping Wednesday, October 2, 13
  57. 57. Capturing Customer Feedback Wednesday, October 2, 13
  58. 58. Discipline Wednesday, October 2, 13
  59. 59. Conflict that arises is critical to innovation. Wednesday, October 2, 13
  60. 60. Foundations Wednesday, October 2, 13
  61. 61. Foundations Conversations story writing, milestone planning, acceptance Wednesday, October 2, 13
  62. 62. Foundations Conversations story writing, milestone planning, acceptance Culture cross-functional teams, design, and dev integration Wednesday, October 2, 13
  63. 63. Foundations Conversations story writing, milestone planning, acceptance Culture cross-functional teams, design, and dev integration Cadance short term solution-focused product development Wednesday, October 2, 13
  64. 64. Wednesday, October 2, 13
  65. 65. Wednesday, October 2, 13
  66. 66. Thanks! Courtney Hemphill courtney@carbonfive.com @chemphill Wednesday, October 2, 13

×