Grandview Solutions

Release Manager — Multishoring Delivery Team

Embedded with Customer LightSpeed

Role Overview

The Release Manager provides end-to-end release coordination for work delivered by the Multishoring team to Customer LightSpeed. This role owns release readiness, scheduling, traceability, stakeholder communication, production incident coordination, and delivery reporting. The Release Manager serves as the go/no-go decision point for each Keystone Release while partnering closely with Customer Platform Engineering on pipeline and infrastructure activities.

Reports to: Multishoring Engagement Lead, with a coordination line to Customer Project Management and Platform Engineering.

Key Responsibilities

• Manage release planning. Own the release calendar and maintain clear sprint-to-release mapping for Multishoring-delivered work.
• Track release candidates. Maintain an accurate view of which Product Backlog Items (PBIs) and pull requests (PRs) are ready for release consideration.
• Gate release readiness. Confirm that builds are green, required testing is complete, at least one approval is recorded, review comments are resolved, Sonar checks are clean, and Azure DevOps (ADO) work-item traceability is in place before work is proposed for release.
• Enforce traceability and process standards. Ensure the appropriate work-item ID appears in branches, commits, and PRs, and reinforce agreed naming and delivery conventions across the Multishoring team.
• Coordinate release branches. Own the cut and merge of the release branch into master for each Keystone Release, coordinating timing and dependencies with Customer stakeholders.
• Lead release decisions and communications. Serve as the single point of contact for go-live, hold, and rollback decisions, and communicate status, risks, and outcomes to Customer stakeholders.
• Coordinate production incidents. When a release causes a production issue, organize the response, recommend whether to roll back, and coordinate ownership of investigation and reversion activities rather than performing the technical fix.
• Report delivery status. Prepare sprint and release notes and reconcile delivered work against timesheets and ADO records to support Customer reporting and delivery audits.

Operating Boundaries

The Release Manager coordinates and governs the release process but does not unilaterally trigger ADO pipeline runs or modify variable groups, service connections, or other infrastructure-related settings. These higher-risk actions remain the responsibility of Customer Platform Engineering.

Success in This Role

• Release candidates are clearly tracked, fully traceable, and ready at the agreed sprint boundary.
• Release decisions are timely, evidence-based, and clearly communicated.
• Production incidents have defined coordination, ownership, and rollback paths.
• Release notes, ADO records, and timesheet reporting remain accurate and reconcilable.