The document discusses integrating user experience (UX) design into an agile development process. It recommends doing initial user research, creating a high-level concept upfront with sitemaps, wireframes and templates. The UX team should work one sprint ahead of development to test prototypes and pass designs to developers. Frequent short usability tests are more efficient than long tests. Development and UX teams should collaborate throughout with UX involved in analysis and development sprints. Challenges include resource availability, working on multiple sprints, and client demands and involvement.

1. SoftShake 2010IntegratingUser Centered Design with Agile Development Geneva, 18.10.2010

2. The Agile ManifestoBeck et al,2001

3. This is what usability and user experience are all about.

4. What does usability mean?

5. ISO 9241 – 11: Definition of UsabilityThe extent to which a product can be used by specified users to achieve specified goals witheffectiveness, efficiencyand satisfactionin a specified context of use.

6. ISO 9241-12 Recommendations on Presentation of informationinformation should be conveyed quickly and accuratelyClarityinformation should be able to be distinguished accuratelyDiscriminabilityprovide only the information necessary to complete the taskConcisenesspresent the same information in the same way throughout the applicationConsistencydirect the user’s attention to the information requiredDetectabilityLegibilityinformation should be easy to readComprehensibilitythe meaning should be clearly understandable

7. In short:

8. …but wait, there is moreUSEREXPERIENCE

9. whatis User Experience?desirablevaluableUser experienceefficientcredibleeffectiveUsabilityusefulsatisfactoryaccessible

10. User experience is the perceived value.

11. Creating the User ExperienceAccording to ISO 9241-210, a user-centred design process is characterized by:The active involvement of usersA clear understanding of user and task requirementsAn appropriate allocation of function between users and technologyThe iteration of design solutionsMulti-disciplinary design

12. Creating the User Experience

13. Whatis a user experiencespecialist?ispassionate about makingdifficultthingseasycares about the usersunderstands design and usabilityprinciplesSeeks to innovate and delightmakes the linkbetween business and developmentunderstandspossibilities and limitations of different technologiesisexperiencedwithtesting techniquesvisualizesprocesses and interfaces

14. When…Developersdon’t care about the UI – and evenless about the users.Designers justcomplicatethings, wewouldbebetter off withoutthem.UXmeetsAgile

15. How to integrate User Experience into an Agile processThere is a need for initial user research to understand the users’ motivations, the context of use, and existing tools.Do your homework firstAn overall sitemap, hi-level wireframes, UI patterns and design templates are important to be defined up-front.Build a hi-level conceptIn order to test the paper prototypes, the UX team needs enough time to make modifications before handing over to development.UX works one sprint ahead of developmentFrequent shorter tests are more efficient and can be organised quite easily, especially for internal applications.Agile usability testingDevelopment team should be included in the initial analysis phase. UX / Design should be involved during the development sprints.Collaborate throughout

16. Do your homework first

17. Get the foundations rightWhenyoubuild a house, youget the foundationsright.The sameappliesto a web site or an application.

18. Cost of changeConceptDevelopmentAnalysisCost of changeReal productPrototypePaper prototypeTime

19. Gathering requirementsIndividual interviews and observationsWorkshops and focus groups with end users and stakeholdersWeb surveysExpert review / testing of existing solutionsAnalysis of statistics, support calls, training materialCompetitive AssessmentUser and Business requirements(including Personas and Scenarios)

20. Build a hi-level concept

21. Concept is crucialFor StrategyiTunes was an entire concept, not an afterthought of the iPod.For InnovationWe shouldn’t blindly copy what exists already.For ConsistencyAvoid impulsive and ad-hoc design decisionsFor the BrandBrand damage takes far longer to mend than it does to make.For User and Stake-holder FeedbackEven hand-drawn sketches can be used to quickly gather reactions from users and stake-holders.

22. Building a conceptBrainstorm and sketch rough concept on paperFormalize task flows and processesCreate a site structure and flowCreate hi-level wireframes and test themLogoDefine UI patterns and rulesCreate graphic concept and style guide

23. UX works one sprint ahead of Development

24. One sprint aheadHi-level ConceptResearch & AnalysisSprint 3Sprint 2Sprint 0Sprint 1Create Wireframes and Specs for Sprint 2Create Wireframes and Specs for Sprint 1Create Wireframes and Specs for Sprint 3Test Wireframes for Sprint 3Test Wireframes for Sprint 2Usability testing for Sprint 1UXTest Build from Sprint 1Test Build from Sprint 2Research for Sprint 3Research for Sprint 2Research next phaseCollaborate on Sprint 3 developmentCollaborate on Sprint 2 developmentCollaborate on Sprint 1 developmentCollaborate on application concept Develop Sprint 3Technical ArchitectureDevelop Sprint 2Develop Sprint 1Test Sprint 2Development setupFix issues from Sprint 2Test Sprint 1DevelopmentFix issues from Sprint 1Deliver, deploy Sprint 1Implement changes to Sprint 1Deliver, deploy Sprint 2Deliver, deploy Sprint 3

25. One sprint aheadHi-level ConceptResearch & AnalysisSprint 3Sprint 2Sprint 0Sprint 1Create Wireframes and Specs for Sprint 2Create Wireframes and Specs for Sprint 1Create Wireframes and Specs for Sprint 3Test Wireframes for Sprint 3Test Wireframes for Sprint 2Usability testing for Sprint 1UXTest Build from Sprint 1Test Build from Sprint 2Research for Sprint 3Research for Sprint 2Research next phaseCollaborate on Sprint 3 developmentCollaborate on Sprint 2 developmentCollaborate on Sprint 1 developmentBrief team members on Concept Develop Sprint 3Technical ArchitectureDevelop Sprint 2Develop Sprint 1DevelopmentTest Sprint 2Development setupFix issues from Sprint 2Test Sprint 1Deliver, deploy Sprint 1Fix issues from Sprint 1Implement changes to Sprint 1Deliver, deploy Sprint 2Deliver, deploy Sprint 3

26. Agile Usability testing

27. How effectively and efficiently were the users able to perform the tasks and how satisfied were they?

28. Why usability testing?Get feedback directly from the users – not intermediaries

29. Provide data for design decisions – not opinions

30. Save development time by avoiding rework later in the development process

31. Increase user satisfaction and adoptionWhatisAgileusabilitytesting?Tests canbeconductedwith few usersTests canbecarried out in an informal, low-keymanner, no specialusabilitylabisnecessaryResults and recommendationscanbe made quickly, in a collaborative way, no lengthyoffical reports are necessaryTools:Morae software or simple excelspreadsheetSmall, frequent tests are betterthan few bigones

32. Usability testing during the product life cycle

33. Collaborate throughout