Long gameBook by Isaac Asimov, 1951 Terminus

Foundation as a project: Kanban board and Gantt chart

The mathematician Hari Seldon predicts that the Galactic Empire will fall and plans to cut the dark age that follows from thirty thousand years to one thousand. He sets up a Foundation on Terminus at the edge of the galaxy, with an encyclopedia as its cover story.

  • Scientists, then a planetteam
  • About 150 years in the bookduration (approximate)
  • Open endingoutcome
  • 5handoffs, our count
  • 1re-plans, our count

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

Foundation as a Kanban board

The board is frozen at one moment, at the first Seldon crisis. 2 cards wait in To do, 1 is in progress, 1 is blocked and 3 are done. The card on the critical path is "Survive the first crisis", owned by Hardin. Blocked: "Help from the Empire", which the team cannot move on its own.

To do

  • Second crisis
  • A second empire, in a thousand years

In progress

  • Survive the first crisis

Blocked

  • Help from the Empire

Done

  • Predict the fall
  • Settle Terminus
  • Record the vault messages

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

Foundation: the timeline as a Gantt chart

The same work on a timeline: 6 cards, 4 dependencies and the today line at Year 50. 3 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
Seldon's trialYear 0Milestone
Settle TerminusYear 0Year 50
Encyclopedia, the cover storyYear 0Year 50
First crisisYear 50Milestone
Second crisisYear 80Milestone
Traders and merchantsYear 80Year 155

What happened, in project terms

Hari Seldon predicted the fall of the Galactic Empire and planned to cut the dark age after it from thirty thousand years to one thousand. He knew he would be long dead at every crisis, so he recorded messages to play in a vault at the moments he expected them. Good documentation is a plan that keeps working after its author has gone.

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

Lessons for project managers

  1. Write the plan so it runs without you

    In Kanbanchi, split a long plan into phases on the Gantt chart and add a milestone card for every review point. Long projects drift between milestones, so put the milestones where you will actually look.

  2. Write the plan so it runs without you

    Seldon's vault messages kept the plan alive for centuries. Good documentation outlives its author.

  3. Expect the crisis, and plan the review

    Seldon timed his messages for the crises he predicted. Build reviews into the plan at the points where you expect things to break.

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 team takes the cover story at face value

    Likelihood: mediumImpact: high

    Mitigation: Decide how much the team needs to know, and when.

    What happened: The encyclopedists thought they were writing an encyclopedia. The real plan showed itself only at the first crisis. Absorbed

  • Armed neighbours threaten the project

    Likelihood: highImpact: severe

    Mitigation: Find leverage the neighbours cannot do without.

    What happened: Salvor Hardin kept Anacreon in check by making it depend on the Foundation's science. Mitigated

  • The author is gone when the crisis comes

    Likelihood: highImpact: high

    Mitigation: Record the plan so it works without you.

    What happened: Seldon recorded messages to play in a vault at the moments he expected crises, long after his death. Mitigated

Foundation by the numbers

BookFoundation
AuthorIsaac Asimov
First published1951
SettingTerminus
Quest typeLong game
TeamScientists, then a planet
DurationAbout 150 years in the book
OutcomeOpen ending
Handoffs (our count)5
Re-plans (our count)1
Dates on this pageApproximate: the book gives no full timeline, so the Gantt chart uses relative steps

Questions about Foundation as a project

What does Foundation teach about project management?

Write the plan so it runs without you. Write the plan so it runs without you, and expect the crisis, and plan the review. The full reasoning is in the lessons above.

How long does the quest in Foundation take?

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

How would you set up Foundation as a Kanban board?

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