ITSM20F · Question #51
The success and failure of Releases shall be measured. What is included in these measurements?
The correct answer is B. The Incidents related to a Release in the period following a Release. Measuring the success or failure of Releases focuses on impact - specifically, the Incidents (problems, outages, degradations) that occur in the period immediately following a Release, since these directly indicate whether the Release introduced harm or instability into the…
Question
The success and failure of Releases shall be measured. What is included in these measurements?
Options
- AThe frequency and types of Releases
- BThe Incidents related to a Release in the period following a Release
- CThe Release dates
- DThe Request for Change (RFC)
How the community answered
(47 responses)- A11% (5)
- B83% (39)
- C2% (1)
- D4% (2)
Explanation
Measuring the success or failure of Releases focuses on impact - specifically, the Incidents (problems, outages, degradations) that occur in the period immediately following a Release, since these directly indicate whether the Release introduced harm or instability into the environment. This makes B the correct answer, as it captures the real-world outcome of a Release.
Why the distractors are wrong:
- A (frequency and types): These are descriptive statistics about what was released, not whether it succeeded or failed.
- C (Release dates): Dates are scheduling/planning data - meeting a date says nothing about quality or outcome.
- D (RFC): The Request for Change is an input to the Release process (authorization), not a measurement of its outcome.
Memory tip: Think "Release → Ripple." A Release's success is measured by the ripple effect it causes afterward - if Incidents spike post-Release, it failed; if things stay stable, it succeeded. The RFC comes before, dates are during, and frequency/type describe what - only Incidents tell you how well.
Topics
Community Discussion
No community discussion yet for this question.