Lesson 5 of 5
Publishing and maintaining the calendar
9 min
A calendar nobody reads is a private plan. A calendar people read but do not trust is worse, because they keep their own. Luis's goal is one calendar, owned by him, versioned, with sources, that each audience can read at the level it needs. Grace sponsors it at the steering committee; Priya relies on it to book testers; Dan and Maria use it to plan around their busiest weeks.
What a good calendar entry contains
| Field | Example |
|---|---|
| Event | Feature pack stack applied to production |
| Date and time, with time zone | Saturday, 06:00 to 14:00 Eastern |
| Systems | CMP; BTP subaccount cmc-ext-prod smoke tested afterwards |
| Source and date checked | Stack availability from SAP release information, checked on the first of the month |
| Freeze rules | Scope freeze two weeks before; no other imports that weekend |
| Testing | Full regression completed in CMQ; production smoke test by Maria and Dan |
| Owner and status | Luis; Planned, Confirmed, Done or Moved |
Fields for each calendar entry.
A monthly rhythm
- Verify SAP datesRecheck sources for anything in the next six months; read Patch Day results
- Update the calendarApply changes, adjust freezes and windows
- Publish a new versionVersion number and a short change log at the top
- Notify the people affectedOnly those whose dates or duties changed, with what changed and why
- Confirm resourcesPriya confirms testers and environments for the next windows
- Review after eventsDid the window suffice? Feed lessons into the next plan
The change log matters more than it looks. When SAP moves a public edition upgrade date or a stack slips, people need to see quickly what changed: "Version 7: second stack moved from November to January; regression window now December 1 to 19; no change to year-end freeze." A clear log keeps trust, because nobody has to compare two versions line by line.
| Channel | Good for | Not for |
|---|---|---|
| Published calendar page or shared document | The single source of truth, with versions and sources | Urgent changes nobody will see in time |
| Steering committee pack | Quarter view, decisions and risks | Day-level detail |
| Release notice email or channel post | Telling affected people what changed and what to do | Holding the full calendar |
| Change advisory board | Approving specific changes and windows | Long-range planning |
When SAP changes a date
Dates will move, and how the change is handled decides whether the calendar keeps its credibility. Luis follows the same four steps every time: confirm the new date in the primary source, assess the knock-on effects (freezes, regression windows, people), publish a new version with a one-line change log, and send a targeted notice with a proposal to the people affected. He does not wait for the monthly cycle when a change touches the next six weeks.
- Confirm the new date in the primary source and record the check date.
- Assess what else moves: freezes, regression windows, testers, environments.
- Publish a new version with a one-line change log.
- Notify only the people affected, with a proposal, not just the problem.
What would you do?
SAP's published schedule shows that the quarterly upgrade of the SAP BTP ABAP environment hosting Contoso's warranty prototype has moved by one week, so the pre-upgrade regression window now overlaps with Contoso's quarter-end close freeze, when key users are busy. What should Luis do first?
- One calendar, one owner, versioned, with sources for every date.
- Give each audience the right level: quarter view for steering, details for testers and IT.
- Each entry carries date with time zone, systems, source, freeze rules, testing, owner and status.
- Run a monthly cycle: verify, update, publish with a change log, notify, confirm resources, review.
- Acknowledgment from the people who must act is the evidence that communication worked.
Check your understanding · not graded
Lesson check
1. Why publish a change log with each calendar version?
2. What level of detail suits the steering committee?
3. What is the best evidence that a freeze has been communicated?
4. Which field helps resolve disputes about a date?