No response submitted.
No response submitted.
In the event a change involves an IT process, it would seem appropriate either in the request form, the Workplan or elsewhere to provide an install plan, backout plan and test plan. This would help set expectations in the event a change is not seamlessly implemented, similar to common ITIL practices.
"Incomplete forms submitted after December 16 will not be considered in the following year’s Workplan." - Would be worth describing what the cure process looks like and how much time it is given.
Would it be beneficial to have an “other” type of Change Request? This would be if a submitter is unsure, or they may not know the correct selection in the type of change list provided.
In this section of the BPM, it would be helpful to show a summary table of the Workplan Development phase that would include a deadline , task and owner for each individual step of the process. From a visual standpoint, a summary table would make things much easier for the reader.