Agile UX: Embrace or Tolerate


Published on

Agile software development and User experience design are often seen at odds. The problem is that everything is designed by someone. So, it is better to discover how to incorporate UX into an Agile process rather than ignore it and leave the design up to the development team.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Agile UX: Embrace or Tolerate

  1. 1. Agile and UX:Embrace or TolerateRob Keefer, PhD@rbkeefer
  2. 2. @pomietwww.pomiet.comThe Big IdeaEverything is Designed.Be Agile.Get UX Design.
  3. 3. @pomietwww.pomiet.comThe (Longer) Big IdeaEverything is Designed -So, Embrace It or Tolerate ItGet UX DesignYou must BE agile, andInto yourProduct Development Process
  4. 4. @pomietwww.pomiet.comThe Big IdeaEverything is Designed.
  5. 5.
  6. 6.
  7. 7.
  8. 8.
  9. 9.
  10. 10.
  11. 11.
  12. 12.
  13. 13.
  14. 14.
  15. 15.
  16. 16.
  17. 17.
  18. 18. @pomietwww.pomiet.comThe Big IdeaEverything is Designed.Get UX Design.
  19. 19. @pomietwww.pomiet.comUX OverviewUnderstand UserInterviewsImmersionObservationIdentify GoalsInformation ArchitectureFlow ChartsSite MapsNavigationTaxonomyIdentify TasksPrototypeSketchesWireframesInteractive PrototypesUsability TestingUnderstand How People InteractDiscover problemsTest overall Design
  20. 20. @pomietwww.pomiet.comUnderstand User
  21. 21. @pomietwww.pomiet.comPrototype
  22. 22. @pomietwww.pomiet.comUsability Test
  23. 23. @pomietwww.pomiet.comThe Big IdeaEverything is Designed.So, who is doing your design?Are they qualified?
  24. 24. @pomietwww.pomiet.comThe Big IdeaEverything is Designed.Be Agile.Get UX Design.
  25. 25. @pomietwww.pomiet.comThe (Longer) Big IdeaEverything is Designed -So, Embrace It or Tolerate ItGet UX DesignYou must BE agile, andInto yourProduct Development Process
  26. 26.
  27. 27. @pomietwww.pomiet.comFourValues of Agile ManifestoIndividuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a planWeValue ...
  28. 28. @pomietwww.pomiet.comPrinciples of AgileOur highest priority is to satisfy the customer through early and continuous delivery of valuablesoftware.Welcome changing requirements, even late in development. Agile processes harness changefor the customers competitive advantage.Deliver working software frequently, from a couple of weeks to a couple of months, with apreference to the shorter timescale.Business people and developers must work together daily throughout the project.Build projects around motivated individuals. Give them the environment and support they need, andtrust them to get the job done.The most efficient and effective method of conveying information to and within a development team isface-to-face conversation.Working software is the primary measure of progress.Agile processes promote sustainable development. The sponsors, developers, and users should be ableto maintain a constant pace indefinitely.Continuous attention to technical excellence and good design enhances agility.Simplicity--the art of maximizing the amount of work not done--is essential.The best architectures, requirements, and designs emerge from self-organizing teams.At regular intervals, the team reflects on how to become more effective, then tunes andadjusts its behavior accordingly.
  29. 29.
  30. 30. @pomietwww.pomiet.comDoing Agile Sucks ...
  31. 31. @pomietwww.pomiet.comDoing Agile Sucks ...You Need to BE AGILE
  32. 32. @pomietwww.pomiet.comPractices can never be completelyobjectified or formalized becausethey must ever be worked out anewin particular relationships and inreal time.- Dr. Patricia Benner
  33. 33. @pomietwww.pomiet.comThe heart of Scrum is assessing thecondition of activities and empiricallydetermining what to do next.Thisdetermination arises from theexperience, training and commonsense. (p 101, 2001)The XP manager’s most sensitivebarometer of the need for change isawareness of his or her own feelings,physical and emotional. If your stomachknots when you get in the car in themorning, something is wrong with yourproject and it’s your job to effect thechange. (p 73, 2000)
  34. 34.
  35. 35. @pomietwww.pomiet.comThe Big IdeaEverything is Designed.Be Agile.Get UX Design.
  36. 36. @pomietwww.pomiet.comThe (Longer) Big IdeaEverything is Designed -So, Embrace It or Tolerate ItGet UX DesignYou must BE agile, andInto yourProduct Development Process
  37. 37. @pomietwww.pomiet.comLessons from the Trenches• Challenges of Agile UX• Tips for Making it Work•Common Questions
  38. 38. @pomietwww.pomiet.comChallenges of Agile UX• Little Up Front Design• Users are Poorly Defined•Agile is Developer Centric• Little Time to Test
  39. 39. @pomietwww.pomiet.comLittle Up Front Design• No BDUF != No DUF• Rely Heavily on Information Architecture• Establish and Use Design Patterns• Be Flexible
  40. 40. @pomietwww.pomiet.comDo-Go Map
  41. 41. @pomietwww.pomiet.comPoorly Defined Users• Developers are working for the personwho signs the check (Customer)• UX represents the person with handson the keyboard (User)• Verify as early and often as possible
  42. 42. @pomietwww.pomiet.comDeveloper-Centric• The goal of Agile methods is to discoverthe most optimal work environment.• Use reviews and retrospectives as a placeto promote a UX agenda.• Work within the process
  43. 43. @pomietwww.pomiet.comLittle Time to Test• Remember that the goal is to build high qualitysoftware - Lose the emotional ties to a design• Save longer tests for out of sprint activities• Use short tests during product design- Memorization Tests- A-B Tests
  44. 44. @pomietwww.pomiet.comTips for Making It Work• Incorporate Low-Fi prototypes into stories• Work in parallel• Refactor Mercilessly• Documentation• Turn developers into designers
  45. 45. @pomietwww.pomiet.comSupplement Stories
  46. 46. @pomietwww.pomiet.comWork in Parallel
  47. 47. @pomietwww.pomiet.comRefactor Mercilessly1 243
  48. 48. @pomietwww.pomiet.comDocumentation• Assumption Personas• Flowcharts, site-maps, Do-Go Maps• Short Style Guide - patterns, colors• Wireframes• Reduce noise through collaboration overformal documentation.• USE WHAT WORKS.
  49. 49. @pomietwww.pomiet.comDevelopers into DesignersGoal:Train developers to do the little thingsso that you can do the interesting things.Teach them toValue:• People over Features• User Feedback over Generalized Opinions• Ease of Use over Ease of Development• Discovery over Documentation
  50. 50. @pomietwww.pomiet.comCommon Questions• How do I prioritize a feature?• How can I be sure I haven’t missedanything?• What is the best way to track bugs?
  51. 51. @pomietwww.pomiet.comHow do I prioritize a feature?Use Role and Task PriorityDetermine the Feature PriorityUse details about the user role that benefits fromthe feature and the task that the feature supports.
  52. 52. @pomietwww.pomiet.comHow can I be sure I haven’tmissed something?Reconcile Roles and Goals withTasks then Consider FeaturesFor each goal associated with a role, ensure thata task exists to help the person achieve the goal.Make sure that the features support the goal.
  53. 53. @pomietwww.pomiet.comWhat’s the best way totrack bugs?Use Role & Task toDetermine Bug Criticality•Close out as many bugs as possible withthe sprint•Role up remaining bugs into newstories at the end of the month
  54. 54. @pomietwww.pomiet.comConclusionUX is needed in Agile to:Set product directionSpecify cohesive featuresKeep the inmates from running the asylum
  55. 55. @pomietwww.pomiet.comFinal Example
  56. 56. @pomietwww.pomiet.comConclusionEverything is Designed -So, Embrace It or Tolerate ItGet UX DesignYou must BE agile, andInto yourProduct Development Process
  57. 57.
  58. 58. @pomietwww.pomiet.comRob Keefer,