Delivery Manager / Technical Program Manager (TPM)

Overview

Role Overview

Core Responsibilities

• **Program Execution:**
• Lead the planning and end-to-end execution of complex technical roadmaps.
• Drive the release process and ensure milestones are met across various workstreams.
• **Agile Governance:**
• Facilitate Scrum or Kanban ceremonies (Sprint Planning, Stand-ups, Retrospectives).
• Optimize the "Definition of Ready" and "Definition of Done" to ensure team efficiency.
• **Stakeholder Management:**
• Act as the primary point of contact for Product, Engineering, and Business leaders.
• Translate technical complexities into clear status updates and risk assessments.
• **Dependency & Risk Mitigation:**
• Proactively identify "blockers" before they stall progress.
• Manage cross-team dependencies (e.g., API availability, DevOps infrastructure, or Security audits).
• **Metrics & Reporting:**
• Track and report on key performance indicators (KPIs) such as

Velocity

Cycle Time

Lead Time

Burn-down

• rates to drive data-driven improvements.
• **Technical Advocacy:**
• Participate in architectural discussions to understand technical debt and trade-offs, ensuring that delivery timelines remain realistic and sustainable.

Required Skills & Qualifications

• 5+ years in Technical Project/Program Management or Software Engineering leadership.
• Deep expertise in

Agile, Scrum, and Lean

• frameworks.
• PMP or CSM certifications are a plus.
• Ability to understand system design, APIs, and CI/CD pipelines. You don't need to code, but you must "speak engineer."
• Mastery of

Jira, Confluence

• , Linear, or Azure DevOps for tracking and documentation.
• Exceptional conflict resolution, negotiation, and the ability to influence without formal authority.

What Success Looks Like

• **Predictability:**
• The team consistently meets sprint goals and release dates.
• **Transparency:**
• Stakeholders are never surprised by a delay; risks are communicated early with proposed solutions.
• **Quality:**
• High-velocity delivery is achieved without a corresponding spike in production bugs or technical debt.