Off-The-Shelf IT Solutions - extras - Templates for stage: Requirement definition

4 Requirements analysis – capturing the organisational needs

Interview list as GDPM responsibility chart

An adaptation of GDPM’s responsibility chart (the role-responsibility matrix) that treats ‘requirements definition interviewee’ as a role column. You can analyse the matrix via spreadsheet sorting or filtering, for instance to ensure all roles are covered and all departments are represented. Supplemental columns track the allocated session (such as workshop reference) and outcome (such as DNA – Did Not Attend). For broader content with a more conventional GDPM row-column layout, see Chapter 14 downloads. See more on using the GDPM responsibility chart at book sections 4.6 and 14.4.

Download (.xlsx)

5 Requirements document – documenting and agreeing requirements

Detailed requirements document format

Depending on your sector and project management approach, this detailed format is often termed the Requirements Document, the Requirements Definition Document (RDD), the Statement of Requirements (SoR), the Statement of User Requirements (SoUR) or the Service Requirements. This template has many standard headings and some very basic entries to adapt. Note the use of styles Heading 1, 2 and 3 – these are essential to generate the Table of Contents and to give section-specific page headers. Also note the use of fields to automatically generate sequences of numbers. See usage at book section 5.4.1.

Download (.docx)

Scenario requirements format

You can use this alternative format to express requirements in a way that is more goal-orientated and usually briefer. See usage at book section 5.4.2.