Problems handed over to Change Enablement

Problem managers often perform the analysis of the problems they identify. That is because the problem manager of a service is typically the person who is technically the most knowledgeable about the service. But when a problem manager has asked another specialist to perform the analysis of a problem, this problem is returned to the problem manager when the specialist has completed the analysis.

Now that the request review has been completed, you return to the Inbox console. There you see that the analysis of problem #219 has been completed. Curious to see the result of the analysis, you open this problem. You read that Frank Watson, who performed the analysis, recommends that the bug be fixed as part of the next minor release of the Expense Reporting application.

This sounds like a good recommendation. Since changes to the code of applications may only be implemented through the Change Enablement practice, you decide to pass this problem to the change manager of the Expense Reporting service.

Do this by changing the status of problem #219 to “Change Requested” and specifying in the Note field that you would like this bug to be fixed as part of the next minor release of the Expense Reporting application. After that you can save the problem.

Question:

Next Exercise