82
edits
CloudServices/Principles: Difference between revisions
Jump to navigation
Jump to search
→Careful change control
| Line 5: | Line 5: | ||
Change is managed through these policies: | Change is managed through these policies: | ||
* complex changes require a step-by-step plan | * complex changes require a step-by-step plan, including a back-out plan (though, if "perform roll-out steps in reverse" is correct, that's fine). All plans are to undergo a step-by-step "dry run" before executing live. | ||
* a secondary person helps with / checks plans for complex changes (buddy system) | * a secondary person helps with / checks plans for complex changes (buddy system) | ||
* points of commitment (or "no return") have go/no-go calls with a clear owner / deterministic datapoint | * points of commitment (or "no return") have go/no-go calls with a clear owner / deterministic datapoint | ||
* all change plan worthy events must have a clearly defined owner who is responsible for "heads-up", "starting", & "all-clear" communications, as well as any write-up on deviations from the plan or other problems | * all change plan worthy events must have a clearly defined owner who is responsible for "heads-up", "starting", & "all-clear" email communications (and twitter, Yammer, IRC, etc as needed), as well as any write-up on deviations from the plan or other problems. | ||
== Rules of engagement == | == Rules of engagement == | ||