Your plan should be written as though you are seeking approval/buy-in. As such, you should be providing rationale for all of your choices. For example, it is not enough to simply list your metrics; you must explain how those metrics will be used to meet your objective. Simply put, you must explain the WHY for all your choices.
For a detailed explanation of both of the above lists, see the course notes.
This is not an instance where the longest submission will get the highest grade. When seeking buy-in, it is important that your plan be clear and concise. As above, this test plan is not written strictly as documentation, but is meant to be persuasive. Write it as a professional usability document, but one that is accessible to non-technical readers.
Furthermore, write the test plan that is best for the test. Include information that is relevant to the type and scope of the test that you have chosen.
Feel free to work from the usability.gov template, or to base your work on one of the examples. Take care, though, that this fits with the test you are planning.
| Criteria | Weight |
|---|---|
| All relevant topics addressed | 30% |
| Rationale | 30% |
| Appropriate detail | 10% |
| Business logic | 10% |
| Persuasiveness | 10% |
| Use of course content | 10% |
| Late submissions will be penalized 5%/day up to a maximum of 7 days. | |
| Penalty-free extensions will not be granted for than 48 hours in advance. Extensions are not automatic, but require rationale and instructor approval. | |