Testing Plans: Mapping the WorkThursday, February 23, 12
You got to know where                    you want to go.Thursday, February 23, 12
Thursday, February 23, 12
and you got to know                       where the pitfalls are.Thursday, February 23, 12
Thursday, February 23, 12
You need to knowThursday, February 23, 12
• How                     • When                     • Where                     • Who                     • Why          ...
Worries:                            Formal?                            Casual?Thursday, February 23, 12
Prepared.Thursday, February 23, 12
Test plans also:Thursday, February 23, 12
Serve as main communication vehicleThursday, February 23, 12
Defines required                            resources.Thursday, February 23, 12
Define                            Focal points                            MilestonesThursday, February 23, 12
Parts of the Test PlanThursday, February 23, 12
Purpose, goals, and                            objectives of the testThursday, February 23, 12
Broadly.                            Major stuff.Thursday, February 23, 12
Why are you testing?                            What’s the impetus?Thursday, February 23, 12
Reasons NOT to test:Thursday, February 23, 12
Thursday, February 23, 12
• Improving user experienceThursday, February 23, 12
• Improving user experience                     • Everyone else is doing itThursday, February 23, 12
• Improving user experience                     • Everyone else is doing it                     • Space is availableThursd...
• Improving user experience                     • Everyone else is doing it                     • Space is available      ...
• Improving user experience                     • Everyone else is doing it                     • Space is available      ...
Good reasons to test:Thursday, February 23, 12
• Understanding which users can use the                            product well.                     • Compensating for ac...
Research questionsThursday, February 23, 12
Clear, succinctThursday, February 23, 12
Measurable          QuantifiableThursday, February 23, 12
Don’t do this:Thursday, February 23, 12
Thursday, February 23, 12
• Is the product usable?Thursday, February 23, 12
• Is the product usable?                     • Is the product ready for release or does it                            need...
Thursday, February 23, 12
• How easily do users understand what is                            clickable?Thursday, February 23, 12
• How easily do users understand what is                            clickable?                     • How easily do they fin...
• How easily do users understand what is                            clickable?                     • How easily do they fin...
• How easily do users understand what is                            clickable?                     • How easily do they fin...
Participant                            characteristicsThursday, February 23, 12
double-check                             with clientThursday, February 23, 12
# of participantsThursday, February 23, 12
Participant typesThursday, February 23, 12
Method (test design)Thursday, February 23, 12
Why?Thursday, February 23, 12
keeps everyone in the                   team on the same pageThursday, February 23, 12
multiple test                            moderatorsThursday, February 23, 12
focuses test                            developmentThursday, February 23, 12
protocolsThursday, February 23, 12
Task listThursday, February 23, 12
Thursday, February 23, 12
• Description of task (1 line)Thursday, February 23, 12
• Description of task (1 line)                     • Materials/Machine states requiredThursday, February 23, 12
• Description of task (1 line)                     • Materials/Machine states required                     • Successful co...
• Description of task (1 line)                     • Materials/Machine states required                     • Successful co...
Goal:             Indirectly expose usability flawsThursday, February 23, 12
Prioritize tasks:                Frequency                Criticality                Vulnerability                Readines...
Test environment,                  equipment, and logisticsThursday, February 23, 12
Test moderator roleThursday, February 23, 12
Data to be collected                            Evaluation measuresThursday, February 23, 12
Report contents and                               presentationThursday, February 23, 12
Upcoming SlideShare
Loading in...5
×

Usability Testing Plans

1,203

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

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

No notes for slide

