manager

Strategic responsibilities

1. Translate portfolio priorities into executable delivery plans that align roadmaps, capacity, and dependencies across multiple teams and value streams.
2. Set delivery strategy and operating cadence for programs (increment planning, release trains, governance checkpoints) appropriate to the company’s SDLC and risk profile.
3. Establish delivery success criteria (OKRs, release outcomes, acceptance, readiness) with Product, Engineering, and business stakeholders.
4. Drive continuous improvement using delivery analytics (flow metrics, throughput, cycle time, defect trends) to remove systemic constraints.

Operational responsibilities

1. Own integrated delivery plans (scope, milestones, RAID logs, resource plans) across multiple squads/teams and vendors as needed.
2. Run core delivery rituals (planning, sprint/release reviews, cross-team syncs, milestone checkpoints, readiness reviews).
3. Actively manage dependencies across engineering teams, platform/infra, security, data, and external providers—ensuring clear owners and due dates.
4. Monitor execution health (burndown/burnup, flow metrics, blocked work, environment readiness) and intervene early to prevent slippage.
5. Lead risk and issue management with structured escalation, mitigation plans, and decision logs; maintain governance artifacts suitable for audits when required.
6. Coordinate release management activities (release calendars, freeze windows, cutover planning, go/no-go) in partnership with DevOps/SRE and Product.
7. Ensure delivery readiness (documentation, training, support readiness, runbooks, monitoring, rollback plans) prior to launch.
8. Manage vendors/third parties when in scope: delivery commitments, contractual milestones, progress reporting, and integration into internal ways of working.

Technical responsibilities (delivery-technical, not hands-on coding)

1. Facilitate technical planning and sequencing with architects/tech leads, ensuring work is decomposed, estimable, and appropriately staged (MVP, phased rollout).
2. Partner with Engineering and QA to ensure test strategies, quality gates, and non-functional requirements (performance, security, reliability) are embedded in plans.
3. Support DevOps enablement by aligning delivery plans with CI/CD, environment provisioning, feature flagging, and deployment automation needs.
4. Promote operational excellence practices (observability readiness, incident learnings, SLO/SLA alignment) for production-bound changes.