Skip to main content

Release Owner

The release owners play an active role in managing release-related activities across all organizational functions within PCP. They ensure that release planning is both realistic and aligned with the program increments (PIs). These release plans are developed based on input from product management, architects, stream owners, and other key stakeholders throughout the PCP organization.

Description​

The release owner collaborates with other release owners to create a consistent release plan for a stream. This plan includes targeted dates for key milestones, deliverables, demos, and releases. Targets are re-estimated for future increments but committed if they fall within the current increment. Major changes in the release plans are communicated to key stakeholders across PCP to ensure they can adjust their plans accordingly.

The release owner synchronizes progress by gathering input from teams and managing dependencies across other streams and organizational functions. Actions are taken to remove impediments (such as blocked features due to uncertainties or conflicting dependencies) and mitigate risks.

As part of their responsibilities, the release owner ensures that stream backlogs include necessary release activities (such as DSAC, OSS, and user manuals). Additionally, they initiate and plan the work required to meet ABB guidelines and external standards (including OSS, Cyber Security, Safety, and RoHS).

The release owner ensures that the milestone tracker is fulfilled and assists the gate assessor in preparing assessment reports. Additionally, they report progress, status, risks, and issues to the steering committee to address any deviations or impediments.

Responsibilities​

  • Drive integrated planning and execution across organizational functions, including Portfolio and Product Management (PPM), Program Management Office (PMO), R&D, and Operations.
  • Collaborate with other release owners to manage cross-stream dependencies.
  • Ensure regular and transparent communication and status updates to the steering committee (SteCo) and other stakeholders.
  • Align plans with SteCo objectives and decisions.
  • Assess, escalate, and take action on critical risks and issues.
  • Ensure compliance with ABB policies and external standards, such as the gate model, security protocols, and OSS requirements.
  • Ensure milestone readiness and initiate gate assessments with the gate owner.
  • Capture lessons learned at milestones and gates, and implement improvement actions.
  • Ensure quality goals are defined and achieved