Transforming Release Management Through Cross-Functional Ownership

At Huawei, I initially joined to support bug fixing activities. Over time, recurring release failures revealed deeper process issues.

Release scope was often unclear due to the lack of a single source of truth for what had actually changed since the previous production deployment. Teams had different assumptions about which features, bug fixes, and contributors were included in upcoming releases, increasing the risk of incomplete validation and post-release defects.

• Multiple teams participated in releases.
• No dedicated release owner existed.
• Customer timelines remained fixed.
• Existing processes had become normalized despite poor outcomes.

Built a lightweight internal script to analyze the source control history and automatically generate release candidate reports. The report identified all merge requests opened since the previous production release, including ownership, change summaries, and affected areas.

Used these reports to facilitate cross-functional release planning sessions with Product Managers, Engineering Managers, Business Analysts, and QA teams, aligning stakeholders on release scope, test coverage, deployment sequencing, and post-release validation activities.

The role increased operational responsibilities beyond my original scope. It required balancing development activities with release coordination.

Recognized that release failures were often caused by unclear ownership and inconsistent understanding of release scope rather than technical defects alone. Introduced a data-driven release reporting process that transformed repository activity into actionable release plans, enabling stakeholders across engineering, QA, and business functions to align before deployment.

Ownership means solving the problem that exists, not the one described in your job title.