Integrating User Centered Design with Agile Development

7,489 views

Published on

The Agile Manifesto emphasizes the importance of individuals and interactions over processes and tools, and that's precisely where the User Centered Design approach comes in. UCD always focuses on the users first, keeps them involved during the entire project and emphasizes the need for iterations and team collaboration.

Published in: Business, Technology
1 Comment
17 Likes
Statistics
Notes
  • Excellente présentation. Claire et concise. Induire la satisfaction d'utilisation est bien plus compliqué que satisfaire aux critères d'efficience, accessibilité et simplicité requis par l'utilisabilité.
    Constantin Sandru | État de Genève.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
7,489
On SlideShare
0
From Embeds
0
Number of Embeds
2,880
Actions
Shares
0
Downloads
0
Comments
1
Likes
17
Embeds 0
No embeds

No notes for slide
  • User research:In bigger companies, basic knowledge about user work flows, personas, and usability guidelines should live outside individual projects because it will be reused for several years across many projects.
  • JDUX specialist first create the wireframe and the concept (itshomework)Validate the resultagainst final usersThe application isbuilt by the development team. The UX specialistparticipates to the daily meeting (collaboration)Once delivered, the application id test by UX and final users (in collaboration of the UX)The UX gather changes needed in terms of UX, and addthem to the defectlist to betreated in Sprint 3
  • Integrating User Centered Design with Agile Development

    1. 1. SoftShake 2010IntegratingUser Centered Design with Agile Development Geneva, 18.10.2010<br />
    2. 2. The Agile Manifesto<br />Beck et al,2001<br />
    3. 3. This is what usability and <br />user experience are all about.<br />
    4. 4. What does usability mean?<br />
    5. 5. ISO 9241 – 11: Definition of Usability<br />The extent to which a product can be used by specified users to achieve specified goals with<br />effectiveness, efficiencyand satisfaction<br />in a specified context of use.<br />
    6. 6. ISO 9241-12 Recommendations on Presentation of information<br />information should be conveyed quickly and accurately<br />Clarity<br />information should be able to be distinguished accurately<br />Discriminability<br />provide only the information necessary to complete the task<br />Conciseness<br />present the same information in the same way throughout the application<br />Consistency<br />direct the user’s attention to the information required<br />Detectability<br />Legibility<br />information should be easy to read<br />Comprehensibility<br />the meaning should be clearly understandable<br />
    7. 7. In short:<br />
    8. 8. …but wait, there is more<br />USEREXPERIENCE<br />
    9. 9. whatis User Experience?<br />desirable<br />valuable<br />User experience<br />efficient<br />credible<br />effective<br />Usability<br />useful<br />satisfactory<br />accessible<br />
    10. 10. User experience is the perceived value.<br />
    11. 11. Creating the User Experience<br />According to ISO 9241-210, a user-centred design process is characterized by:<br />The active involvement of users<br />A clear understanding of user and task requirements<br />An appropriate allocation of function between users and technology<br />The iteration of design solutions<br />Multi-disciplinary design<br /> <br />
    12. 12. Creating the User Experience<br />
    13. 13. Whatis a user experiencespecialist?<br />ispassionate about makingdifficultthingseasy<br />cares about the users<br />understands design and usabilityprinciples<br />Seeks to innovate and delight<br />makes the linkbetween business and development<br />understandspossibilities and limitations of different technologies<br />isexperiencedwithtesting techniques<br />visualizesprocesses and interfaces<br />
    14. 14. When…<br />Developersdon’t care about the UI – and evenless about the users.<br />Designers justcomplicatethings, wewouldbebetter off withoutthem.<br />UX<br />meets<br />Agile<br />
    15. 15. How to integrate User Experience into an Agile process<br />There is a need for initial user research to understand the users’ motivations, the context of use, and existing tools.<br />Do your homework first<br />An overall sitemap, hi-level wireframes, UI patterns and design templates are important to be defined up-front.<br />Build a hi-level concept<br />In order to test the paper prototypes, the UX team needs enough time to make modifications before handing over to development.<br />UX works one sprint ahead of development<br />Frequent shorter tests are more efficient and can be organised quite easily, especially for internal applications.<br />Agile usability testing<br />Development team should be included in the initial analysis phase. UX / Design should be involved during the development sprints.<br />Collaborate throughout<br />
    16. 16. Do your homework first<br />
    17. 17. Get the foundations right<br />Whenyoubuild a house, youget the foundationsright.<br />The sameappliesto a web site or an application.<br />
    18. 18. Cost of change<br />Elaboration<br />Construction<br />Inception<br />Cost of change<br />Real product<br />Prototype<br />Paper prototype<br />Time<br />
    19. 19. Gathering requirements<br />
    20. 20. Persona and scenarios<br />Personas and scenarios help to communicateusers’ needs and contextual situations. They are the outcome of thourough user research.<br /><ul><li>Evokeempathy
    21. 21. Call out high-level goals
    22. 22. Includespecific habits or pet peeves</li></li></ul><li>Build a hi-level concept<br />
    23. 23. Concept is crucial<br />For StrategyiTunes was an entire concept, not an afterthought of the iPod.<br />For InnovationWe shouldn’t blindly copy what exists already.<br />For ConsistencyAvoid impulsive and ad-hoc design decisions<br />For the BrandBrand damage takes far longer to mend than it does to make.<br />For User and Stake-holder FeedbackEven hand-drawn sketches can be used to quickly gather reactions from users and stake-holders. <br />
    24. 24. The concept flow<br />
    25. 25. Sitemap<br />
    26. 26. Task flows<br />
    27. 27. Define patterns<br />
    28. 28. Design concepts<br />
    29. 29. Corporate road<br />
    30. 30. Style guide<br />
    31. 31. UX works one sprint ahead of Development<br />
    32. 32. One sprint ahead<br />Hi-level Concept<br />Research & Analysis<br />Sprint 3<br />Sprint 2<br />Sprint 0<br />Sprint 1<br />Create Wireframes and Specs for Sprint 2<br />Create Wireframes and Specs for Sprint 1<br />Create Wireframes and Specs for Sprint 3<br />Test Wireframes for Sprint 3<br />Test Wireframes for Sprint 2<br />Usability testing for Sprint 1<br />UX<br />Test Build from Sprint 1<br />Test Build from Sprint 2<br />Research for Sprint 3<br />Research for Sprint 2<br />Research next phase<br />Collaborate on Sprint 3 development<br />Collaborate on Sprint 2 development<br />Collaborate on Sprint 1 development<br />Collaborate on application concept <br />Develop Sprint 3<br />Technical Architecture<br />Develop Sprint 2<br />Develop Sprint 1<br />Test Sprint 2<br />Development setup<br />Fix issues from Sprint 2<br />Test Sprint 1<br />Development<br />Fix issues from Sprint 1<br />Deliver, deploy Sprint 1<br />Implement changes to Sprint 1<br />Deliver, deploy Sprint 2<br />Deliver, deploy Sprint 3<br />
    33. 33. One sprint ahead<br />Hi-level Concept<br />Research & Analysis<br />Sprint 3<br />Sprint 2<br />Sprint 0<br />Sprint 1<br />Create Wireframes and Specs for Sprint 2<br />Create Wireframes and Specs for Sprint 1<br />Create Wireframes and Specs for Sprint 3<br />Test Wireframes for Sprint 3<br />Test Wireframes for Sprint 2<br />Usability testing for Sprint 1<br />UX<br />Test Build from Sprint 1<br />Test Build from Sprint 2<br />Research for Sprint 3<br />Research for Sprint 2<br />Research next phase<br />Collaborate on Sprint 3 development<br />Collaborate on Sprint 2 development<br />Collaborate on Sprint 1 development<br />Brief team members on Concept <br />Develop Sprint 3<br />Technical Architecture<br />Develop Sprint 2<br />Develop Sprint 1<br />Development<br />Test Sprint 2<br />Development setup<br />Fix issues from Sprint 2<br />Test Sprint 1<br />Deliver, deploy Sprint 1<br />Fix issues from Sprint 1<br />Implement changes to Sprint 1<br />Deliver, deploy Sprint 2<br />Deliver, deploy Sprint 3<br />
    34. 34. Producewireframes<br />
    35. 35.
    36. 36. Test wireframes<br />By hand<br />Morae software<br />
    37. 37. Specifications<br />Format may vary:<br />Annotated wireframes<br />Clickable prototype, e.g. with Axure<br />Word document<br />Wiki (e.g. Confluence)<br />
    38. 38. Agile Usability testing<br />
    39. 39. usabilitytesting<br />How effectively and efficiently were the users able to perform the tasks and how satisfied were they?<br />
    40. 40. Why usability testing?<br /><ul><li>Get feedback directly from the users – not intermediaries
    41. 41. Provide data for design decisions – not opinions
    42. 42. Save development time by avoiding rework later in the development process
    43. 43. Increase user satisfaction and adoption</li></li></ul><li>Agile usabilitytesting<br />Tests canbeconductedwith few users<br />Tests canbecarried out in an informal, low-keymanner, no specialusabilitylabisnecessary<br />Results and recommendationscanbe made quickly, in a collaborative way, no lengthyoffical reports are necessary<br />Tools:Morae software or simple excelspreadsheet<br />Small, frequent tests are betterthan few bigones<br />
    44. 44. Usability testing during the product life cycle<br />
    45. 45. Collaborate throughout<br />
    46. 46.
    47. 47. Challenges <br />Internal<br />Client<br /><ul><li>Availability of resources
    48. 48. Multi-disciplinary team
    49. 49. Constant pressure on the team
    50. 50. Working on several sprints at the same time for the UX team</li></ul>Changing client demands<br />Consistent client involvement<br />Number of actors, communication, validation and escalation on the client side<br />Level of maturity for UX on the client side<br />Global<br /><ul><li>Timing pressure at each Sprint
    51. 51. Budget for fixed price projects
    52. 52. Constant change management
    53. 53. Rigorous project management
    54. 54. Clearly defined deliverables</li></li></ul><li>thank youjulia.borkenhagen@b-i.com<br />jacques.desmazieres@b-i.com<br />

    ×