Simple requirements checklist for PMs. Please feel free to recommend additions/changes, this is WIP based on my last project.
 |
Click here to mark the task as complete |
|---|---|
| 1 | Complete 1
|
Are goals of the system understood and signed off |
|
| 2 | Complete 2
|
Is functional design signed off by team and client |
|
| 3 | Complete 3
|
Has the data model been signed off |
|
| 4 | Complete 4
|
Have all data validation rules been signed off |
|
| 5 | Complete 5
|
Have all use cases been signed off |
|
| 6 | Complete 6
|
Have all support operations been defined and signed off, including responsibility matrix for exception handling |
|
| 7 | Complete 7
|
Have all systems support schedules (including integration with external systems) been signed off |
|
| 8 | Complete 8
|
Is the detail design signed off |
|
| 9 | Complete 9
|
Do the functional and detailed specifications meet all of the agreed system goals |
|
| 10 | Complete 10
|
Is all system documentation complete and version-controlled |
|
| 11 | Complete 11
|
Have the performance criteria been defined and agreed |
|
| 12 | Compliant 1
|
Does the system design meet with all of the stated compliance requirements |
|
| 13 | Compliant 2
|
Do the design, procedures and documentation comply with in-house standards |
|
| 14 | Compliant 3
|
Do the design, procedures and documentation comply with client standards |
|
| 15 | Compliant 4
|
Is all compliance documentation complete, version-contolled and filed |
|
| 16 | Functional 1
|
Have all objects been defined, including super/sub classes |
|
| 17 | Functional 2
|
Have all data elements and structures been defined |
|
| 18 | Functional 3
|
Have all entity relationships been defined |
|
| 19 | Functional 4
|
Have all data items been mapped to the appropriate objects |
|
| 20 | Functional 5
|
Do all objects specify their triggers, output and lifecycle |
|
| 21 | Functional 6
|
Have all physical outputs such as reports and files been defined |
|
| 22 | Functional 7
|
Have all points of integration with external systems been defined |
|
| 23 | Acceptance 1
|
Has a system acceptance test pack (use cases and data) been defined that also meets the volume testing criteria |
|
| 24 | Acceptance 2
|
Has a user acceptance test pack (use cases and data) been defined that also meets the volume testing criteria |
