April 24, 2020
By Lee Bourke
Requirements for a project need to be mined, compiled, analysed, negotiated, specified, validated, tracked, and updated during the life of a project. All of this has to take place within a controlled environment so that;
The method of requirements delivery will vary from project to project normally based on project complexity. As well as complexity the level or type of requirements management can vary for risk, cost or political purposes. Here are some common project requirement configurations across simple, standard and complex project categories;
Each organisation may use different document titles however the purpose and content should be very similar. Some organisations may also use a version system on each of the documents. The core concept here is that collectively all requirements are trapped and documented.
The requirements delivery for a project is directly related to the projects commercial outcomes. Every requirement delivered should exist in one of the requirements documents and each of the requirements should have an associated commercial cost (even if it is $0). A problem we see too often is project teams failing to document $0 changes. Whilst they may think that this is saving time on admin they are actually causing the following potential problems;
At FileBound we would love to hear any thoughts you have around this subject matter. Have we missed anything? Have you noticed similar outcomes?
Contact our team today to discuss your needs and discover how our solutions could deliver big benefits to your organisation.