Usability Testing Plans

  1. 1. Testing Plans: Mapping the WorkThursday, February 23, 12
  2. 2. You got to know where you want to go.Thursday, February 23, 12
  3. 3. Thursday, February 23, 12
  4. 4. and you got to know where the pitfalls are.Thursday, February 23, 12
  5. 5. Thursday, February 23, 12
  6. 6. You need to knowThursday, February 23, 12
  7. 7. • How • When • Where • Who • Why • WhatThursday, February 23, 12
  8. 8. Worries: Formal? Casual?Thursday, February 23, 12
  9. 9. Prepared.Thursday, February 23, 12
  10. 10. Test plans also:Thursday, February 23, 12
  11. 11. Serve as main communication vehicleThursday, February 23, 12
  12. 12. Defines required resources.Thursday, February 23, 12
  13. 13. Define Focal points MilestonesThursday, February 23, 12
  14. 14. Parts of the Test PlanThursday, February 23, 12
  15. 15. Purpose, goals, and objectives of the testThursday, February 23, 12
  16. 16. Broadly. Major stuff.Thursday, February 23, 12
  17. 17. Why are you testing? What’s the impetus?Thursday, February 23, 12
  18. 18. Reasons NOT to test:Thursday, February 23, 12
  19. 19. Thursday, February 23, 12
  20. 20. • Improving user experienceThursday, February 23, 12
  21. 21. • Improving user experience • Everyone else is doing itThursday, February 23, 12
  22. 22. • Improving user experience • Everyone else is doing it • Space is availableThursday, February 23, 12
  23. 23. • Improving user experience • Everyone else is doing it • Space is available • Somebody wants to do something shinyThursday, February 23, 12
  24. 24. • Improving user experience • Everyone else is doing it • Space is available • Somebody wants to do something shiny • Market testingThursday, February 23, 12
  25. 25. Good reasons to test:Thursday, February 23, 12
  26. 26. • Understanding which users can use the product well. • Compensating for acknowledged issues. • Addressing specific complaints.Thursday, February 23, 12
  27. 27. Research questionsThursday, February 23, 12
  28. 28. Clear, succinctThursday, February 23, 12
  29. 29. Measurable QuantifiableThursday, February 23, 12
  30. 30. Don’t do this:Thursday, February 23, 12
  31. 31. Thursday, February 23, 12
  32. 32. • Is the product usable?Thursday, February 23, 12
  33. 33. • Is the product usable? • Is the product ready for release or does it need more work?Thursday, February 23, 12
  34. 34. Thursday, February 23, 12
  35. 35. • How easily do users understand what is clickable?Thursday, February 23, 12
  36. 36. • How easily do users understand what is clickable? • How easily do they find X information?Thursday, February 23, 12
  37. 37. • How easily do users understand what is clickable? • How easily do they find X information? • How quickly & successfully do they register for the service?Thursday, February 23, 12
  38. 38. • How easily do users understand what is clickable? • How easily do they find X information? • How quickly & successfully do they register for the service? • Where in the site do they go to find Search?Thursday, February 23, 12
  39. 39. Participant characteristicsThursday, February 23, 12
  40. 40. double-check with clientThursday, February 23, 12
  41. 41. # of participantsThursday, February 23, 12
  42. 42. Participant typesThursday, February 23, 12
  43. 43. Method (test design)Thursday, February 23, 12
  44. 44. Why?Thursday, February 23, 12
  45. 45. keeps everyone in the team on the same pageThursday, February 23, 12
  46. 46. multiple test moderatorsThursday, February 23, 12
  47. 47. focuses test developmentThursday, February 23, 12
  48. 48. protocolsThursday, February 23, 12
  49. 49. Task listThursday, February 23, 12
  50. 50. Thursday, February 23, 12
  51. 51. • Description of task (1 line)Thursday, February 23, 12
  52. 52. • Description of task (1 line) • Materials/Machine states requiredThursday, February 23, 12
  53. 53. • Description of task (1 line) • Materials/Machine states required • Successful completion criteriaThursday, February 23, 12
  54. 54. • Description of task (1 line) • Materials/Machine states required • Successful completion criteria • Timing/BenchmarksThursday, February 23, 12
  55. 55. Goal: Indirectly expose usability flawsThursday, February 23, 12
  56. 56. Prioritize tasks: Frequency Criticality Vulnerability ReadinessThursday, February 23, 12
  57. 57. Test environment, equipment, and logisticsThursday, February 23, 12
  58. 58. Test moderator roleThursday, February 23, 12
  59. 59. Data to be collected Evaluation measuresThursday, February 23, 12
  60. 60. Report contents and presentationThursday, February 23, 12
  1. A particular slide catching your eye?

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

×