All service changes should be reflected in Change Management records. Which of the aspects below is an example of a service change, that needs to be reflected in a Change record?
Hmm, I think Michael has a point. Those other options seem like they could also be considered service changes that require Change Management documentation.
I'm not sure about that. Wouldn't a major Incident or a Service Level Agreement failure also be considered service changes that need to be reflected in the Change records?
I've got a good handle on service changes from my work experience. I'd say A and B are the obvious answers here. The other two are more about incidents and problems, which may or may not require a Change record depending on the specifics.
I think the key here is to focus on anything that changes the normal delivery of the service. A formal closure, a major Incident - those are clear service changes. The other options are a bit more ambiguous, so I'll have to weigh those carefully.
Okay, let me see if I can break this down. A Service Level Agreement failure could potentially impact the service, so that might need to be recorded. But an identified Problem? I'm not sure how that fits in.
Fernanda
3 days agoRaelene
8 days agoMa
13 days agoRosalind
18 days agoCherry
24 days agoCraig
29 days agoGoldie
1 month agoVal
2 months agoHobert
2 months agoAshleigh
2 months agoBen
2 months agoMatthew
3 months agoJosue
3 months agoCary
3 months agoAdelaide
3 months agoJunita
3 months agoHelene
3 months agoCarma
4 months agoRyan
4 months ago