[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-162187-105":3,"detail-sidebar-cat-1-en-105":80,"doc-detail-162187-en":126},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":73,"head_meta":75,"extra_data":77,"updated_unix":79},105,"en","ewf-go-live-deployment-checklist-deployment-guide","EWF Go-Live Deployment Checklist - Deployment Guide","","EWF Go-Live Deployment Checklist provides a structured deployment guide covering prerequisite, implementation, and validation activities for production go-live. It defines roles and contact considerations, outlines weekly-reviewed prerequisite tasks with status tracking, and specifies health checks to prevent issues on implementation and the following day. The guide also describes parallel implementation streams, handling of go-live bugs via ServiceNow defect records, and enhancements via ServiceNow story backlog management. An appendix run sheet details pre-commit, commit, and post-commit steps.",{"@graph":14,"@context":72},[15,34,55],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/presentations/","Presentations",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/ewf-go-live-deployment-checklist-deployment-guide/162187/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/ewf-go-live-deployment-checklist-deployment-guide/162187.png","ImageObject",442,249,{"name":42,"@type":43},"Eden","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/vnd.openxmlformats-officedocument.wordprocessingml.document","2026-09-20","2026-08-30",true,{"@type":52,"interactionType":53,"userInteractionCount":30},"InteractionCounter",{"@type":54},"ViewAction",{"@type":56,"mainEntity":57},"FAQPage",[58,64,68],{"name":59,"@type":60,"acceptedAnswer":61},"What is the purpose of this go-live deployment checklist?","Question",{"text":62,"@type":63},"It organizes prerequisite, implementation, and validation activities to ensure a controlled EWF go-live in production. It also standardizes tracking and post-release readiness checks.","Answer",{"name":65,"@type":60,"acceptedAnswer":66},"Which health checks are performed and when?",{"text":67,"@type":63},"Health checks are performed on the day of implementation to avoid issues affecting the planned change. Additional health checks are performed on the day after implementation to confirm the environment supports business needs.",{"name":69,"@type":60,"acceptedAnswer":70},"How are go-live bugs and enhancements handled?",{"text":71,"@type":63},"Implementation issues are tracked in ServiceNow Agile Development as defect records for triage, prioritization, fix, testing, and deployment. Requested enhancements are captured as story records for backlog prioritization and sizing.","https://schema.org",{"og:url":32,"og:type":74,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":76,"canonical":32},"index,follow",{"doc_id":78,"site_id":7},162187,1788119881,{"code":4,"msg":81,"data":82},"success",[83,87,92,97,102,107,112,117,122],{"id":84,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":85,"slug":86},11,90,"presentations",{"id":88,"doc_module":22,"doc_module_name":25,"category_name":89,"show_sort_weight":90,"slug":91},12,"Resumes",80,"resumes",{"id":93,"doc_module":22,"doc_module_name":25,"category_name":94,"show_sort_weight":95,"slug":96},14,"Invoices",70,"invoices",{"id":98,"doc_module":22,"doc_module_name":25,"category_name":99,"show_sort_weight":100,"slug":101},15,"Posters",60,"posters",{"id":103,"doc_module":22,"doc_module_name":25,"category_name":104,"show_sort_weight":105,"slug":106},16,"Social Media",50,"social-media",{"id":108,"doc_module":22,"doc_module_name":25,"category_name":109,"show_sort_weight":110,"slug":111},17,"Forms",40,"forms",{"id":113,"doc_module":22,"doc_module_name":25,"category_name":114,"show_sort_weight":115,"slug":116},18,"Letters",30,"letters",{"id":118,"doc_module":22,"doc_module_name":25,"category_name":119,"show_sort_weight":120,"slug":121},21,"Paper Templates",5,"papers-templates",{"id":123,"doc_module":22,"doc_module_name":25,"category_name":124,"show_sort_weight":4,"slug":125},158,"General","general-158",{"code":4,"msg":81,"data":127},{"doc_id":78,"user_id":128,"nickname":42,"user_avatar":129,"doc_module":22,"category_id":84,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":30,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":135,"language":136,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":12,"update_tm":79,"read_time":140},1374391974468,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","EWF Go-Live Deployment Checklist\nDeployment Guide\n\u003CProject Name>\nAsset number: 0003913\nUpdated: June 2024\n\u000f\n\u0003Table of Contents\n\u0013 TOC \\o \"1-3\" \\h \\z \\t \"03_Subhead Body Title,1,04_Subhead Body,2\" \u0014\u0013 HYPERLINK \\l \"_Toc168937990\" \u0014Background\t\u0013 PAGEREF _Toc168937990 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc168937991\" \u0014Contacts\t\u0013 PAGEREF _Toc168937991 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc168937992\" \u0014Prerequisite activities\t\u0013 PAGEREF _Toc168937992 \\h \u00144\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc168937993\" \u0014Health checks\t\u0013 PAGEREF _Toc168937993 \\h \u00148\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc168937994\" \u0014Implementation\t\u0013 PAGEREF _Toc168937994 \\h \u00149\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc168937995\" \u0014Post implementation – Day 1\t\u0013 PAGEREF _Toc168937995 \\h \u001414\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc168937996\" \u0014Go-Live bugs & enhancements\t\u0013 PAGEREF _Toc168937996 \\h \u001415\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc168937997\" \u0014Notes\t\u0013 PAGEREF _Toc168937997 \\h \u001415\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc168937998\" \u0014Appendix A – Run sheet\t\u0013 PAGEREF _Toc168937998 \\h \u001416\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc168937999\" \u0014Pre-commit\t\u0013 PAGEREF _Toc168937999 \\h \u001416\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc168938000\" \u0014Commit\t\u0013 PAGEREF _Toc168938000 \\h \u001419\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc168938001\" \u0014Post-commit\t\u0013 PAGEREF _Toc168938001 \\h \u001420\u0015\u0015\n\u0015\u0004\nBackground\nThe following plan covers the prerequisite, implementation, and validation activities relating to Go-Live for the \u003C‘[add release/project name here]’>\nContacts\nThe following resources are involved with the implementation or validation of the change.\nNote: Highlight in the table above whether contacts are ‘onsite’ or ‘remote’ for the implementation.\nPrerequisite activities\nThe following activities must be completed before the production implementation can be executed. These should be reviewed with the implementation team each week in preparation for Go-Live.\nNote: The values for ‘Status’ should be open, work in progress, blocked, or closed.\nNote: You can also create ‘Actions’ for some of the above activities in PPM to ensure visibility for the team member assigned and track progress to completion.\n\u000f\nHealth checks\nThe following health checks should be performed in the production environment on the day of implementation to ensure no issues could impact the planned change.\n\u000f\nImplementation\nThe following activities can only be completed after the approved change start time.\nNote: There may be multiple streams of activity running in parallel for larger deployments. Ensure the dependencies for activities are clearly documented above.\n\u000f\nPost implementation – Day 1\nThe following health checks should be performed in the production environment on the day following implementation to ensure the environment is ready to support the business.\n\u000f\nGo-Live bugs & enhancements\nAny ‘issues’ identified from the implementation to be tracked in the ServiceNow Agile Development application as a ‘defect’ record for triage, prioritization, fix, testing, and deployment.\nIf required, a Case will be raised with ServiceNow Customer Support using the \u000b\u0013 HYPERLINK \"https://hi.service-now.com/\" \u0014HI Service Portal\u0015.\nAny ‘enhancements’ requested from product owners or end-users should be created in the ServiceNow Agile Development application as a ‘story’ for prioritization and sizing of the backlog.\nNotes\nCapture any notes from the dress rehearsal or production implementation here.\nAppendix A – Run sheet\nThe following steps are referenced in the implementation plan above. This run sheet may be replaced by a separate file depending on the agreed approach with the business, e.g. Excel spreadsheet, Knowledge article.\nThe steps in the run sheet should be populated by the development team as migrations are performed between the development and other non-production instances.\nPre-commit\nThis stage of the deployment is intended for setting up the prerequisites for the deployment. It includes installing/activating plugins, importing/creating data that later steps depend on.\nNote: A SysAdmin, Developer, or Platform Architect may be assigned to peer review activities above as they are performed.\nCommit\nThis stage of the de","cbCainhQ8or6xd8D","https://ap.wps.com/l/cbCainhQ8or6xd8D","docx",114020,20,"English","# Background\n# Contacts\n# Prerequisite activities\n# Health checks\n# Implementation\n# Post implementation – Day 1\n# Go-Live bugs & enhancements\n# Notes\n# Appendix A – Run sheet\n## Pre-commit\n## Commit\n## Post-commit","[{\"question\":\"What is the purpose of this go-live deployment checklist?\",\"answer\":\"It organizes prerequisite, implementation, and validation activities to ensure a controlled EWF go-live in production. It also standardizes tracking and post-release readiness checks.\"},{\"question\":\"Which health checks are performed and when?\",\"answer\":\"Health checks are performed on the day of implementation to avoid issues affecting the planned change. Additional health checks are performed on the day after implementation to confirm the environment supports business needs.\"},{\"question\":\"How are go-live bugs and enhancements handled?\",\"answer\":\"Implementation issues are tracked in ServiceNow Agile Development as defect records for triage, prioritization, fix, testing, and deployment. Requested enhancements are captured as story records for backlog prioritization and sizing.\"}]","EWF Go-Live Deployment Checklist - Deployment Guide | DOCX",7]