Project Assurance

One of the hardest things to do with any new project initiative is to truly quantify the scale and scope of the effort involved.

A project may have an outline brief, normally with input from the sponsoring executives and some cost saving/revenue generating figures.

However, what is often lacking is a clear view of how the intended solution will be used operationally – how many teams will be affected by the change in process, how these changes affect other manual processes and procedures, whether there are any other regulatory considerations and whether there is accurate static data already maintained for this process to function.

This is often information which is discovered later in the project lifecycle, causing costly rework, additional effort, moved delivery dates, additional stakeholders being identified late and the impacts of the project scope being revised during the build phase.