Agile & Lean UX
13 likes3,863 views
This document discusses the history and evolution of agile UX practices. It outlines Don Norman's coining of the term "user experience architect" in 1993 and Jesse James Garrett's Elements of User Experience model in 2000 as important early developments. The document then presents six principles for realigning UX with agile, including not dictating to developers and designing all aspects of the user experience. Finally, it lists twelve emerging best practices for integrating UX work into agile development processes and recommends several books and resources on lean UX.
![“Don also described and solicited discussion
on, the "User Interface [sic] Architect's
office" (hereafter UEA).”
- Meeting notes made by Tom Erickson](https://image.slidesharecdn.com/agile-lean-ux-boeing-130817141220-phpapp02/85/Agile-Lean-UX-14-320.jpg)
Agile & Lean UX
- 1. Agile & Lean UX Boeing Agile Support Group, July 2013 Adrian Howard (@adrianh) quietstars.com
- 3. Why?
- 5. 1. Build something 2. (there is no step 2)
- 6. 1. Build something 2. Apply lipstick to pig
- 7. 1. Build something 2. Usability testing
- 8. 0. Design/Research 1. Build something
- 9. 0. Design/Research 1. Build something 2. Usability testing
- 10. Doesn't sound very agile does it?
- 11. History lesson
- 12. 1993
- 14. “Don also described and solicited discussion on, the "User Interface [sic] Architect's office" (hereafter UEA).” - Meeting notes made by Tom Erickson
- 15. “I invented the term because I thought Human Interface and usability were too narrow: I wanted to cover all aspects of the person's experience with a system, including industrial design, graphics, the interface, the physical interaction, and the manual.” - Don Norman
- 16. 2000
- 20. “The model outlined here does not account for secondary considerations (such as those arising during technical or content development) that may influence decisions during user experience development. Also, this model does not describe a development process, nor does it define roles within a user experience development team. Rather, it seeks to define the key considerations that go into the development of user experience on the Web today.” - Jesse James Garrett
- 22. How do we realign?
- 23. Six principles
- 24. 1. Missionaries not Dictators 2. Beautiful all the way down 3. Design does not stop 4. Pretty pictures must die 5. Get out of the bunker 6. Steal other people's tools
- 25. What do we do?
- 27. Twelve emerging best practices for adding UX work to Agile development
- 28. 1. Drive: UX are part of the customer or product owner team
- 29. 2. Research, model, and design up front - but only just enough
- 30. 3. Chunk your design work
- 31. 4. Use parallel track development to work ahead, and follow behind
- 32. 5. Buy design time with complex engineering stories
- 33. 6. Cultivate a group for continuous user validation
- 34. 7. Continuous user research in a separate track from development
- 35. 8. Leverage user time for multiple activities
- 36. 9. Use RITE to iterate UI before development
- 37. 10. Prototype in low fidelity
- 38. 11. Treat prototype as specification
- 39. 12. Become a design facilitator
- 40. What next?
- 41. Lean Startup
- 42. Lean Startup
- 43. Lean UX
- 44. Books • UX for Lean Startups by Laura Klein • Agile User Experience Design by Diana Brown • Lean UX by Jeff Gothelf & Josh Seiden • User-Centered Agile Methods by Hugh Beyer • Agile Experience Design by Lindsay Ratcliffe and Marc McNeill
- 45. balancedteam.org