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 Manifesto Beck 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 Usability The extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiencyand satisfaction in a specified context of use.

6. ISO 9241-12 Recommendations on Presentation of information information should be conveyed quickly and accurately Clarity information should be able to be distinguished accurately Discriminability provide only the information necessary to complete the task Conciseness present the same information in the same way throughout the application Consistency direct the user’s attention to the information required Detectability Legibility information should be easy to read Comprehensibility the meaning should be clearly understandable

7. In short:

8. …but wait, there is more USEREXPERIENCE

9. whatis User Experience? desirable valuable User experience efficient credible effective Usability useful satisfactory accessible

10. User experience is the perceived value.

11. Creating the User Experience According to ISO 9241-210, a user-centred design process is characterized by: The active involvement of users A clear understanding of user and task requirements An appropriate allocation of function between users and technology The iteration of design solutions Multi-disciplinary design

12. Creating the User Experience

13. Whatis a user experiencespecialist? ispassionate about makingdifficultthingseasy cares about the users understands design and usabilityprinciples Seeks to innovate and delight makes the linkbetween business and development understandspossibilities and limitations of different technologies isexperiencedwithtesting techniques visualizesprocesses and interfaces

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

15. How to integrate User Experience into an Agile process There is a need for initial user research to understand the users’ motivations, the context of use, and existing tools. Do your homework first An overall sitemap, hi-level wireframes, UI patterns and design templates are important to be defined up-front. Build a hi-level concept In 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 development Frequent shorter tests are more efficient and can be organised quite easily, especially for internal applications. Agile usability testing Development 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 right Whenyoubuild a house, youget the foundationsright. The sameappliesto a web site or an application.

18. Cost of change Concept Development Analysis Cost of change Real product Prototype Paper prototype Time

19. Gathering requirements Individual interviews and observations Workshops and focus groups with end users and stakeholders Web surveys Expert review / testing of existing solutions Analysis of statistics, support calls, training material Competitive Assessment User and Business requirements (including Personas and Scenarios)

20. Build a hi-level concept

21. Concept is crucial For 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 decisions For 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 concept Brainstorm and sketch rough concept on paper Formalize task flows and processes Create a site structure and flow Create hi-level wireframes and test them Logo Define UI patterns and rules Create graphic concept and style guide

23. UX works one sprint ahead of Development

24. One sprint ahead Hi-level Concept Research & Analysis Sprint 3 Sprint 2 Sprint 0 Sprint 1 Create Wireframes and Specs for Sprint 2 Create Wireframes and Specs for Sprint 1 Create Wireframes and Specs for Sprint 3 Test Wireframes for Sprint 3 Test Wireframes for Sprint 2 Usability testing for Sprint 1 UX Test Build from Sprint 1 Test Build from Sprint 2 Research for Sprint 3 Research for Sprint 2 Research next phase Collaborate on Sprint 3 development Collaborate on Sprint 2 development Collaborate on Sprint 1 development Collaborate on application concept Develop Sprint 3 Technical Architecture Develop Sprint 2 Develop Sprint 1 Test Sprint 2 Development setup Fix issues from Sprint 2 Test Sprint 1 Development Fix issues from Sprint 1 Deliver, deploy Sprint 1 Implement changes to Sprint 1 Deliver, deploy Sprint 2 Deliver, deploy Sprint 3

25. One sprint ahead Hi-level Concept Research & Analysis Sprint 3 Sprint 2 Sprint 0 Sprint 1 Create Wireframes and Specs for Sprint 2 Create Wireframes and Specs for Sprint 1 Create Wireframes and Specs for Sprint 3 Test Wireframes for Sprint 3 Test Wireframes for Sprint 2 Usability testing for Sprint 1 UX Test Build from Sprint 1 Test Build from Sprint 2 Research for Sprint 3 Research for Sprint 2 Research next phase Collaborate on Sprint 3 development Collaborate on Sprint 2 development Collaborate on Sprint 1 development Brief team members on Concept Develop Sprint 3 Technical Architecture Develop Sprint 2 Develop Sprint 1 Development Test Sprint 2 Development setup Fix issues from Sprint 2 Test Sprint 1 Deliver, deploy Sprint 1 Fix issues from Sprint 1 Implement changes to Sprint 1 Deliver, deploy Sprint 2 Deliver, 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?

29. Provide data for design decisions – not opinions

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

32. Usability testing during the product life cycle

33. Collaborate throughout

36. Multi-disciplinary team

37. Constant pressure on the team

39. Budget for fixed price projects

40. Constant change management

41. Rigorous project management