the tw ain shall meet user experience design in agile

"The Tw ain Shall Meet: User Experience Design in Agile - PDF document

T16 Class 11/18/2010 2:45:00 PM "The Tw ain Shall Meet: User Experience Design in Agile Development" Presented by: Scott Plew es Macadamian Technologies Brought to you by: 330 Corporate Way, Suite 300, Orange Park, FL 32073 888


  1. T16 Class 11/18/2010 2:45:00 PM "The Tw ain Shall Meet: User Experience Design in Agile Development" Presented by: Scott Plew es Macadamian Technologies Brought to you by: 330 Corporate Way, Suite 300, Orange Park, FL 32073 888 ‐ 268 ‐ 8770 ∙ 904 ‐ 278 ‐ 0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com

  2. Scott Plew es Macadamian Technologies The user experience design lead at Macadamian Technologies, Scott Plewes has more than seventeen years of experience in all aspects of user experience design—defining user experience business goals, user requirements, and user interface design. Scott has worked with many of Macadamian's clients—in desktop, Web applications, and mobile device software—to successfully enhance their approaches to user experience design. Clients benefit from Scott's ability to adapt the user experience design processes to their development environment and provide pragmatic solutions in line with their business objectives.

  3. Agile UX Design: The Twain Shall Meet Scott Plewes, with Sylvain St. Germain October 2010 1

  4. Contents Introduction  Agile  UCD and UX  Agile UX  Summary 

  5. About Macadamian Product Creation Firm  Product Strategy • User Experience Design • Software Development • Quality Assurance • Offices in Canada, Europe and the US  12 Years in Business, Over 100 Personnel  VP of User Experience Design for Macadamian  17 Years in the Field of User Experience Design, 16 Years in High  Tech S/W Development

  6. Why Agile?

  7. Agile Working S/W over Documentation  People over Process  Terrain vs. the Map 

  8. Agile “Complaints” (from outside development) Focused on building instead of designing  Poor requirements or assumptions; untested  Engineers make business or user decisions 

  9. Why UCD and UX Design?

  10. UCD Business, User Driven  Highly Iterative  Design before you build 

  11. UCD Benefits Discover success and failures ahead of building  Focuses team on business and user goals  A Catalyst for creativity and innovation 

  12. UCD “Complaints” (from outside UX) Doesn’t consider needs of engineers  Slow and plodding  Not scientific, quantitative 

  13. Engineers and UX Designers Unite!

  14. Our Manifesto All Individuals over process and tools  Working experiences over functionality  Customer collaboration!  Anticipating and responding to change 

  15. Benefits of United Approach Realized Great UX Design  Creativity and Innovation  Improvement Right Up to Release  Speed and Value  Team Harmony 

  16. Ingredients for Success

  17. Value Each Other’s Roles

  18. Sprint “Zero” Two to Six Weeks  Product Strategy and Value  UX Concept Design  Technical Architecture 

  19. Ultra Fast User Feedback Flexible  Specific  Users Ready  Expert Run 

  20. Traps Sprinting in Circles  “Perfect” Experiments vs. Insight  Seclusion  Democracy and Consensus  Quantity over Value  Every Project is The Same 

  21. Summary Set a Value Based Design Direction  Course Correct Often  Minimize  Everybody Involved  Behaviours Are Transferable 

  22. Contact Information Scott Plewes VP of User Experience Macadamian Technologies scott@macadamian.com (613) 219-1040

Recommend


More recommend