|
Who We Are |
|
Agreements |

|
Home |


|
TM |
|
Get Ahead |
|
Stay Ahead |
|
Assistance@AssistUK.org |

|
Home |

|
? |
|
Why |
|
|
|
Projects work in dynamic environments across multiple disciplines, leading to constant changes and clarification. Changes need to be controlled to ensure the whole project can be moved forward together and people can remain focused and clear on the deliverable while the final product meets the environment and requirements in which it is implemented. |
|
|
|
Our Consultants can provide independent views on whether changes are clarification or changes to the original specifications. |
|
|
|
|

|
What |
|
The strategy for change control includes clarity on the baseline which change is to be applied to and the frequency of change e.g. as needed, monthly when the final freeze is made (if any) to ensure everything is tested before implementation. This then overflows to post-implementation. |
|
How |
|
This will be determined with you, but typically: |
|
|
|
· Agree the Strategy with the business, project, development, test and implementation teams |
|
· Agree standards, templates and where relevant tools. |
