Guides

The rules behind DeployLogs

Why the tracker asks for what it asks for.

• One runlist, in order, across every team. Including the waits and the handoffs between teams.
• The practice run puts real numbers on estimates. Where a system has no test environment, say so.
• Progress is finished steps. Not a percentage someone reports.
• Rollback, not heroics. A tested or walked-through rollback beats a hero at 2am.
• Know which steps mean stop. Decide before the day.
• A freeze window everyone agreed to. Changes made after a backup are lost on rollback.
• Sign-off agreed up front. Someone in the business owns every smoke test, by name.
• The same rule for every team. Nobody gets a pass, and nobody is singled out.
• Every number says where it comes from.
• Keep the record. Each deploy's spreadsheet is the record of what happened.