Examples
These are parts of the tabs DeployLogs builds, filled in with its sample deploy: a made-up weekend cutover of a billing system across five teams. Column letters and row numbers are the ones in the sheet. Headings in orange are worked out for you; headings in beige are where you type.
The runlist
Steps from every team, in run order. Each step says what it waits for and what it hands over.
| A | B | D | F | J | K | L | |
|---|---|---|---|---|---|---|---|
| 1 | ID | Run order | Team | Step | Waits for (IDs) | Can start? | Hands over |
| 9 | D-03 | 8 | Billing | Turn on the new billing feature | Ready | ||
| 10 | D-04 | 9 | Billing | Deploy invoice and credit memo templates | D-03 | Waiting on D-03 (Billing) | Invoice and credit memo template IDs, for the integration release |
| 11 | D-05 | 10 | Integration | Deploy the integration release | D-01, D-04 | Waiting on D-01 (CRM), D-04 (Billing) | |
| 16 | C-01 | 15 | Integration | Resume order sync and watch the first orders | M-03 | Waiting on M-03 (ERP) |
Before the deploy starts. On D-05, "Received from earlier steps" reads: D-04: Invoice and credit memo template IDs, for the integration release (not handed over yet).
Estimates
Plan hours use the longest practice run, times the data size factor. With no practice run, they use the owner's estimate.
| A | F | O | P | Q | S | T | U | |
|---|---|---|---|---|---|---|---|---|
| 1 | ID | Step | Owner estimate (hrs) | Practice run 1 (hrs) | Practice run 2 (hrs) | Data size factor | Plan hours | Estimate source |
| 13 | M-01 | Run the account migration | 3.0 | 3.0 | 2.5 | 1.4 | 4.2 | Practiced |
| 14 | M-02 | Migrate billing accounts | 4.0 | 4.0 | Owner's guess | |||
| 15 | M-03 | Load customer records | Missing |
The overview
Every number says where it comes from. Some rows are left out here.
| A | B | C | |
|---|---|---|---|
| 1 | Deploy overview | Where this comes from | |
| 7 | Where we are | ||
| 9 | Steps left | 19 | Steps that are not Done or Skipped. |
| 16 | Projected finish | Sun 25 Oct, 12:12 am | Now (or the planned start, if that is later) plus plan hours left and planned waits left. Assumes steps run one after another. |
| 17 | On track? | Yes, 29.8 hrs to spare | Projected finish compared with the deadline. |
| 35 | If something goes wrong | ||
| 36 | Hours to roll back everything | 13.0 | Rollback hours of every step except Skipped ones. |
| 39 | Latest safe time to keep going | Sat 24 Oct, 7:48 am | Deadline minus plan hours left, planned waits left and the time to roll back everything. |
| 41 | How solid is the plan | ||
| 42 | Plan hours backed by a practice run | 44% | Plan hours of Practiced steps, out of all plan hours. |
| 44 | Steps with no estimate | 2 | Steps whose estimate source is Missing. |
| 47 | Teams not ready | 2 | Teams whose "Ready?" on the Teams tab is Not ready or No steps listed. |
Changes
Each change in the deploy, and whether it is covered.
| A | B | F | I | K | |
|---|---|---|---|---|---|
| 1 | ID | Change | Steps | Smoke tests | Covered? |
| 2 | F-01 | New billing feature: billing attributes on accounts | 2 | 1 | Rollback missing |
| 3 | F-02 | New invoice and credit memo templates | 1 | 1 | Not signed off yet |
| 7 | F-06 | Customer records flow to ERP | 2 | 0 | No smoke test |
Smoke tests
Every test names the person in the business who signs off the result.
| A | D | K | O | P | R | |
|---|---|---|---|---|---|---|
| 1 | ID | What we are testing | Result | Business sign-off by | Business sign-off | Sign-off check |
| 2 | T-01 | A new order syncs to billing on the right billing account | Passed | Morgan | Approved | Signed off |
| 4 | T-03 | Invoice uses the new template | Passed | Alex | Waiting for sign-off | |
| 6 | T-05 | Test bill run groups charges by billing attributes | Not run | No one accountable |
Partway through business testing: T-01 and T-03 have been run. In the sample as filled in, every test starts as Not run.
Data migration
Record counts before, expected after, and loaded. Merging records can make the expected count lower.
| A | B | I | J | L | O | |
|---|---|---|---|---|---|---|
| 1 | ID | What is moving | Records before | Records expected after | Records loaded | Match |
| 2 | DM-01 | Accounts | 12,480 | 12,480 | 12,480 | Matches |
| 3 | DM-02 | Billing accounts | 9,310 | 8,655 | 8,642 | Does not match |
| 4 | DM-03 | Customer records to ERP | No expected count |
The loaded counts are made up to show each result. The sample leaves them blank until the migration runs.
Teams
Every team is held to the same rule. A team with no steps at all shows No steps listed.
| A | E | F | N | |
|---|---|---|---|---|
| 1 | Team | Steps | Practiced | Ready? |
| 2 | CRM | 7 | 100% | Ready |
| 3 | Billing | 6 | 0% | Not ready |
| 4 | Integration | 3 | 100% | Ready |
| 5 | ERP | 2 | Not ready | |
| 6 | Business | 1 | 0% | Partly practiced |
Audit log
During a run, only the person running it can edit, and the audit log records every edit.
| A | B | C | D | E | F | G | H | |
|---|---|---|---|---|---|---|---|---|
| 1 | When | Who | Tab | Row | Field | Old value | New value | Note |
| 2 | Fri 23 Oct, 6:02 pm | avery@example.com | Steps | D-01 | Status | Not started | In progress | |
| 3 | Fri 23 Oct, 7:41 pm | avery@example.com | Steps | D-04 | Value handed over | INV-2207, CM-0419 | ||
| 4 | Fri 23 Oct, 7:43 pm | avery@example.com | Gates | Row 5 | Call | Go |
These rows are made up to show what an entry looks like.
Building a tracker
Building takes about a minute. The dialog shows each step as it goes.
Build a new tracker
Step 6 of 17: Laying out Steps… 23s
This takes about a minute. Keep this window open until it finishes.