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.

Agile UX, Yes We Can!

6,085 views

Published on

This presentation clearly defines the difference between agile principles and practices and the role of the ux practitioner within this process.

Published in: Design
  • Great deck Alla!

    I just presented a talk on best practices for UX-agile integration a couple of weeks ago: http://slidesha.re/b5tdE7. Seems like you're advocating a similar approach based on your experience. Very cool.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Agile UX, Yes We Can!

  1. 1. Prepared by: Alla Zollers – Senior Experience Designer March 30, 2010 Agile UX, Yes We Can! boston upa
  2. 2. Part 1: The Educational Bit
  3. 3. What does it mean to “be agile”? <ul><li>Agile is not a specific method you can follow. No team practices the Agile method. There is no such thing. </li></ul><ul><li>Agile is philosophy , a set of values and principles, a mindset. </li></ul><ul><li>To “be agile”, you need to put the agile values and principles into practice . </li></ul>Source: The Art of Agile Development by Shore and Warden
  4. 4. (Very Brief) History of Agile Principles and Practices <ul><li>Inspired by Japanese industry and specifically Toyota’s Lean Thinking , agile evolved from the development community in the mid-90’s as a reaction to “heavyweight” methods. </li></ul>At the core, I believe Agile Methodologists are really about &quot;mushy” stuff, about delivering good products to customers by operating in an environment that does more than talk about ‘people as our most important asset’ but actually ‘acts’ as if people were the most important , and lose the word ‘asset’ “ ” Source: The Agile Manifesto
  5. 5. (Very Brief) History of Agile Principles and Practices <ul><li>Work at a sustainable pace </li></ul><ul><li>Self-organize </li></ul><ul><li>Work cross-functionally as a team </li></ul><ul><li>Recognize that we will never know everything upfront, and be flexible enough to adapt and change course when new information surfaces </li></ul><ul><li>Realize business value quicker by decreasing the time to market </li></ul><ul><li>Create higher quality work </li></ul><ul><li>Work in a way that makes sense for the types of products being created in today’s market </li></ul>
  6. 6. Agile Values Source: The Agile Manifesto Translation: Great products come from great teams <ul><li>Individuals and interactions over processes and tools </li></ul>Translation: Get to high-functional fidelity quickly. Provide just enough documentation to produce great work. <ul><li>Working software over comprehensive documentation </li></ul>
  7. 7. Agile Values Source: The Agile Manifesto <ul><li>Customer Collaboration over contract negotiation </li></ul>Translation: Involve end-users, decision makers, and stakeholders throughout the entire process <ul><li>Responding to change over following a plan </li></ul>Translation: Existing in a mindset that is always ready for change
  8. 8. Agile Values Although unwritten, one of the major agile values is continuous improvement , at the individual, team, and organizational levels.
  9. 9. Agile Practices <ul><li>A method , or process , is a way of working. Whenever you do something, you are following a process. </li></ul><ul><li>Agile methods are processes that support the agile philosophy . Examples include Extreme Programming (XP) and Scrum. </li></ul>Source: The Art of Agile Development by Shore and Warden
  10. 10. A Few Key Agile Practices <ul><li>Co-Location / Pairing </li></ul><ul><li>Story Creation </li></ul><ul><li>Real Customer Involvement </li></ul><ul><li>Stand-Up Meetings </li></ul><ul><li>Continuous Testing </li></ul><ul><li>Retrospectives </li></ul>
  11. 11. Agile Practice – Co-Location/ Pairing Principle: Individuals and interactions over processes and tools & continuous improvement
  12. 12. Agile Practice – Story Creation Principles: Individuals and interactions over processes and tools & Working software over comprehensive documentation
  13. 13. Agile Practice – Real Customer Involvement Principle: Customer collaboration over contract negotiation
  14. 14. Agile Practice – Stand-Up Meetings Principles: Individuals and interactions over processes and tools & Responding to change over following a plan
  15. 15. Agile Practice – Continuous Testing Principles: Working software over comprehensive documentation & Responding to change over following a plan
  16. 16. Agile Practice – Retrospectives Principle: Individuals and interactions over processes and tools & continuous improvement
  17. 17. Lifecycles Plan Analysis Design Code Test Deploy Waterfall 3- 24 months, Features 1-30 Agile Plan Analysis Design Code Test Deploy Plan Analysis Design Code Test Deploy 1 - 3 months Features 1-15 1 - 3 months Features 15-30 $ $ $ Source: The Art of Agile Development by Shore and Warden
  18. 18. Value Propositions <ul><li>Higher productivity, lower cost </li></ul><ul><li>Improved employee engagement, and job satisfaction </li></ul><ul><li>Faster time to market </li></ul><ul><li>Higher quality </li></ul><ul><li>Improved stakeholder satisfaction </li></ul><ul><li>What we have been doing no longer works </li></ul>Source: The Art of Agile Development by Shore and Warden
  19. 19. Main Value Proposition Design In Waterfall the designer/developer wall creates an “us” vs “them” mindset In Agile, everyone works as a team Development Build Design
  20. 20. Challenges with Agile <ul><li>Agile is not a silver bullet </li></ul><ul><li>Few tried and tested agile practices for UX designer </li></ul><ul><li>Unclear role of UX in process </li></ul><ul><li>Requirements gathering process is not defined </li></ul><ul><li>Setting up a successful implementation of agile practices is difficult </li></ul><ul><li>Agile practices are pervasive throughout the entire organization </li></ul><ul><li>Organization upheaval and change </li></ul><ul><li>Any transition to agile must come both from top-down and bottom-up </li></ul><ul><li>Better for refining not defining </li></ul>
  21. 21. Can We Change Our Mindset to be Agile? Yes We Can!
  22. 22. Part 2: The Practical Bit
  23. 23. Agile UX (AUX) <ul><ul><li>The question is not “how do you fit UX into Agile”, its “how do you fit Agile into UX” </li></ul></ul><ul><ul><li>There is an assumption that the standard set of UX activities and outputs should simply slot into agile development practices unchanged </li></ul></ul><ul><ul><li>Lets flip the question and ask what would a UX Design project look like if you were following Agile principals. </li></ul></ul>
  24. 24. The Role of UX <ul><li>UX practitioners are most successful in the customer role on an agile team. The customer defines the software, and determine what stakeholders find valuable. </li></ul><ul><li>The customers most important job is release planning which includes </li></ul><ul><ul><li>Evangelize product vision </li></ul></ul><ul><ul><li>Identify features and stories </li></ul></ul><ul><ul><li>Group features into small, frequent releases </li></ul></ul><ul><ul><li>Manage risk </li></ul></ul><ul><ul><li>Create an achievable plan </li></ul></ul><ul><li>Ratio: 2 customers per 3 developers </li></ul>
  25. 25. Agile UX – Beginning of Project UX Inception Workshops UX Prototype Iteration 1 UX Prototype Iteration 2 UX Prototype Iteration 3 Initial Discovery Research Customer journey sketch boards Interaction design & wireframes Context, Customer, Scenarios Interactive Prototype Development Usability Test Usability Test Usability Test Usability Test Showcase Showcase Prioritize Design analysis UX Prototype Usability Test Design analysis UX Prototype Usability Test Design analysis UX Prototype Usability Test Discovery (1-2 Weeks) Iteration 0 (2-4 Weeks) UX Prototype Stories Scoping Showcase Showcase Ongoing Discovery Research Time boxed analysis, development and user testing cycles focusing on collaboration, testing and fast feedback
  26. 26. Objection <ul><ul><li>Agile methods do not provide enough time for UX practitioners to conduct necessary research and discovery </li></ul></ul><ul><ul><li>Agile does not provide as much time upfront to conduct research and discovery, this is an ongoing activity </li></ul></ul>Answer
  27. 27. The ‘Just-Enough’ Mindset Plan Analysis Design Code Test Deploy Plan Analysis Design Code Test Deploy Release 1 Release 2 Conduct enough research to start designing for release 1, continue to research during iterations Conduct enough research to start designing for release 2, continue to research during iterations
  28. 28. Agile UX – Middle of a Project UX Dev iterating the UX design and Dev implementation tracks simultaneously Short iterative design steps and regular testing cycles, ensuring we craft UX in a collaborative manner Source: Adapting Usability Investigation for Agile User Centered Design by Sy (2007)
  29. 29. Objection <ul><ul><li>If I break up my design into pieces that can be fit into an iteration, it is difficult for me to picture the holistic system </li></ul></ul><ul><ul><li>Sketch your initial understanding of the holistic system, then begin to dive deep into the parts of the system that are prioritized </li></ul></ul>Answer
  30. 30. Think Holistically, Work Incrementally Next Iteration Entire System Wireframe or Prototype Sketches Post-It Notes or Storyboards
  31. 31. Objection <ul><ul><li>Some designs are too complex to fit within one iteration </li></ul></ul><ul><ul><li>Break large designs into small, cycle-size pieces called design chunks that incrementally add elements to the overall design over several iterations </li></ul></ul>Answer Source: Adapting Usability Investigations for Agile User Centered Design by Sy (2007)
  32. 32. Objection <ul><ul><li>There is not enough time to conduct formative usability testing and then create a usability report. </li></ul></ul><ul><ul><li>Employ light-weight usability techniques, and progressively engage in defining test protocols and recruitment. </li></ul></ul>Answer
  33. 33. Objection <ul><ul><li>Working software over comprehensive documentation means no more wireframes or mockups </li></ul></ul><ul><ul><li>Use the tools that will help you produce good work </li></ul></ul>Answer
  34. 34. Can We Adopt Our Practices to be Agile? Yes We Can!
  35. 35. Part 3: The Emotional Bit
  36. 36. Resistance to Agile <ul><li>Like the status quo </li></ul><ul><ul><li>I like who I work with </li></ul></ul><ul><ul><li>I like the power and prestige that comes with my current role </li></ul></ul><ul><ul><li>This is the way I was trained to do it and the only way I know how </li></ul></ul><ul><ul><li>I don’t like change of any sort </li></ul></ul><ul><ul><li>I don’t want to start another change initiative because they always fail anyway </li></ul></ul><ul><li>Don’t like Agile Practices </li></ul><ul><ul><li>I think agile is a fad and we’ll just have to switch back in three years </li></ul></ul><ul><ul><li>Agile is a bad idea for our products </li></ul></ul><ul><ul><li>I got into the field so that I could put on headphones on and not talk to people </li></ul></ul>
  37. 37. Can We Be Honest With Ourselves? Yes We Can!
  38. 38. Can We Be Successful with Agile? Yes We Can!
  39. 39. Can We Gain Benefits from Agile? Yes We Can!
  40. 40. Agile UX, Yes We Can! [email_address]

×