Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Exploring design with Agile

827 views

Published on

Design is an essential key to building the right product. However research and exploration can take time. Working a sprint ahead can help UX and design teams get designs ready for development. But is that truly agile?

Key points
- Be part of product strategy
- Deliver learnings
- Flexibility in the process

Published in: Design
  • Be the first to comment

Exploring design with Agile

  1. 1. Michael Le @lifeofmle Exploring design with Agile
  2. 2. Design is iterative
  3. 3. Before After
  4. 4. Be part of product strategy Deliver learnings Flexibility in the process
  5. 5. Product Backlog Sprint Backlog Potentially Shippable Items
  6. 6. Be part of product strategy
  7. 7. – Yaseed Chaumoo, Telegraph “If you don’t have a dream you’ll be heading towards nothing”
  8. 8. Research
  9. 9. Sketches
  10. 10. Wireframes
  11. 11. #showyourwork
  12. 12. Existing Vision
  13. 13. Product roadmap
  14. 14. Product Backlog Sprint Backlog Potentially Shippable Items
  15. 15. Deliver learnings
  16. 16. TDDTest Driven Design
  17. 17. If [action] then [outcome] because [customer need/problem] Source — Maximilian Wambach, eBay Germany
  18. 18. We test hypotheses not designs
  19. 19. Hypothesis lead testing Better for density
  20. 20. Share results
  21. 21. Product Backlog Sprint Backlog Learnings
  22. 22. Flexibility in the process
  23. 23. 1 2 3 4 5 6 7 8 9 10 Test DemoDemoDemo Sprint schedule
  24. 24. Dev have the opportunity to feedback into current designs Explore & Discover Implementation & Build Design ownership from start to finish Design team can cycle through phases
  25. 25. DeliveryDiscovery
  26. 26. Design sprints with discovery
  27. 27. Scrum in delivery
  28. 28. Discovery Delivery
  29. 29. Product Design Technology
  30. 30. Product Design Technology What does the user need? What is appropriate and possible? What does the business need?
  31. 31. Scrum of scrums
  32. 32. Quarterly planning sessions
  33. 33. A healthy design process is one that can be challenged
  34. 34. Tech Debt Design Debt
  35. 35. Tech Debt Design Debt
  36. 36. TRUST
  37. 37. Budget Design Build Evaluate
  38. 38. Budget Design Build Evaluate
  39. 39. Budget Design Build Evaluate
  40. 40. Be part of product strategy Deliver learnings Flexibility in the process
  41. 41. – Henrik Kniberg, Spotify “Agile matters more than Scrum”
  42. 42. Michael Le @lifeofmle THANK YOU

×