Business case assignment
Page 2
Product Requirements Document
1. Objective
|
Description |
Describe the product in simple terms |
|
Vision |
Where you want your product to be in the future |
|
Goals |
List product goals including their timeframe, and success metric |
|
Initiatives |
List high-level product initiatives |
|
Persona(s) |
Who the product is for |
|
Environment |
Where is the product to be used |
2. Features (copy and paste table as needed for additional features)
|
Feature # |
Feature or user story name |
|
Requirement |
Description of what the new feature will do… starts with” The system shall…” |
|
Purpose |
Task or action the user wants to accomplish |
|
User problem |
Pain point or challenge |
|
User value |
How the proposed solution helps the user |
|
Assumptions |
Business, user, or technical assumptions |
|
Not doing |
Anything that is out of scope for this feature |
|
Acceptance criteria |
Conditions of acceptance; how are you going to test the feature works? |
|
Type of Requirement |
Functional or non-functional |
|
Association |
Are there any other features this feature is connected to put # (s) here |
|
Source of Requirement |
Where did the requirement originate from and if it is an initial requirement or a follow-on requirement |
|
Changes to Requirement |
List any changes to this requirement after receiving feedback -note where the feedback came from. |
|
Feature # |
Feature or user story name |
|
Requirement |
Description of what the new feature will do… starts with” The system shall…” |
|
Purpose |
Task or action the user wants to accomplish |
|
User problem |
Pain point or challenge |
|
User value |
How the proposed solution helps the user |
|
Assumptions |
Business, user, or technical assumptions |
|
Not doing |
Anything that is out of scope for this feature |
|
Acceptance criteria |
Conditions of acceptance; how are you going to test the feature works? |
|
Type of Requirement |
Functional or non-functional |
|
Association |
Are there any other features this feature is connected to put # (s) here |
|
Source of Requirement |
Where did the requirement originate from and if it is an initial requirement or a follow-on requirement |
|
Changes to Requirement |
List any changes to this requirement after receiving feedback -note where the feedback came from. |
|
Feature # |
Feature or user story name |
|
Requirement |
Description of what the new feature will do… starts with” The system shall…” |
|
Purpose |
Task or action the user wants to accomplish |
|
User problem |
Pain point or challenge |
|
User value |
How the proposed solution helps the user |
|
Assumptions |
Business, user, or technical assumptions |
|
Not doing |
Anything that is out of scope for this feature |
|
Acceptance criteria |
Conditions of acceptance; how are you going to test the feature works? |
|
Type of Requirement |
Functional or non-functional |
|
Association |
Are there any other features this feature is connected to put # (s) here |
|
Source of Requirement |
Where did the requirement originate from and if it is an initial requirement or a follow-on requirement |
|
Changes to Requirement |
List any changes to this requirement after receiving feedback -note where the feedback came from. |
|
Feature # |
Feature or user story name |
|
Requirement |
Description of what the new feature will do… starts with” The system shall…” |
|
Purpose |
Task or action the user wants to accomplish |
|
User problem |
Pain point or challenge |
|
User value |
How the proposed solution helps the user |
|
Assumptions |
Business, user, or technical assumptions |
|
Not doing |
Anything that is out of scope for this feature |
|
Acceptance criteria |
Conditions of acceptance; how are you going to test the feature works? |
|
Type of Requirement |
Functional or non-functional |
|
Association |
Are there any other features this feature is connected to put # (s) here |
|
Source of Requirement |
Where did the requirement originate from and if it is an initial requirement or a follow-on requirement |
|
Changes to Requirement |
List any changes to this requirement after receiving feedback -note where the feedback came from. |
|
Feature # |
Feature or user story name |
|
Requirement |
Description of what the new feature will do… starts with” The system shall…” |
|
Purpose |
Task or action the user wants to accomplish |
|
User problem |
Pain point or challenge |
|
User value |
How the proposed solution helps the user |
|
Assumptions |
Business, user, or technical assumptions |
|
Not doing |
Anything that is out of scope for this feature |
|
Acceptance criteria |
Conditions of acceptance; how are you going to test the feature works? |
|
Type of Requirement |
Functional or non-functional |
|
Association |
Are there any other features this feature is connected to put # (s) here |
|
Source of Requirement |
Where did the requirement originate from and if it is an initial requirement or a follow-on requirement |
|
Changes to Requirement |
List any changes to this requirement after receiving feedback -note where the feedback came from. |
|
Feature # |
Feature or user story name |
|
Requirement |
Description of what the new feature will do… starts with” The system shall…” |
|
Purpose |
Task or action the user wants to accomplish |
|
User problem |
Pain point or challenge |
|
User value |
How the proposed solution helps the user |
|
Assumptions |
Business, user, or technical assumptions |
|
Not doing |
Anything that is out of scope for this feature |
|
Acceptance criteria |
Conditions of acceptance; how are you going to test the feature works? |
|
Type of Requirement |
Functional or non-functional |
|
Association |
Are there any other features this feature is connected to put # (s) here |
|
Source of Requirement |
Where did the requirement originate from and if it is an initial requirement or a follow-on requirement |
|
Changes to Requirement |
List any changes to this requirement after receiving feedback -note where the feedback came from. |