Release, deployment, change, suppliers and events

Five practice purposes that questions ask you to recognise from a paraphrase, including the release and deployment pair that is the most confused boundary in the whole objective.

Lesson 1 of 3 in objective 6. Purpose and key terms of 15 ITIL practices, part of ITIL 4 Foundation.

Release and deployment: two practices, two different questions. Deployment management — The question it answers: Where have the components been moved to?; Environments involved: Live, and also test and staging; Can happen without the other?: Yes — deployed behind a switch, not released. Release management — The question it answers: When can people actually use it?; Environments involved: Availability for use, wherever it sits; Can happen without the other?: Yes — switched on with nothing newly deployed Deployment management Release management The question it answers Where have the components been moved to? When can people actually use it? Environments involved Live, and also test and staging Availability for use, wherever it sits Can happen without the other? Yes — deployed behind a switch, not released Yes — switched on with nothing newly deployed
Release and deployment: two practices, two different questions.

Release and deployment, which are not the same event

Deployment management moves components — hardware, software, documentation and the rest — into an environment. The detail that decides questions is that those environments include test and staging, not only production; an option that restricts deployment to live environments is subtly wrong.

Release management is about making new or changed services and features AVAILABLE FOR USE. That is a different question from where the bits are sitting. Modern practice makes the split obvious: code can be deployed behind a feature switch without anybody being able to use it, and a release can be turned on for users without anything new being deployed at all. If a question is about moving things, it is deployment; if it is about when people can start using them, it is release.

Change enablement, and what its purpose actually is

Change enablement exists to maximise the number of SUCCESSFUL product and service changes — by making sure risk is assessed properly, authorisation happens before work starts, and a schedule of authorised work is maintained. The recognition cue is that combination: successful changes, risk assessed, work authorised, schedule kept.

What it is not is a brake. Its purpose is not to minimise the number of changes, not to prevent change, and not to act as a gate that work has to survive. The rename from the older "change management" was meant to signal exactly that, and an option describing the practice as controlling or restricting change is testing whether you absorbed the shift.

Change enablement, next to the brake the wrong option describes. The practice — What it does with change: Maximises successful changes; How it does it: Risk assessed, authorised before work starts, schedule kept; The tell in the option: The word successful. The wrong option — What it does with change: Minimises or prevents change; How it does it: A gate that work must survive; The tell in the option: Controlling and restricting language The practice The wrong option What it does with change Maximises successful changes Minimises or prevents change How it does it Risk assessed, authorised before work starts, schedule kept A gate that work must survive The tell in the option The word successful Controlling and restricting language
Change enablement, next to the brake the wrong option describes.

Suppliers, and watching what services do

Supplier management ensures the organisation's suppliers and their performance are managed so that a seamless quality of products and services is delivered. The scoping word is SUPPLIERS: if the scenario is about another organisation you buy from and how well it performs, this is the practice.

Monitoring and event management keeps services and their components under continuous observation, records the changes of state that matter and reports them, and settles what the right response to each one should be. The two halves are what identify it: observing state, and deciding what a change of state means. An event is a change of state with significance, and the practice is about noticing it and responding rather than about fixing anything, which is where incident management takes over.

What monitoring and event management does with an event, and where it hands over. In order: Observed continuously (the services, and the components under them), then A state change that matters (that is what makes it an event), then Recorded and reported (on the record, and passed on), then The right response settled (responding is the job; fixing is not), then Over to incident management (resolution never belonged to this practice). Observed continuously the services, and the components under them A state change that matters that is what makes it an event Recorded and reported on the record, and passed on The right response settled responding is the job; fixing is not Over to incident management resolution never belonged to this practice
What monitoring and event management does with an event, and where it hands over.

Worth carrying in

Release management
Making new or changed services and features available for use.
Deployment management
Moving components into environments — live, and test and staging too.
Change enablement
Maximising SUCCESSFUL changes: risk assessed, work authorised, schedule kept.
Supplier management
Suppliers and their performance, for seamless quality.
Monitoring and event management
Watch state, report the changes that matter, decide the response.

What the exam does with this

Objective
6. Purpose and key terms of 15 ITIL practices
Share of the exam
12.5% (the whole objective)
Questions in this lesson
5
Signed for by a person
0

Partly checked. None of the 5 questions here has been read against the cited source by a person. 5 questions have been checked against their cited clause by an automated pass — which is not the same thing, and is not a signature.

Only questions a person has signed for are used in mock exams here. That is the whole difference between the two kinds of checking above.

How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.

Drill this lesson

A lesson is one sitting: the trainer draws a short run from these questions alone and spaces the ones you get wrong.

Practise Release, deployment, change, suppliers and events

Questions in this lesson

Practise Release, deployment, change, suppliers and events

The rest of objective 6