REPORT WITH RISK, PRIORITY, AND TEST

Budget cuts forced the company to implement only high and medium priority requirements. The company used the following method of assigning user priority:

• High - the requirement is critical for operations or performing the job
• Medium - the job can be performed without the requirement, but not very well
• Low - the requirement would be nice to have

All high risk requirements had to be thoroughly tested, and medium risk requirements would be tested as much as remaining resources allowed.

The project manager pulled a report sorted by priority from the requirements repository to help plan the effort. The report combines risk, priority, and test(s) associated with each requirement.

Although not depicted here, more than one test case is commonly associated with a requirement. Requirement text is shown to help clarity, but can be omitted from some reports.

See the link on the RM links page for more about requirement prioritization and priority schemes.