Requirements Capture

The importance of capturing requirements is often overlooked, and is very often the project deliverable to suffer when budgets are tight. However, when examined closely, capturing requirements poorly will likely lead to more work having to be done at a later date, inevitably at a greater overall expense to the project.

Requirements fall under two main categories; functional and non-functional. Functional requirements relate directly to the functionality of an IT product (capabilities, particular features, etc.). Non-functional requirements on the other hand relate to things outside of a product’s functionality (performance, security, etc.).

Taking the time to gathering a clear, concise set of Business Requirements, can be invaluable to delivering a project on time to the scope that is set out at the offset. Most importantly, when requirements are captured to a high standard, they act to remove any ambiguity, potential scope creep and further confusion on the necessary deliverables, against which to conduct reviews of project success.

Aardvark Associates are well versed in Requirements Capture, and have a proven track record in such projects, successfully gathering, defining and prioritising IT Requirements, accounting for input and expertise from a wide array of sources.