User experience & agile

1,026
-1

Published on

A proposed approach for integrating UX activities into a scrum program.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,026
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

User experience & agile

  1. 1. User Experience & Agile A proposed approach
  2. 2. <ul><li>Ongoing user testing </li></ul><ul><li>Portfolio-wide field research </li></ul><ul><li>User needs </li></ul><ul><li>Product-based field research </li></ul><ul><li>Personas </li></ul><ul><li>Scenarios/stories </li></ul><ul><li>User testing </li></ul>Program Product Project
  3. 3. Challenges <ul><li>Agile methodologies demand speed, in design as well as development </li></ul><ul><li>UX tasks must not interrupt the workflow, but we still need quality products </li></ul><ul><li>Agile does not inherently make space for user research or user testing </li></ul>
  4. 4. Solutions <ul><li>Run large user research and testing pieces in parallel to Agile project </li></ul><ul><li>Test components during project lifecycle </li></ul><ul><li>Implement ongoing user testing across all products, rather than project-based testing only </li></ul><ul><li>Utilise Sprint Zero to incorporate user research into project planning </li></ul>
  5. 5. Resource & Business Implications <ul><li>Requires usability resources to be available outside the Scrum/Agile team </li></ul><ul><li>Requires business owners to take users into account from beginning of product conceptualisation </li></ul>
  6. 6. User Research <ul><li>Conduct user research (eg, field research, focus groups) when business case is being developed </li></ul><ul><li>Develop personas based on this research before project begins </li></ul><ul><li>Use this research to feed into Sprint Zero of project </li></ul>
  7. 7. Sprint Zero <ul><li>Write stories based on personas </li></ul><ul><li>Minimal design up-front, but not no design </li></ul><ul><li>Information architecture must be designed up-front, and may need to be tested using paper prototypes, depending on project </li></ul><ul><li>Interaction design required up-front (eg, basic templates, understanding of behaviour) </li></ul>
  8. 8. Sprints <ul><li>Testing and design tasks to be done one sprint ahead of development </li></ul><ul><li>Testing of small pieces of design/functionality as tasks are completed. Feed results back into the project so usability improvements can be made quickly. </li></ul><ul><li>Testing of completed designs, where possible. </li></ul>
  9. 9. Post-build <ul><li>During UAT, or after launch, complete task-based testing of completed build. </li></ul><ul><li>Agreement with team on how usability issues will be handled (eg, are usability issues bugs? How are they prioritised?) </li></ul>
  10. 10. Post-launch <ul><li>Regular testing of live site and continuous improvement </li></ul><ul><li>Field studies where appropriate </li></ul><ul><li>Data from testing to inform next project, or next stage of the project if it is ongoing </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×