Agile Delivery Lead

Craftware Sp. z o.o.; Poland; Remote; PLN 90,000 - 130,000; Full time

Job summary

Craftware Sp. z o.o. in Poland is seeking an experienced Delivery Manager to streamline multi-team, multi-vendor delivery efforts across DORIS and related streams.

You will map current ways of working, resolve ownership conflicts, and establish a sustainable delivery cadence using Azure DevOps or Jira. The role demands hands-on leadership, strong stakeholder facilitation, and a track record of end-to-end transformation.

Qualifications

• Proven experience as a Delivery Manager, Agile Delivery Lead, Agile Coach or similar in a multi-team, multi-vendor enterprise environment.
• Track record of designing and implementing ways of working, not just running an existing process — including at least one end-to-end transformation you personally led.
• Strong command of agile delivery mechanics: backlog design, estimation and story points, sprint cadence, refinement, retrospectives, flow metrics.
• Hands-on experience with Azure DevOps (ADO) or an equivalent tool (Jira), including backlog architecture, work-item hierarchy, boards, queries and reporting.
• Experience balancing BAU/run work against project and initiative delivery in one capacity pool.
• Demonstrated ability to prioritise across competing stakeholders and to make allocation decisions stick.
• Outcome-oriented planning experience — OKRs, quarterly or 90-day planning cycles, and connecting delivery to business results.
• Excellent stakeholder management and facilitation skills at IT management level.
• Fluent English, written and spoken (working language of the project).

Responsibilities

• Map the current ways of working across all teams, vendors and delivery areas.
• Identify overlaps, bottlenecks and unclear ownership between the core DORIS team and the parallel streams (VEP, DAAAI, Veeva Professional Services).
• Present findings and a prioritised improvement roadmap to Governance and stakeholders
• Define how business-as-usual work and project work coexist in one delivery system.
• Decide and implement the backlog structure in ADO/VDO (Jira-class tooling): one backlog or several, how work is classified, how it flows, what the definition of ready and done looks like.
• Establish a prioritisation framework that works across competing demand from Veeva-mandated releases, business releases, on-demand interface requests and strategic initiatives.
• Design capacity and people-allocation models that prevent priority clashes and over-commitment of shared specialists.
• Re-establish delivery fundamentals where they have lapsed: sprint cadence, estimation and story points, refinement, sprint planning, review.
• Introduce planning in 90-day cycles and connect delivery activity to measurable business outcomes rather than output.
• Run and improve retrospectives so that they generate real, tracked change.
• Work side by side with Unit Lead, Squad Leads, BAs and vendor teams — coaching in the flow of work, not from a slide deck.
• Document the target operating model, cadences, roles and metrics.
• Build the capability in the existing leadership layer so the system keeps running without you.
• Experience in pharma, life sciences or another regulated industry.
• Familiarity with GxP, CSV and GAMP 5 validation processes and their impact on delivery cadence.
• Exposure to Veeva Vault (RIM, Submissions, Publishing) or comparable regulatory/document management platforms.
• Experience working with platform-vendor release calendars and external implementation partners.
• Background in data/interface delivery (database views, integrations with satellite systems).
• Experience introducing automation or AI capabilities into an existing delivery landscape.

Job description

• Map the current ways of working across all teams, vendors and delivery areas.
• Identify overlaps, bottlenecks, priority conflicts and unclear ownership between the core DORIS team and the parallel streams (VEP, DAAAI, Veeva Professional Services).
• Present findings and a prioritised improvement roadmap to Governance and stakeholders
• Define how business-as-usual work and project work coexist in one delivery system.
• Decide and implement the backlog structure in ADO/VDO (Jira-class tooling): one backlog or several, how work is classified, how it flows, what the definition of ready and done looks like.
• Establish a prioritisation framework that works across competing demand from Veeva-mandated releases, business releases, on-demand interface requests and strategic initiatives.
• Design capacity and people-allocation models that prevent priority clashes and over-commitment of shared specialists.
• Re-establish delivery fundamentals where they have lapsed: sprint cadence, estimation and story points, refinement, sprint planning, review.
• Introduce planning in 90-day cycles and connect delivery activity to measurable business outcomes rather than output.
• Run and improve retrospectives so that they generate real, tracked change.
• Work side by side with Unit Lead, Squad Leads, BAs and vendor teams — coaching in the flow of work, not from a slide deck.
• Document the target operating model, cadences, roles and metrics.
• Build the capability in the existing leadership layer so the system keeps running without you.

Requirements:

• Proven experience as a Delivery Manager, Agile Delivery Lead, Agile Coach or similar in a multi-team, multi-vendor enterprise environment.
• Track record of designing and implementing ways of working, not just running an existing process — including at least one end-to-end transformation you personally led.
• Strong command of agile delivery mechanics: backlog design, estimation and story points, sprint cadence, refinement, retrospectives, flow metrics.
• Hands-on experience with Azure DevOps (ADO) or an equivalent tool (Jira), including backlog architecture, work-item hierarchy, boards, queries and reporting.
• Experience balancing BAU/run work against project and initiative delivery in one capacity pool.
• Demonstrated ability to prioritise across competing stakeholders and to make allocation decisions stick.
• Outcome-oriented planning experience — OKRs, quarterly or 90-day planning cycles, and connecting delivery to business results.
• Excellent stakeholder management and facilitation skills at IT management level.
• Fluent English, written and spoken (working language of the project).

Nice to have

• Experience in pharma, life sciences or another regulated industry.
• Familiarity with GxP, CSV and GAMP 5 validation processes and their impact on delivery cadence.
• Exposure to Veeva Vault (RIM, Submissions, Publishing) or comparable regulatory/document management platforms.
• Experience working with platform-vendor release calendars and external implementation partners.
• Background in data/interface delivery (database views, integrations with satellite systems).
• Experience introducing automation or AI capabilities into an existing delivery landscape.