You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm hoping to get some feedback from the community on how to handle service requests that are actually projects. For example, we received a request to change the name of a hospital. One of our applications contains a list of hospitals which requires a code change to update. We are starting a project to make it so a code change is not longer required and to turn this into a standard change going forward but a question arose about what to do with the initial service request ticket? Do we close it and open a change request?
Another example - we have a ticket open to make a change to an environment that is scheduled to happen in January. Should that be converted to a change request?
How do other people handle requests that get assessed and then a decision is made to put them into a project?
We are having trouble knowing what to do with things that are kind of like "to dos"...i.e. this needs to be done and it will be done as part of X project. Do we just close the ticket and make sure it is added to project scope?
We are fairly new to ITIL and have implemented RF, IM and PM but do not really have a change management process. As I write this I am beginning to think maybe these are changes and we should implement change management next!
Thanks for your help!