...
Status | Activity | Description | Duration |
|---|---|---|---|
| Submit change request | Open a build/test change request in https://yale.service-now.com/, assign to | minutes |
(n/a) | Schedule code review (Mon 1pm) | this should happen after initial handover and before release | minutes |
| Build phase work | Begin work in dev | days |
| Unit tests | Ensure all pushed to tst & unit tested | hours |
| Initial code freeze | Hand over initial requirements list for functional & QA validation in tst | minutes |
| Conduct code review | Shouldn't take long, just basic validation of approach and docs | hours |
| Defect fixes | Iterative follow-up work in dev, test for defect resolution | days |
| Finalize release | Identify changes & updates that are going/not going. Push to (tst). | hours |
| Final code freeze | Hand over final requirements list for functional & QA validation, w/ regression, in (tst) | 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 |
(n/a) | Clone | clone from prd to: pre, trn, and tst for after release | 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 |
| Target/Actuals | Deliver target/actuals using estimator spreadsheet or equivalent | hours |
Change Control
Release Notes
https://yale.service-now.com/kb_view.do?sysparm_article=KB0000066
...