agile-user experience design: an agile and user-centered process?

Download Agile-User Experience Design: an Agile and User-Centered Process?

Post on 28-Jan-2015

106 views

Category:

Technology

1 download

Embed Size (px)

DESCRIPTION

Agile-User Experience Design, also called Agile-UX, is a trend of the last decade that mixes values and practices from the Agile software engineering methods and the User-Centered Design. Several practitioners have proposed different processes to organize the work between development and design. After a short reminder of the values of Agile and User Centered Design methods, this paper presents five processes proposed in the literature. The processes are discussed with regards to their respect of the Agile and User Centered Design values. This comparative study concludes that not one process totally covers the Agile and User Centered Design values: they all make a trade-off and could be completed by practices and by a state of mind and a willingness adopted by the team.

TRANSCRIPT

  • 1. Agile-User Experience Design: an Agile and User-Centered Process? Lou Schwartz ICSEA 2013

2. Agenda 1. Agile vs. User Centered Design 2. Review of 5 Agile-UX processes 3. DiscussionAgile-UX: an Agile & UCD process? -- Lou Schwartz2 3. Agile-User Experience DesignValues 1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation. 3. Customer collaboration over contract negotiation. 4. Responding to change over following a plan.1. The design is based upon an explicit understanding of users, tasks and environments 2. Users are involved throughout the design and the development 3. The design is driven and refined by user-centered evaluation 4. The process is iterative 5. The design addresses the whole user experience 6. The design team includes multidisciplinary skills and perspectivesAgile ManifestoISO 9241-210 Agile-UX: an Agile & UCD process? -- Lou Schwartz3 4. Agile-User Experience DesignObjectives Enhance value of delivered product to satisfy the customers requirements Avoid delayed projects, budget overruns and stressful jobs Assure qualityBUT Neither method nor good practices to achieve this objective, particularly for the needs elicitation or the design part Focused on the developers work and on the development quality No guarantee on usability of interfacesProduce usable software to satisfy real end-users and customersBUT No guarantee on delayed projects, budget overruns and stressful jobsAgile-UX: an Agile & UCD process? -- Lou Schwartz4 5. Agile-User Experience DesignProcesses [Product owner] Product Backlog (priorized)[Team] Sprint BacklogDaily ScrumProduct (potentially delivered)Sprint 2-4 weeksSCRUM / 1 Agile methodISO 9241-210Agile-UX: an Agile & UCD process? -- Lou Schwartz5 6. Agile-User Experience Design Reconciliation of both approaches is possible And implemented It implies focusing more on design activities It results to a redefinition of the process to organize the activities dedicated to the design and the process dedicated to the development.Agile-UX: an Agile & UCD process? -- Lou Schwartz6 7. Process 1: Parallel tracks SyWell acclaimed by usability experts who test itAgile-UX: an Agile & UCD process? -- Lou Schwartz7 8. Process 2: Design work done on parallel levels Armitage R: requirement S: software P: ProductConcerns only the designers work organization 3 parallel levels, from unit to global level Provide detailed designs for the requirement developed in the current or next iteration. Redesign software developed in previous releases (a release is a set of several iterations). Provide overall product vision, to keep a global coherence throughout the project and developed software. Agile-UX: an Agile & UCD process? -- Lou Schwartz8 9. Process 3: iterative design phase + iterative development phase + Tests Deuff & al.1. Design2. Development3. Final userss test Phase 1: Iterative upfront design Phase 2: Iterative development in agile Phase 3: Big final users testAgile-UX: an Agile & UCD process? -- Lou Schwartz9 10. Process 4: Big upfront design Blomkvist Chamberlain & al. McInerney & Maurer Nodder & Nielsen Big upfront designDevelopment in agile To support product owner in User stories definition usability experts propose a big upfront analysis Supporters Blomkv Chamb Consta ist erlain ntine Project I Do first analysis and design Avoid risks Have a global visionXBrownXXX XDeuffFerreira Project Project Project 2 3 4 XXMcIner Nodder ney Proje ct PVXXX XXXAgile-UX: an Agile & UCD process? -- Lou SchwartzXX 10 11. Process 4: Big upfront design Blomkvist Chamberlain & al. McInerney & Maurer Nodder & Nielsen Big upfront designDevelopment in agileOpponents Iteration 0 is enough Armitage Avoid risks (time & money consuming) Respect Agile values: accept changes Big upfront analysis reduce qualityChamberlain Project IBrownFerreira Project 1XXXXXXXNodderXXAgile-UX: an Agile & UCD process? -- Lou Schwartz11 12. Process 5: Usage centered design ConstantineIntegration of agile and User Usage Centered design more focused on roles and on usage scenarios (task cases) than on users Roles and tasks are identified by stakeholders (domain experts, business people, designers, developers, users, etc.) thanks to brainstormingAgile-UX: an Agile & UCD process? -- Lou Schwartz12 13. N E = Not ensured Recom = recommandedDiscussion Sy3. Design driven and refined by usercentered evaluationConstantineX X X XXXXXNEXNE but recom.XXNEXNE but recom.NOXUCD principles1. Specify context 2. Specify users needs 3. Design 4. Evaluate 1. Design based on explicit understanding of users, tasks and environment 2. Users involvedBig upfront design X X X NOXUCD ActivitiesArmitageDeuffX X X XX X X XXXMore or lessNE but recom.XNENENENENEXXXNE but recom.XNENENENENENE but promotedNENENENE but promotedNENENENENEXX+/-NOX4. Iterative process 5. Process addresses the whole user experience 6. Team includes multidisciplinary skills Agile Values1. Individual and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a planAgile-UX: an Agile & UCD process? -- Lou SchwartzX X X NO13 14. Conclusion Even if the parallel tracks process is generally accepted, some other processes are proposed Brown Every team has to find its proper way to process Agile-UX because different challenges require different solutions No one studied process covers entirely all the UCD activities, UCD principles and Agile values Have to be completed by practices or by cultural aspects, e.g. Add tests Combine some processesAgile-UX: an Agile & UCD process? -- Lou Schwartz14 15. Conclusion Opened questions Which practices are necessary to complete the Agile-UX processes? What can be an Agile-UX process that respects all UCD and Agile principles? How may the people and the cultural question enhance the Agile-UX processes? How to ensure the respect of the fifth UCD principle: process addresses the whole user experience?Agile-UX: an Agile & UCD process? -- Lou Schwartz15 16. Thank you for your attention lou.schwartz@tudor.lu