Summary
- CMDB release 1
- new catalog items
- START items
Progression
Status |
Activity |
Description |
Duration |
---|---|---|---|
|
Submit change request |
Open a build/test change request in https://yale.service-now.com/, assign to |
minutes |
(bw is away) |
Schedule code review |
this should happen after initial handover and before release |
minutes |
|
Build |
Begin work in dev |
days |
|
Developer tests |
Ensure all pushed to and unit tested in test |
hours |
|
Push to Test |
Hand over initial requirements list for functional & QA validation |
minutes |
(bw is away) |
Conduct code review |
Shouldn't take long, just basic validation of approach and docs |
hours |
(in progress) |
Testing |
UAT & product testing (testing instance) |
days |
(in progress) |
Defect fixes |
Iterative follow-up work in dev, test for defect resolution |
days |
() |
Code Freeze |
Identify changes & updates that have passed both testing regimes. Push to preproduction. |
hours |
() |
Regression Testing |
QA group conducts regression testing in preproduction |
minutes |
() |
Go/no-go |
Decide to push to production. |
minutes |
() |
Production deployment |
Push to prd. |
hours |
() |
Production rollback |
If applicable; follow ServiceNow Rollback Procedure. |
hours |
() |
Clone |
clone from prd to: pre, trn, and tst for after release |
hours |
() |
Push to Test |
re-push outstanding, ready work back to test |
hours |
() |
Notify stakeholders |
send out email w/ summary status & link to release documentation, close out RFC and cancel clone requests, if rollback or no-go. |
minutes |
Change Control
Release Notes
https://yale.service-now.com/kb_view.do?sysparm_article=KB0001428
Documentation
Detail is provided in the description. Full implementation detail is captured in the update set, which can be viewed (with admin rights) by drilling down into the links.
Approved Updates
Update_Set_Name |
Description |
---|