Deployment windows

A deployment window records the project, window name, due date, owner and outcome. The owner checks pending windows before the due date and records Met or Missed after the planned event. Operations Overview brings the delivery and exception state together across authorized projects, while Deployment Windows At Risk keeps pending and missed windows in one list.

• Owner. Project Manager keeps the window owner and due date current. Delivery Lead compares the pending window with package work, open issues and recorded decisions. After the planned event, the owner records Met or Missed with an explanation in notes.
• Record. A window has a project reference but no direct release-package reference. Agree which package is being discussed and check that its project matches the window before reporting the outcome. Keep the execution result in the connected delivery system and use the window notes to explain what the team observed.
• Decision. Record the outcome only after the planned event and explain the observed result in notes.

Agree who owns each window, which release package the team discusses when assessing it, and what evidence supports a Met outcome. A due date is a planning commitment. The team should decide how deployment execution and its logs will be linked into the operating process.

Rehearse this module with an active project and a package whose dates the team can discuss. Give each participant access to the linked records they need, then ask a second person to find the same owner, status and next action. Keep the original record available for the next review.

Consider a package whose remaining tasks look complete while an issue is still open. The project manager checks the window date and asks the delivery lead to review the issue and any recorded decision. If the planned window passes without the release, mark the window Missed and write the reason in notes.

For the missed window, check the issue owner and the package’s remaining tasks before setting a new date. The project manager records the missed outcome on the original window so its history remains understandable at the next delivery meeting.

At the next delivery meeting, revisit the missed window beside the package status. The owner can update a new plan after the team agrees which issue or task needs attention first.

• Deployment Windows At Risk — Review pending and missed windows with their owners and due dates.
• Active Projects — Open the linked project to check its schedule and owner.

See plan and delivery, issue triage and release window review for the steps around this work.