Sprint-Integrated Usability Evaluation

Description

Run a small, recorded usability test at the end of every development sprint against fixed UX goals and feed the issues straight into the next sprint backlog.

User-centred design activities are mapped onto Scrum events: personas and scenarios inform backlog items, and each sprint ends with a short usability evaluation of the increment against UX goals defined in advance, such as understanding the main goal or learning the controls. Sessions are timed and filmed, observers note where help was needed and where participants quit, and short pre-test profile and post-test questionnaires add context. Issues enter the next sprint backlog and the cycle repeats with fresh participants, so sample size can grow as the product matures; in the source case rounds escalated from one user on a bare level to 24 teenagers. The rigour comes from fixed goals carried across sprints, which make rounds comparable, rather than from any single round.

Attributes

Loss type
Active
Data
Mixed
Effort
Weeks

Steps

  1. Map UCD activities to Scrum events and agree who owns the end-of-sprint evaluation.
  2. Create personas and scenarios for target users.
  3. Define UX goals to be checked every sprint, with observable criteria such as completion without help within a time limit.
  4. At the end of each sprint run timed, recorded sessions with fresh participants, observers noting help requests and abandonment.
  5. Administer a short pre-test profile and post-test questionnaire.
  6. Write issues as backlog items for the next sprint and track goal attainment across sprints.
  7. Increase participant numbers as the increment stabilises.

Sources

  • DUXU 2017: Designing Pleasurable Experiences (Marcus & Wang, 2017)
  • Just Enough Research (Hall, 2013)

Also known as

  • Sprint-integrated usability evaluation in Scrum
  • Continuous usability evaluation
  • UCD in Scrum
  • Agile usability testing

Categories

  • User Research
  • Usability & Evaluation