Agile Delivery Lead​/Consultant

We are not looking for a facilitator; we are looking for a Delivery Engine. You will be the primary person accountable for ensuring that software moves from the backlog to production predictably and at high quality. You must be an expert in Azure Dev Ops (ADO), using data to navigate complex dependencies and drive outcomes in a fast-paced, regulated environment.

• End-to-End Delivery Ownership: Manage the full SDLC lifecycle, ensuring teams meet release milestones and business commitments.
• Azure Dev Ops Power User: Architect and maintain ADO boards, queries, and delivery plans. Use ADO data to create automated reporting for leadership on team health and progress.
• Metric-Driven Leadership: Beyond simple velocity, you will own and improve Cycle Time, Lead Time, and Flow Efficiency. You must be able to diagnose a bottleneck through data before it impacts a deadline.
• Dependency &
  
  Risk Management:
  
  Proactively identify and resolve cross-team technical dependencies and architectural blockers.
• Stakeholder Navigation: Present clear trade-offs (Scope vs. Time vs. Quality) to Product and Engineering leadership to facilitate rapid decision-making.

• 5+ Years of Hands-on Delivery: Proven track record as a Delivery Lead or Technical Project Manager in a high-growth or modernized tech stack.
• Advanced ADO/Jira Expertise: Must be able to demonstrate (not just mention) how you use these tools for day-to-day delivery tracking, capacity planning, and dependency mapping.
• Technical Literacy: Ability to "speak engineer." You should understand CI/CD pipelines, automated testing requirements, and the impact of technical debt on delivery speed.
• Outcome Focus: Experience delivering complex initiatives in regulated industries (e.g., Insurance, Fintech) where "Done" includes compliance and security.

• Pure Coaches: If your primary focus is teaching Agile theory rather than shipping code, this is not the right fit.
• Passive Facilitators: We need leaders who lean into conflict, resolve blockers aggressively, and hold teams accountable to their commitments.
• Manual Reporters: If you rely on manual spreadsheets instead of leveraging Azure Dev Ops automated insights, you will struggle in this environment.