HOW TO GO ABOUT IT

Work through the life cycle of the emerging project to identify key areas where requirements need to be defined. Record each area for focus in a list.

Take the Requirements Specification template and begin filling in the fields – one row per key area identified. The fields of the template are as follows:

• Number or code: This simply helps the project manager to keep track of each requirement and creates a reference to check performance against.
• Mandatory requirement: This field is where the requirement is described. Take care to fill in the requirements by stating “what” but not “how” each requirement should perform. Describing the “what” sets a measurable target for the project, whereas describing “how” (even though tempting) may limit the solution space and cut out valuable innovation opportunities.
• Comments:This field leaves room for members of the project to remind themselves of reasons for including the requirement, general questions about the technological elements of the solution, recommendations from other colleagues or similar projects, etc.
• Priority: This field helps to communicate the relative importance of various parameters of the solution.

M – MUST have this.
S – SHOULD have this if at all possible.
C – COULD have this if it does not affect anything else.

W – WON’T have this time but would like in the future

• Review date: This field helps to keep track of the date for review of each parameter.
• Reviewed/Approved:This field allows for the assigned reviewer and/or approver to sign on each requirement, which must be completed prior to starting work on that requirement.