Harry Potter: the Horcrux hunt as a project

DefenceBook by J.K. Rowling, 2007 Wizarding Britain

Harry Potter: the Horcrux hunt as a project: Kanban board and Gantt chart

Harry, Ron and Hermione leave school to find and destroy the Horcruxes, the objects that keep Voldemort alive. Dumbledore has left them the goal, a few odd objects and no plan.

  • 3team
  • About nine monthsduration (approximate)
  • Delivered at a costoutcome
  • 5handoffs, our count
  • 5re-plans, our count

Start your free trial7 days, every feature, on your Google or Microsoft account.

Harry Potter: the Horcrux hunt as a Kanban board

The board is frozen at one moment, in the winter, while one teammate is away. 2 cards wait in To do, 2 are in progress, 2 are blocked and 2 are done. The card on the critical path is "Find the next piece", owned by Harry. Blocked: "A way to destroy them" and "Ron", which the team cannot move on its own.

To do

  • Destroy the last pieces
  • Win at the school

In progress

  • Find the next piece
  • Research

Blocked

  • A way to destroy them
  • Ron

Done

  • Leave the wedding
  • Take the locket

Purple label: on the critical path. Letter: the card owner, and a question mark means nobody owns it. Blocked: stopped by something outside the team.

Run your own project on a board like this

Lists, owners, due dates and subcards, inside the Google Drive or Microsoft account your team already uses.

Start your free trial

The Horcrux hunt timeline as a Gantt chart

The same work on a timeline: 7 cards, 6 dependencies and the today line at Month 4. 4 cards are milestones, drawn as diamonds. No arrow is red: every card waits for the one before it, as planned.

Dates are approximate: the book does not give a full timeline, so the chart uses relative steps.

Cards on the timeline
CardStartDue
Leave the weddingMonth 0Milestone
Hide in LondonMonth 0Month 1
Take the locketMonth 1Milestone
Camping without a planMonth 1Month 4.8
Find the swordMonth 4.8Milestone
Spring breakoutsMonth 5Month 8.9
Final battleMonth 9Milestone

What happened, in project terms

The team was given a goal, a few odd objects and no plan. It spent months camping without progress, lost a member for weeks and found the tool it needed only with outside help. If you are the sponsor, write the brief down. If you are the team, ask for it.

By our count the quest has 5 handoffs, moments where work changes hands, and 5 re-plans: more re-plans than most books on this page.

Lessons for project managers

  1. A sponsor who hands out the brief in pieces

    In Kanbanchi, give each threat a card with an owner, a due date for the next check and a Critical path label if it can end the project. Threats without cards are the ones that arrive as surprises.

  2. Rotate the stress

    The locket wore down whoever carried it, so they took turns. Do not leave the hardest work on one person for months.

  3. Write the brief down

    If the sponsor is going to be unavailable, a written brief is the only one the team will have. Ask for it while you can.

Draw the dependencies before they bite

The Gantt chart uses the same cards your team already moves on the board.

Start your free trial

What went wrong: the risk register

Most of what went wrong was visible early. Here are three risks a project manager could have written down at the start. Switch between the plan and what actually happened.

  • The brief is incomplete

    Likelihood: highImpact: severe

    Mitigation: Write the brief down, and ask the sponsor for it while you still can.

    What happened: The team spent months camping without progress, working out the plan from fragments. Materialised

  • The team splits under pressure

    Likelihood: highImpact: high

    Mitigation: Share the load and talk about morale openly.

    What happened: Ron left after an argument and was away for weeks before he found his way back. Absorbed

  • There is no means to destroy what you find

    Likelihood: highImpact: severe

    Mitigation: Find the tool before you need it.

    What happened: They found the sword of Gryffindor only with outside help, in a frozen pool in the Forest of Dean. Absorbed

Harry Potter: the Horcrux hunt by the numbers

BookHarry Potter: the Horcrux hunt
AuthorJ.K. Rowling
First published2007
SettingWizarding Britain
Quest typeDefence
Team3
DurationAbout nine months
OutcomeDelivered at a cost
Handoffs (our count)5
Re-plans (our count)5
Dates on this pageApproximate: the book gives no full timeline, so the Gantt chart uses relative steps

Questions about Harry Potter: the Horcrux hunt as a project

What does Harry Potter: the Horcrux hunt teach about project management?

A sponsor who hands out the brief in pieces. Rotate the stress, and write the brief down. The full reasoning is in the lessons above.

How long does the quest in Harry Potter: the Horcrux hunt take?

About nine months. The book gives no full timeline, so the Gantt chart on this page uses approximate, relative steps.

How would you set up Harry Potter: the Horcrux hunt as a Kanban board?

Four lists: To do, In progress, Blocked and Done. At the moment shown above there are 2 cards to do, 2 in progress, 2 blocked and 2 done. The card to watch is "Find the next piece", on the critical path. Give it two owners, and link it to the cards it waits on so the Gantt chart shows the order.

Plan your own quest on one board and one timeline

Lists for the work, two names on every critical card and the dependencies drawn before anything goes wrong, inside the Google or Microsoft account you already use.

Start your free trial