Your SlideShare is downloading. ×
Integrating User Centered Design with Agile Development
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Integrating User Centered Design with Agile Development

4,864
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 …

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
15 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
4,864
On Slideshare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
0
Comments
1
Likes
15
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
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
  • Transcript

    • 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
      Elaboration
      Construction
      Inception
      Cost of change
      Real product
      Prototype
      Paper prototype
      Time
    • 19. Gathering requirements
    • 20. Persona and scenarios
      Personas and scenarios help to communicateusers’ needs and contextual situations. They are the outcome of thourough user research.
      • Evokeempathy
      • 21. Call out high-level goals
      • 22. Includespecific habits or pet peeves
    • Build a hi-level concept
    • 23. 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.
    • 24. The concept flow
    • 25. Sitemap
    • 26. Task flows
    • 27. Define patterns
    • 28. Design concepts
    • 29. Corporate road
    • 30. Style guide
    • 31. UX works one sprint ahead of Development
    • 32. 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
    • 33. 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
    • 34. Producewireframes
    • 35.
    • 36. Test wireframes
      By hand
      Morae software
    • 37. Specifications
      Format may vary:
      Annotated wireframes
      Clickable prototype, e.g. with Axure
      Word document
      Wiki (e.g. Confluence)
    • 38. Agile Usability testing
    • 39. usabilitytesting
      How effectively and efficiently were the users able to perform the tasks and how satisfied were they?
    • 40. Why usability testing?
      • Get feedback directly from the users – not intermediaries
      • 41. Provide data for design decisions – not opinions
      • 42. Save development time by avoiding rework later in the development process
      • 43. Increase user satisfaction and adoption
    • Agile usabilitytesting
      Tests canbeconductedwith few users
      Tests canbecarried out in an informal, low-keymanner, no specialusabilitylabisnecessary
      Results and recommendationscanbe made quickly, in a collaborative way, no lengthyoffical reports are necessary
      Tools:Morae software or simple excelspreadsheet
      Small, frequent tests are betterthan few bigones
    • 44. Usability testing during the product life cycle
    • 45. Collaborate throughout
    • 46.
    • 47. Challenges
      Internal
      Client
      • Availability of resources
      • 48. Multi-disciplinary team
      • 49. Constant pressure on the team
      • 50. Working on several sprints at the same time for the UX team
      Changing client demands
      Consistent client involvement
      Number of actors, communication, validation and escalation on the client side
      Level of maturity for UX on the client side
      Global
      • Timing pressure at each Sprint
      • 51. Budget for fixed price projects
      • 52. Constant change management
      • 53. Rigorous project management
      • 54. Clearly defined deliverables
    • thank youjulia.borkenhagen@b-i.com
      jacques.desmazieres@b-i.com