Tuesday, March 31, 2009

Uses cases for a new user

Hi folks.

We want to rethink the ease of use features we talked about in previous blog posts. first we need to think about the Person and use cases we want to address.

Persona:

  • Name: Suzy Rockshire
  • Age: 30
  • Occupation: Team Lead\project lead
  • Team size: 3
  • Place of work: large university computer dep.
  • Experience: Started in VB 6, moved on to .NET and C#, lots of work with classic ASP and ASP.NET. Sharepoint webparts. Standard Microsoft developer.
  • Unit testing experience: very little. mostly from hearing. thinks it’s a good idea, has no time to try it with her busy schedule. She finally foudn some time to install isolator. she has a free our. No TDD experience.

 

Possible scenarios where we can make things easier for her:

  1. After she has finished running the installer.
  2. The first time she opens visual studio after installing isolator
  3. When she decides to she wants to see what Isolator looks and feels like (visual studio already open)
  4. When she is writing a simple NUnit or MSTest unit test (no Isolator in it)
  5. When she wants to create a new test from an existing piece of code
  6. When she wants to write a sharepoint test
  7. when she first runs the test she wrote and it succeeds
  8. when the test she wrote fails
  9. when she uses Isolator’s syntax wrongly
  10. when a test using isolator has failed

which scenario would you choose first to show her the most value as quickly as possible if she has never used the product before?

are missing we missing scenarios where we could be of help?

2 comments:

  1. Between items 3 and 4 would be "When she wants to create a unit test assembly."

    ReplyDelete
  2. 11. when she uninstalls the Isolator

    You might want not to overlook this, and try to understand why users decide to drop. Give them a chance to try something else? Ask why are they leaving? Apologise? :)

    ReplyDelete

Note: Only a member of this blog may post a comment.