Prioritization Key: Must – Project will not be successful without this (should be 20-40% of project effort) Should – Project expects to accomplish this, but if resources and schedule are constrained to the point of not completing scope, these items will be negotiated Could – This will likely not be in this project, although if time and resources permit, this may be negotiated Will Not – This will not be considered part of this project Functionality or Behavior Priority (Must Actor have, (Sponsor, Deliverable # Use Case Name User Story Should, Partner, End Cross-Ref. Could, User, OtheR) Will Not) Availability or Reliability Requirement Deliverable # Priority Description Name Cross-Ref. Performance Requirement Deliverable # Priority Description Name Cross-Ref. Supportability Requirement Deliverable # Priority Description Name Cross-Ref. Environment Requirement Deliverable # Priority Description Name Cross-Ref.
Prioritization Key: Must – Project will not be successful without this (should be 20-40% of project effort) Should – Project expects to accomplish this, but if resources and schedule are constrained to the point of not completing scope, these items will be negotiated Could – This will likely not be in this project, although if time and resources permit, this may be negotiated Will Not – This will not be considered part of this project Functionality or Behavior # Priority (Must have, Should, Could, Will Not) Actor (Sponsor, Partner, End User, OtheR) Use Case Name User Story Deliverable Cross-Ref. Availability or Reliability # Priority Requirement Name Description Deliverable Cross-Ref. Performance # Priority Requirement Name Description Deliverable Cross-Ref. Supportability # Priority Requirement Name Description Deliverable Cross-Ref. Environment # Priority Requirement Name Description Deliverable Cross-Ref.
Product-Requirements.docx