Delivery Lead / Scrum Master

The Onshore Delivery Lead / Scrum Master is accountable for day-to-day delivery leadership for the Integration Platform Engineering team. This role connects product priorities to executable team plans, coordinates onshore and offshore contributors, manages cross-team dependencies, and provides clear visibility into progress, risks, decisions, and release readiness. The role is embedded with IPE and is expected to operate with confidence in a fast-paced platform engineering environment while preserving clear boundaries between product ownership, technical ownership, people leadership, and delivery facilitation.

Key Responsibilities

Stakeholder and Delivery Leadership

·                     Serve as the primary delivery interface between IPE engineering, Product Ownership, the Portfolio/Program team, and dependent onshore teams.

·                     Translate delivery status, risks, dependencies, tradeoffs, and decisions into concise, outcome-focused updates for leadership and stakeholders.

·                     Lead cross-functional coordination with Infrastructure, DevSecOps, Security, QA, application teams, and other platform partners.

·                     Drive timely decisions and escalate unresolved constraints with clear impact and recommended options.

Planning and Team Execution

·                     Facilitate sprint planning, daily standups, backlog refinement, reviews, retrospectives, and release-readiness discussions.

·                     Partner with the Product Owner and engineering leads to ensure priorities, features, stories, acceptance criteria, dependencies, and technical tasks are ready before commitment.

·                     Maintain the integrated delivery plan, milestones, capacity view, release dates, and dependency sequencing across onshore and offshore contributors.

·                     Protect sprint goals by controlling unplanned work, clarifying scope changes, and ensuring decisions are reflected in Jira.

Risk, Dependency, and Release Management

·                     Identify blockers and delivery risks early; coordinate owners, due dates, mitigation actions, and escalation paths.

·                     Ensure external dependencies, environments, approvals, security reviews, infrastructure requests, QA activities, and change records are planned early enough to support delivery.

·                     Coordinate release readiness, demonstrations, stakeholder acceptance, production change activities, and closure of delivery actions.

Delivery Transparency and Improvement

·                     Maintain accurate Jira boards, releases, dashboards, RAID information, and leadership reporting that reflect the true state of delivery.

·                     Monitor capacity, throughput, cycle time, work-item age, carryover, blocked work, and commitment reliability to identify improvement opportunities.

·                     Coach the team toward clear ownership, appropriately sized work, sustainable pace, and continuous improvement.

Onshore/Offshore Partnership

·                     Create a single delivery cadence and shared source of truth across time zones.

·                     Provide clear priorities, decisions, dependency updates, and stakeholder context to the Offshore Delivery Lead.

·                     Conduct structured handoffs and ensure offshore escalations receive timely onshore resolution.

Role Boundaries

·                     Does not own product strategy, roadmap priorities, business requirements, or acceptance decisions; partners with the Product Owner to make work ready for execution.

·                     Does not make technical architecture, engineering-design, or people-management decisions; ensures the accountable owners make and document those decisions.

·                     Does not perform engineers’ status updates or move work on their behalf as a standard practice; establishes transparency and reinforces team ownership.

·                     Escalates unresolved cross-team, capacity, scope, and decision constraints with facts, impact, options, and a recommended path forward.

Required Qualifications

·                    10+ years of experience as a Scrum Master, Delivery Lead, Technical Project Manager, or similar role supporting engineering teams.

·                     Demonstrated experience facilitating Scrum ceremonies and managing Agile delivery in Jira or Azure DevOps.

·                     Strong backlog, dependency, risk, issue, milestone, and release-management skills.

·                     Ability to work effectively with product owners, engineers, architects, QA, infrastructure, security, DevSecOps, and leadership.

·                     Clear, concise written and verbal communication; able to facilitate difficult conversations and drive follow-through without direct authority.

·                     Working knowledge of APIs, integration services, microservices, cloud platforms, CI/CD, DevSecOps, or platform engineering.

Preferred Qualifications

·                     Certified ScrumMaster (CSM), Professional Scrum Master (PSM), SAFe Scrum Master, or comparable Agile certification.

·                     Experience in a large, regulated enterprise or healthcare technology environment.

·                     Experience supporting API management, event streaming or messaging, identity services, cloud infrastructure, or developer-platform capabilities.

·                     Advanced Jira, Confluence, dashboard, query, and reporting skills.