Posted by: kerrywills | December 23, 2016

Is Change Control really Controlling Changes?

The industry term of “change control” related to projects is around the management and control of changes to scope to ensure that no unnecessary changes are made and that all changes are documented. But in many cases, it feels like there is not much “control” going on since changes continuously come in and are being assessed (which, by itself, is adding scope and work to the team who has to review and assess the changes). So the process becomes more reactive to changes as opposed to controlling them coming in.


I realize that changes will always occur and there needs to be a mechanism to manage them…and this becomes increasingly more important in an “agile” world where scope is viewed as being more fluid.  However, adding new scope or changing it does have real implications which need to be understood and the only way to do that is to understand it, document it, solution it, review it and to discuss it. So we are living in a world where we need to allow for the flexibility of scope but also have the diligence and transparency to understand, assess and communicate the implications of that flexibility.

While I don’t have the solution for how to manage work in this new environment, I do propose that we submit a change control to modify the term to be called “identify and assess change implications of scope flexibility” since clearly nothing is being controlled.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s


%d bloggers like this: