Requirements Identification and Capture

Whether working with an Agile approach or a Formal approach it is essential to define the scope and expectations of the project. The requirements capture and functional specification is essential.

The requirements identification and capture process starts with at least one client meeting, generally in the format of a Requirements Capture Workshop, where initial requirements, from the primary business units involved, are collated and clarified.

Typically these requirements breakdown in five core areas:

• Identification of the key business objective and deliverables
• Information Architecture (site/application structure, navigation, etc.)
• Look and feel (design, branding etc.)
• Functional Processes (functionality contained and managed as part of the site/application)
• Integration Processes (data exchanges with other systems)

Once these initial requirements are documented we require you, the client, to review them and formally sign them off, confirming that they are the requirements of the system. This document then becomes the first of the Core Project Documents (CPD).