At the last moment, just before the deployment of a new release, it is reported that one of the changes in the release isn't going to be ready in time. In which process is decided whether the change…

Question

Options

• APlanning and resource management
• BTransition
• CChange management

• A
  70% (23)
• B
  18% (6)
• C
  12% (4)

Explanation

Planning and resource management is where release scope decisions are made - it defines which changes are included in or excluded from an upcoming release. When a change is reported as not ready at the last moment, it is the planning process that evaluates the impact and formally decides whether to pull it from the release or delay the deployment.

Option B (Transition) is wrong because Transition (or deployment) is the execution phase - it carries out the release as planned, but it does not determine the release's content or scope.

Option C (Change management) is wrong because Change management governs the approval and tracking of individual changes throughout their lifecycle, not the decision about which changes are bundled into a specific release.

Memory tip: Think of it as "Planning = guest list." You decide who's invited to the release during Planning. Transition is the party itself - by then the list is set. Change management is like the RSVP process for each individual guest, which is separate from deciding the final attendee roster.

No community discussion yet for this question.