Skip to content

Insufficient Protection of Delivery Phases Impacting SRE Operations

The Lesson

Delivery activities that impact an existing SRE-managed platform must be planned, resourced and governed in a way that protects ongoing operational responsibilities.

SRE exists to operate and improve production services. It is not an extension of delivery teams and should not become a substitute for insufficient delivery capacity.

When new delivery phases occur on platforms already under SRE ownership, there must be a clear separation between delivery responsibilities and operational responsibilities.

Delivery teams must remain accountable for delivering new features, completing project activities and preparing changes for production.

SRE should support the operational transition of these changes, but should not be required to absorb delivery responsibilities because a delivery phase has been inadequately planned or resourced.

When delivery phases are not properly protected, SRE teams can be pulled away from operational responsibilities, resulting in increased maintenance backlog, reduced reliability improvement activity and a shift towards reactive ways of working.

The Problem

A recurring challenge occurs when delivery activity continues on platforms already supported by SRE without sufficient planning, ownership or resource protection.

An example of this pattern is where an additional phase of development is initiated on an existing production platform, but the delivery team is not adequately resourced to complete the work before their engagement ends.

The delivery phase then reaches a critical point where:

  • Delivery timelines are incomplete.
  • Production readiness activities are unfinished.
  • Delivery teams are preparing to roll off.
  • SRE is expected to help complete outstanding delivery activities.

This creates an unacceptable transfer of delivery responsibility into an operational team.

Delivery Teams Rolling Off Before Completion

A delivery team should not roll off a project while significant delivery responsibilities remain incomplete.

When delivery teams leave before a new phase reaches production readiness, SRE can become the default owner of unresolved delivery activity.

This creates several problems:

  • SRE inherits incomplete work without the original context.
  • Operational engineers must spend time understanding delivery requirements.
  • Existing operational commitments are deprioritised.
  • Accountability becomes unclear.
  • Delivery risks become operational risks.

The transition point between delivery and operations must represent a clear ownership boundary.

SRE ownership does not mean accepting unfinished delivery work.

Under-Resourced Delivery Creates Operational Impact

Delivery phases must be appropriately resourced based on the scope and complexity of the work.

When delivery teams are under-resourced, operational teams often experience the impact.

Examples include:

  • SRE engineers being asked to assist with development activities.
  • SRE involvement in testing or delivery coordination.
  • Operational work being delayed.
  • Maintenance tasks accumulating.
  • Reliability improvements being postponed.

This creates a situation where SRE is unable to focus on its primary responsibility because capacity is being redirected towards completing delivery activities.

The impact is often not immediately visible. The delivery phase may appear to progress, but the operational cost is transferred into SRE.

SRE Becoming an Unplanned Extension of Delivery

SRE engineers may have strong technical knowledge of the platform, which can make them appear to be a natural resource to help delivery teams.

However, this creates a significant risk.

SRE involvement in delivery should be intentional and planned. It should not become an unmanaged expectation.

Examples of inappropriate SRE responsibilities include:

  • Completing unfinished development work.
  • Taking ownership of delivery tasks.
  • Coordinating project completion activities.
  • Acting as replacement delivery engineers.
  • Resolving delivery resource gaps.

When SRE becomes responsible for completing delivery activity, the operational model breaks down.

The team is no longer focused on reliability engineering and service operation.

Increased Reactive Operational Pressure

When SRE capacity is consumed by delivery activities, normal operational responsibilities begin to accumulate.

This can include:

  • Maintenance activities.
  • Technical debt reduction.
  • Automation.
  • Platform improvements.
  • Documentation updates.
  • Reliability work.

Once operational backlog increases, teams often enter a reactive cycle.

Engineers become focused on catching up rather than improving the platform.

This reinforces the same reactive operating pattern described in:

Loss of Clear Ownership and Accountability

A successful managed service depends on clear ownership boundaries.

Delivery teams are responsible for delivering changes.

SRE is responsible for operating the service.

When these boundaries become unclear, several risks emerge:

  • Issues are difficult to assign.
  • Delivery delays become operational concerns.
  • SRE accountability expands beyond the agreed service.
  • Clients may receive unclear messages about ownership.

Clear responsibility boundaries protect both delivery and SRE teams.

The Solution

Delivery phases that affect SRE-managed platforms must be planned with clear ownership, sufficient resources and appropriate transition processes.

SRE involvement should be expected and structured, but SRE should not become responsible for completing delivery work.

Maintain Clear Separation Between Delivery and Operations

Delivery and operations should remain separate responsibilities.

Delivery teams should own:

  • Feature development.
  • Implementation activities.
  • Testing.
  • Delivery timelines.
  • Release preparation.
  • Completion of project commitments.

SRE should own:

  • Production operation.
  • Reliability.
  • Monitoring.
  • Incident response.
  • Operational improvement.
  • Service management.

Where collaboration is required, responsibilities should be explicitly defined.

Include SRE in Delivery Planning Early

When a new delivery phase affects an existing SRE-managed platform, SRE should be involved during planning.

This allows teams to understand:

  • Expected operational impact.
  • Required SRE involvement.
  • Transition requirements.
  • Support considerations.
  • Resource needs.

Early involvement prevents last-minute expectations being placed on SRE.

Protect SRE Capacity

SRE capacity allocated to operational responsibilities must be protected.

If SRE involvement in delivery activities is required, this should be:

  • Planned in advance.
  • Explicitly agreed.
  • Properly resourced.
  • Included within service expectations.

Unplanned diversion of SRE capacity creates operational risk.

Ensure Delivery Teams Remain Until Completion

Delivery teams should remain accountable until agreed delivery outcomes are achieved.

This includes:

  • Completing development activities.
  • Completing testing.
  • Addressing delivery defects.
  • Supporting production transition.
  • Completing knowledge transfer.

A delivery team should not roll off simply because a project phase reaches its scheduled end date if critical responsibilities remain incomplete.

Establish Clear Transition Criteria

Before delivery responsibility transitions away, the following should be confirmed:

  • Features are complete.
  • Testing is complete.
  • Production readiness activities are complete.
  • Documentation is updated.
  • Knowledge transfer has occurred.
  • SRE understands operational impact.
  • Ownership boundaries are agreed.

Transition should represent a controlled handover, not an abandonment point.

Define Planned SRE Engagement During Delivery

There are situations where SRE involvement during delivery is appropriate.

Examples include:

  • Providing operational guidance.
  • Reviewing production readiness.
  • Supporting deployment planning.
  • Validating monitoring requirements.

However, this involvement should be planned and capacity-managed.

SRE support during delivery should be a defined activity, not an assumption.

Include Delivery Protection Within Service Governance

Service governance should include checks to prevent delivery activities from negatively impacting operations.

Considerations should include:

  • Delivery resource allocation.
  • Impact assessments.
  • Transition planning.
  • SRE capacity impact.
  • Production readiness status.
  • Ownership confirmation.

This provides visibility before delivery risks become operational problems.

Summary

SRE cannot operate effectively when it becomes the fallback resource for incomplete delivery activity.

Delivery teams and SRE teams have different responsibilities. Collaboration between them is essential, but responsibility boundaries must remain clear.

A successful delivery phase should leave SRE with a production-ready platform and the knowledge required to operate it.

It should not leave SRE responsible for completing unfinished project work.

Protecting delivery phases protects SRE capacity, improves operational reliability and enables teams to scale effectively.