1.
SoftShake 2010IntegratingUser Centered Design with Agile Development Geneva, 18.10.2010<br />

2.
The Agile Manifesto<br />Beck et al,2001<br />

3.
This is what usability and <br />user experience are all about.<br />

4.
What does usability mean?<br />

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.
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.
In short:<br />

8.
…but wait, there is more<br />USEREXPERIENCE<br />

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.
User experience is the perceived value.<br />

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.
Creating the User Experience<br />

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.
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.
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.
Do your homework first<br />

17.
Get the foundations right<br />Whenyoubuild a house, youget the foundationsright.<br />The sameappliesto a web site or an application.<br />

18.
Cost of change<br />Concept<br />Development<br />Analysis<br />Cost of change<br />Real product<br />Prototype<br />Paper prototype<br />Time<br />

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

20.
Build a hi-level concept<br />

21.
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 />

22.
Building a concept<br />Brainstorm and sketch rough concept on paper<br />Formalize task flows and processes<br />Create a site structure and flow<br />Create hi-level wireframes and test them<br />Logo<br />Define UI patterns and rules<br />Create graphic concept and style guide<br />

23.
UX works one sprint ahead of Development<br />

24.
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 />

25.
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 />

26.
Agile Usability testing<br />

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

28.
Why usability testing?<br /><ul><li>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 adoption</li></li></ul><li>WhatisAgileusabilitytesting?<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 />

32.
Usability testing during the product life cycle<br />

33.
Collaborate throughout<br />

34.

35.
Challenges <br />Internal<br />Client<br /><ul><li>Availability of resources

36.
Multi-disciplinary team

37.
Constant pressure on the team

38.
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

39.
Budget for fixed price projects

40.
Constant change management

41.
Rigorous project management

42.
Clearly defined deliverables</li></li></ul><li>thank youjulia.borkenhagen@b-i.com<br />jacques.desmazieres@b-i.com<br />