SurvivalBook by Yann Martel, 2001 The Pacific, 1977

Life of Pi as a project: Kanban board and Gantt chart

When the ship carrying his family's zoo sinks in the Pacific, Pi is left in a lifeboat with a Bengal tiger, Richard Parker. He survives 227 days at sea before reaching Mexico.

  • 2team
  • 227 daysduration
  • Delivered at a costoutcome
  • 1handoffs, our count
  • 3re-plans, our count

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

Life of Pi as a Kanban board

The board is frozen at one moment, in the first weeks on the lifeboat. 1 cards wait in To do, 2 are in progress, 1 is blocked and 3 are done. The card on the critical path is "Keep the tiger fed and watered", owned by Pi. Blocked: "Get picked up by a passing ship", which the team cannot move on its own.

To do

  • Reach land

In progress

  • Keep the tiger fed and watered
  • Fish from the raft

Blocked

  • Get picked up by a passing ship

Done

  • Survive the sinking
  • Rig a raft
  • Mark out a territory

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

Life of Pi: the timeline as a Gantt chart

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

Dates follow the timeline stated in the book.

Cards on the timeline
CardStartDue
Ship sinksDay 0Milestone
Rig the raftDay 1Day 6
Train the tigerDay 6Day 60
Fish, ration, collect waterDay 6Day 227
Reach MexicoDay 227Milestone

What happened, in project terms

After the ship sank, Pi shared a lifeboat with a Bengal tiger called Richard Parker. He survived by rigging a raft of his own, marking out territory, training the tiger and keeping it fed and watered on a fixed routine. It is the most extreme stakeholder management in fiction, and the principles hold: clear boundaries, steady supply, no surprises.

By our count the quest has 1 handoff, moments where work changes hands, and 3 re-plans: about as many re-plans as the typical book on this page.

Lessons for project managers

  1. A risky stakeholder needs routines, boundaries and regular feeding

    In Kanbanchi, keep a short Blocked list and review it every day. Survival plans fail when a blocker sits unnoticed, not when the team lacks ideas.

  2. Use the manual

    The lifeboat had a survival manual, and Pi used it. Most problems have been met before, so read what is written down.

  3. A temporary fix can look like a permanent one

    The island gave food and rest, and would have killed him if he had stayed. Review a workaround before it becomes the plan.

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 biggest stakeholder can end the project at any time

    Likelihood: highImpact: severe

    Mitigation: Set clear boundaries, a routine and a steady supply.

    What happened: Pi rigged a raft, marked out territory and trained the tiger. Richard Parker never attacked him. Mitigated

  • Supplies run out

    Likelihood: highImpact: severe

    Mitigation: Ration, then build ways to collect more.

    What happened: He used the survival kit, fished, rationed and collected rainwater and fresh water from the stills. Absorbed

  • A refuge that looks safe is not

    Likelihood: mediumImpact: severe

    Mitigation: Check a refuge over time before you settle there.

    What happened: The floating island of algae turned out to be deadly at night. Pi worked it out and left. Absorbed

Life of Pi by the numbers

BookLife of Pi
AuthorYann Martel
First published2001
SettingThe Pacific, 1977
Quest typeSurvival
TeamA boy and a Bengal tiger
Duration227 days
OutcomeDelivered at a cost
Handoffs (our count)1
Re-plans (our count)3
Dates on this pageAs stated in the book

Questions about Life of Pi as a project

What does Life of Pi teach about project management?

A risky stakeholder needs routines, boundaries and regular feeding. Use the manual, and a temporary fix can look like a permanent one. The full reasoning is in the lessons above.

How long does the quest in Life of Pi take?

227 days. The Gantt chart on this page follows the timeline stated in the book.

How would you set up Life of Pi as a Kanban board?

Four lists: To do, In progress, Blocked and Done. At the moment shown above there are 1 cards to do, 2 in progress, 1 blocked and 3 done. The card to watch is "Keep the tiger fed and watered", 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