Change Schedule
A calendar that contains details of all planned changes. It is used to plan changes, identify potential conflicts, and communicate planned maintenance windows to stakeholders.
A calendar that contains details of all planned changes. It is used to plan changes, identify potential conflicts, and communicate planned maintenance windows to stakeholders.
Visibility prevents collision. Knowing that the network team is upgrading the firewall at the same time the database team is migrating the schema helps prevent catastrophic outages.
If you need a complex manual Change Schedule, your architecture is likely too tightly coupled. In a truly decoupled microservices architecture, Team A should be able to deploy without knowing or caring what Team B is doing. We aim to architect away the need for a calendar.