Changes

CIA ambushes Business Analyst

BAs will often work closely in creating a CIA, however its not always pleasing work.
CIA = Change Impact Assessment 😋

A CIA is vitally important for the OCM team to successfully manage stakeholder engagement in making sure
- expected project deliverable is acceptable,
- broad number of end-users are engaged,
- satisfactory training of users is conducted,
- senior stakeholders are happy with expected outcomes from an end-user perspective.

A CIA is a deeper analysis on the differences and similarities that a user can expect between what they may have today vs. what they will get on go-live and potentially subsequent releases.

Any changes to the following;
- scope
- resources unavailability
- Solution is not final and evolving
And soon a CIA becomes a hinderance for BAs - requiring more time and effort.

When this happens, the PM needs to make a firm decision on what takes priority and equally state what activities will suffer as a result.
- In my experience this is where BA's will often get caught out and frustrations start to set in.

The CIA is sometimes misunderstood, but given proper planning it is highly useful for both the OCM team and BAs when engaging stakeholders for validation, training and testing and great for support material