Change management

Controlling how changes reach production systems.

Changes should be requested, assessed, approved, tested and moved to production by someone other than the developer, with records kept. Emergency changes can skip some steps up front but must be documented, approved and reviewed after the fact.

On the exam

For an emergency change, the right answer is retrospective approval and review, not a ban on emergency changes. Developers with production access is a classic finding.

Related terms

Segregation of dutiesSplitting key steps of a process so no one person can both commit and hide an error or fraud.
Post-implementation reviewChecking, after go-live, whether a project delivered what it promised.

Test yourself with today’s question of the day.