Agile Delivery Manager → VP Technology

A realistic transition from Agile Delivery Manager to VP Technology: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 23%. Difficulty: Hard.

Difficulty: Hard6 stepsDuration: 16 to 20 monthsOverlap: 23%

Transition from Agile Delivery Manager to VP Technology.

Transferable skills

  • Stakeholder management
  • Team development

Skills to learn

  • Technology leadership
  • Strategy
  • Architecture & platforms
  • Innovation
  • Budget
  • Mentoring

Step-by-step learning plan

  1. 1. Build on your Agile Delivery Manager experience

    2–4 weeks

    Leverage

    • Stakeholder management
    • Team development

    Map transferable skills — Stakeholder management, Team development — against what a VP Technology needs.

  2. 2. Learn the core of the VP Technology role

    6–10 weeks

    Learn

    • Technology leadership
    • Strategy
    • Budget

    Technologies

    AWSAzureGCP

    Cover the biggest gaps first: Technology leadership, Strategy, Budget.

  3. 3. Master advanced VP Technology skills

    6–10 weeks

    Learn

    • Architecture & platforms
    • Innovation
    • Mentoring

    Technologies

    KubernetesTerraformServiceNow

    Handle the advanced topics: Architecture & platforms, Innovation, Mentoring.

  4. 4. Get productive with the VP Technology toolchain

    4–8 weeks

    Technologies

    AWSAzureGCPKubernetesTerraformServiceNow

    Be hands-on with AWS, Azure, GCP and the rest of the target stack.

  5. 5. Practise VP Technology work in real conditions

    4–8 weeks

    Ship a portfolio project or take on VP Technology tasks at work.

  6. 6. Get certified and position yourself as a VP Technology

    4–8 weeks

    Technologies

    TOGAF 9 CertifiedSAFe Program ConsultantCISM

    Update your CV and LinkedIn around VP Technology, then apply to target roles.

Alternative routes