Skip to content
  • Start any day: Day 1 opens when you enrol
  • 1–2 hrs a day, in your own time
  • Reviewed work and interview prep
  • Individual feedback every week
KLYMB.AI
Log in
Career track 03This job is changing

Project Manager, becoming AI Delivery Lead

Planning, requirements, execution, risk management, stakeholder communication and reporting.

Choose this trackSee the 30 days
AI skillsRAGAI agentsLLMOpsEvalsAI safetyGuardrails
A hand arranging cards on a project planning board
days
30days
checkpoints
4checkpoints
interview-prep days
2interview-prep days

What's changing in this role

Status reports, plan updates and meeting notes are increasingly generated by tools. What remains valuable is scoping, decisions, accountability and designing how AI fits into delivery.

What you carry over

  • + Stakeholder judgment
  • + Knowing how your organisation actually decides
  • + Delivery accountability

Who it is for

Built for people like you.

  • Coordinators and team leads
  • Business analysts moving into delivery
  • Professionals switching into project management

Skills covered

What you will practise.

  • Planning
  • Requirements
  • Agile and Scrum
  • Risk management
  • Stakeholder communication
  • Status reporting
  • AI-assisted delivery
A team gathered around a laptop, talking through a piece of work

30-day overview

Every day, planned.

Four weekly phases of daily problems, an assessment after each week, and interview prep on Days 29–30. Open a week to see every day.

Enroll now
Week 1Days 1–7FoundationsDelivery foundationsThe core of delivery, and an honest audit of what tools now do without you.
  1. Day 1Project charter: Write a one-page charter for a new internal tool.
  2. Day 2Requirements from a messy brief: Turn a rambling stakeholder email into clear requirements.
  3. Day 3Work breakdown: Break a project into a WBS and milestones.
  4. Day 4Agile vs. waterfall decision: Choose a delivery approach for three projects and justify it.
  5. Day 5Stakeholder map: Map stakeholders by influence and interest.
  6. Day 6What automation already does: Audit a PM's week against today's tooling.
  7. Day 7Checkpoint: Process auditMap one real delivery process against today's tooling and identify what should change.Practical task + short written reasoning, scored against a rubric
Week 2Days 8–14Practical executionPlanning and scoping AI-native workEstimates, backlogs and review loops when AI drafts the first version.
  1. Day 8Estimation: Estimate a backlog using story points and explain your assumptions.
  2. Day 9Sprint planning: Plan a two-week sprint with a capacity constraint.
  3. Day 10Writing user stories: Write stories with acceptance criteria for a feature.
  4. Day 11Timeline and dependencies: Build a timeline and identify the critical path.
  5. Day 12AI in the loop: Re-estimate work when an agent drafts code or content.
  6. Day 13Status report that gets read: Write a one-page RAG status update.
  7. Day 14Checkpoint: Re-estimateRe-estimate a live project with AI in the loop and explain the changes.Practical task + short written reasoning, scored against a rubric
Week 3Days 15–21Real-world problem solvingRisk, change and stakeholdersThe judgment calls: risk, scope change, conflict and human-in-the-loop design.
  1. Day 15Risk register: Identify, score and plan responses for ten risks.
  2. Day 16Scope change request: Handle a late scope change without losing the date.
  3. Day 17Difficult stakeholder: Prepare for a meeting with a stakeholder who disagrees.
  4. Day 18Project in trouble: Recover a project that is three weeks behind.
  5. Day 19Review gates for AI work: Design where humans must review AI-generated output.
  6. Day 20Escalating to leadership: Write an escalation that asks for a clear decision.
  7. Day 21Checkpoint: Workflow designDesign the review gates for one real workflow.Practical task + short written reasoning, scored against a rubric
Week 4Days 22–28Portfolio and interview readinessMeasurement and portfolioProving delivery impact and packaging your work.
  1. Day 22Delivery metrics: Choose metrics for throughput, quality and predictability.
  2. Day 23Dashboard for leadership: Build a delivery dashboard in a spreadsheet.
  3. Day 24Retrospective: Run a retrospective and turn it into actions.
  4. Day 25Portfolio: case study: Write a before-and-after case study of a redesigned process.
  5. Day 26Portfolio: presentation: Present your case study in 5 minutes.
  6. Day 27Interview drill: situational: Answer situational PM questions using STAR.
  7. Day 28Checkpoint: Case study presentationPresent a before-and-after of a process you redesigned.Practical task + short written reasoning, scored against a rubric

Weekly checkpoints

Four checkpoints. Real feedback.

Each one is marked on your reasoning, not just the output: and you defend it.

  1. 7After Day 7Process auditMap one real delivery process against today's tooling and identify what should change.
  2. 14After Day 14Re-estimateRe-estimate a live project with AI in the loop and explain the changes.
  3. 21After Day 21Workflow designDesign the review gates for one real workflow.
  4. 28After Day 28Case study presentationPresent a before-and-after of a process you redesigned.
A woman presenting her work to colleagues in a meeting room

Expected outcomes

What you will be able to do.

  • Plan and scope a project from a messy brief
  • Run sprints and track dependencies
  • Manage risk and scope change
  • Communicate status to stakeholders
  • Design where AI fits into delivery

Role-specific projects

Evidence you can show.

  1. 01End-to-end project plan: charter, backlog, timeline, risk register and status reports
  2. 02Case study of an AI-assisted delivery process

Interview preparation

Practise the questions Project Manager interviews actually ask.

Preparation runs through Week 4, then the most-asked questions on Days 29–30. Here is what you will be asked, and what a strong answer looks like.

  • Days 29–30Interview prep after Week 4
  • Three kinds of questionTechnical, scenario, behavioural
  • Model answersWhat a strong answer shows
  1. 01Technical

    “How do you estimate a project you have never done before?”

    A strong answer shows

    Uses decomposition, comparable work, ranges and explicit assumptions.

  2. 02Scenario

    “Your project is behind by three weeks. What do you do?”

    A strong answer shows

    Diagnoses the cause, presents options with trade-offs, and communicates early.

  3. 03Scenario

    “A senior stakeholder adds scope a week before launch.”

    A strong answer shows

    Assesses impact, offers options, and gets a documented decision.

  4. 04Technical

    “What is the difference between a risk and an issue?”

    A strong answer shows

    Clear distinction and how each is managed.

  5. 05Behavioural

    “Tell me about a project that failed.”

    A strong answer shows

    Honest ownership and specific lessons applied later.

  6. Topics covered

    • Project lifecycle
    • Agile and Scrum
    • Estimation
    • Risk and change management
    • Stakeholder management
    • Metrics and reporting
    Enroll now