Delivery Manager- Remote

 *We are open to supporting 100% remote work anywhere within the US*

The Delivery Manager will be the execution lead responsible for driving consistent, high-quality delivery across Agile teams. This role focuses on ensuring that delivery commitments are met, product and engineering expectations are aligned, and team performance is visible, measurable, and continually improving. 

With a focus on data-informed execution, the Delivery Manager owns delivery performance and quality accountability across the multiple teams—ensuring sprint goals are achievable, risk is proactively managed, and the program is operating with clarity and confidence. This is a delivery-focused leadership position responsible for connecting development activity to measurable outcomes and reporting internal ART health. 

Key Responsibilities:

Delivery Execution & Coordination 

• Align closely with product and technical leadership to ensure scope is delivery-ready and priorities are clear. 

• Monitor execution against PI commitments, ensure consistent Jira workflows to report on delivery cadence and quality as needed. 

• Provide internal coordination and continuity across teams. 

Metrics, Reporting & Visibility 

• Define and maintain delivery performance metrics across teams, including: 

• Velocity and sprint throughput 

• Feature delivery vs. PI commitments 

• Bug trends: found in production, introduced by releases, or caught in lower environments 

• Production support volume (Tier1, Tier 2, Tier 3 tickets) 

• Defect resolution timelines and burndown 

• Build internal dashboards and reporting structures to surface trends and delivery risks, and communicate those trends clearly to program leadership and customer stakeholders. 

Quality & Support Alignment 

• Track delivery-related quality metrics that reflect engineering health over time—such as defect escape rates, bugs introduced per release, mean time to resolution, and reopened defect trends. 

• Analyze post-launch behavior to identify quality breakdowns tied to delivery—like issues stemming from unclear requirements, insufficient test coverage, or unstable code paths that lead to increased support volume. 

• Incorporate production and support issue trends into delivery planning to ensure that recurring quality gaps inform future sprint priorities and engineering practices. 

Launch & Hypercare Support 

• Coordinate readiness efforts for all releases, including cutover planning, pre-launch quality checks, and internal sign-offs. 

• Establish post-launch hypercare expectations and ensure active monitoring of production issues. 

• Report on release impact, success metrics, and any corrective actions needed to improve future delivery cycles. 

Governance & Process Improvement 

• Establish internal delivery governance practices, backlog readiness expectations, and definitions of done. 

• Identify and respond to patterns in blockers, scope churn, or quality gaps across teams. 

• Support onboarding of new team members and help operationalize delivery processes as the program scales. 

Near-Term Focus (First 90 Days) 

• Stabilize sprint execution across key delivery areas (e.g., Framework, Analytics, Innovation).