required or not. See the home page for details on the service capability. The service Phase two of the ServiceNow project is now at an advanced stage of planning. All remaining requirements have been development identified and structured into workstreams. We have developed the Service Development Map as a standardised journey way to deliver each of these workstreams. A visual guide for The Service Development Map has been developed using standard project management practices, but it has also ServiceNow future been informed by the challenges encountered in the earlier implementation! phase of the project. In addition, as you dig a little deeper into the project plan you see that each map element has activities that meet our working processes: Work Packages, Test Plans, RfC’s, etc. For all involved in governing the project and those involved in delivering the workstreams, the Service Development Map should act as an accessible way to see what happens and in what order. For example: Training resources are engaged from the very start and are involved throughout, and beyond the release. Testing and Build resources are also engaged at the same time and fall out of the scoping. For me as Project Manager, the Service Development Map helps me identify dependencies and also understand where delays could impact the critical path and overall project schedule. Enhancements & Small scale improvements There is now a Support Guide link in the user portal. improvements Separately, the Incident form Email function gets Due to the patching process with more comprehensive and useful information, such as Full Name, Email Address and User ID. mentioned in previous newsletters, larger scale Change module has also been further enhanced: improvement projects have Separate Technical/Peer Approver field been held until patching is Added Environment field (Production/ Preproduction/ completed. However a Development) number a small scale
required or not. See the home page for details on the service capability. The service development journey A visual guide for ServiceNow future implementation! Phase two of the ServiceNow project is now at an advanced stage of planning. All remaining requirements have been identified and structured into workstreams. We have developed the Service Development Map as a standardised way to deliver each of these workstreams. The Service Development Map has been developed using standard project management practices, but it has also been informed by the challenges encountered in the earlier phase of the project. In addition, as you dig a little deeper into the project plan you see that each map element has activities that meet our working processes: Work Packages, Test Plans, RfC’s, etc. For all involved in governing the project and those involved in delivering the workstreams, the Service Development Map should act as an accessible way to see what happens and in what order. For example: Training resources are engaged from the very start and are involved throughout, and beyond the release. Testing and Build resources are also engaged at the same time and fall out of the scoping. For me as Project Manager, the Service Development Map helps me identify dependencies and also understand where delays could impact the critical path and overall project schedule. Enhancements & improvements Due to the patching process mentioned in previous newsletters, larger scale improvement projects have been held until patching is completed. However a number a small scale Small scale improvements There is now a Support Guide link in the user portal. Separately, the Incident form Email function gets with more comprehensive and useful information, such as Full Name, Email Address and User ID. Change module has also been further enhanced: Separate Technical/Peer Approver field Added Environment field (Production/ Preproduction/ Development)
Newsletter_Issue_7_final.docx