6.3Transition to service management

Even once a project finishes its deliverable, the project's value is not realized unless it can be safely released into production and smoothly handed off to ongoing operations and maintenance. A PM must judge whether to proceed with production transition (go/no-go) based not just on how complete development is, but on the operations side's readiness and risk as well. The judgment criteria are built starting from the impact on users and operators once the thing runs as a live service, not from the convenience of the development side.

6.3.1Production transition and the go/no-go decision

• Production transition (release) is the activity of deploying a deliverable built in a development/test environment into the production environment actual users will use. It is more than a deployment step—it is planned to include rollback procedures, an assessment of the scope of impact during the transition, and the monitoring setup after the transition.
• Go/no-go decision: the gate at which the organization formally decides whether to proceed with the planned production transition or postpone it, judged against predetermined criteria—acceptance test pass status, absence of unresolved critical defects, readiness of rollback procedures, readiness of the operations organization, and so on. Beyond technical completeness, the criteria also include the appropriateness of the transition timing (e.g., avoiding a peak business period) and the readiness of the operations handoff.

6.3.2SLA and the ITIL perspective

• SLA (Service Level Agreement) is the level of service quality agreed between the service provider and the user—numeric targets for availability, response time, incident recovery time, and the like. Before a project's deliverable moves into production, it must be verified whether the operations and monitoring setup can meet the level the SLA requires.
• ITIL (IT Infrastructure Library) is a best-practice framework for IT service management, providing the lifecycle perspective of service strategy, design, transition, operation, and improvement. From a project's viewpoint, the service transition area is especially relevant: change management, release management, and handing over known-issue information (e.g., a known error database) to reliably carry the development side's knowledge over to the operations side.

Suppose a PM is heading into the go/no-go decision meeting for a large-scale core-system overhaul project. The development team reports that "all acceptance test items passed, and there are zero unresolved critical defects," and pushes to proceed with the transition as scheduled. But when the PM checks with the operations team, it turns out that the new system's monitoring dashboard is not yet fully configured, and operations staff are not set up to meet the SLA's recovery-time target (e.g., detecting a critical incident within one hour) if a failure occurs. On top of that, the planned transition date turns out to fall during an internal peak period that coincides with financial closing. Rather than jumping to "all tests passed, so we can proceed" the PM returns to the principle that go/no-go criteria include operations readiness to receive the handoff, not just technical completeness, and judges this decision to be no-go (postpone). As corrective action, the PM has three things done before revisiting the decision: (1) finish configuring the monitoring dashboard and complete operator training, (2) reschedule the transition date to avoid the peak period, and (3) following ITIL's service-transition thinking, formally document and hand over to operations, as known-error information, the minor known issues and operational cautions the development team is aware of. In this way, the timing at which development considers something "done" does not necessarily match the timing at which operations can "safely take it on," and the PM plays the role of reconciling that gap, starting from the SLA as the promise made to users.

6.3.3Section summary

• Production transition (release) is planned to include rollback procedures, impact scope, and post-transition monitoring
• The go/no-go decision is a gate that judges based on operations readiness, timing, and knowledge handoff, not just technical completeness
• The SLA is the agreed level for the operations phase and must be checked for feasibility before transition; ITIL's service transition is the activity of handing development knowledge over to operations