...
Status | Activity | Description | Duration |
|---|---|---|---|
| Submit change request | Open a build/test change request in https://yale.service-now.com/, assign to | minutes |
| Schedule code review | this should happen after initial handover and before release | minutes |
() | Initial development, pushes to test | Begin work in dev | days |
() | QA, UAT in test | iterate on defects found by QA and UAT feedback; any items passing both should be moved to "Ready to Release" column | hours |
() | Conduct code review | Shouldn't take long, just basic validation of approach and docs | hours |
() | Code Freeze | By Wed AM: Identify changes & updates that have passed both testing regimes. Push to preproduction. | hours |
(in progress) | Regression Testing | QA group conducts regression testing in preproduction | minutes |
(pending) | Go/no-go | Get approval from QA to go 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 |
...