JourneyBook by Homer, c. 8th century BC The ancient Aegean

The Odyssey as a project: Kanban board and Gantt chart

After the fall of Troy, Odysseus has one deliverable: bring his ships and crew home to Ithaca. It takes ten years of wandering, he loses every ship and every man on the way, and when he finally lands, his house is full of suitors who have written him off.

  • 12 ships of crewteam
  • Ten yearsduration (approximate)
  • Delivered at a costoutcome
  • 2handoffs, our count
  • 6re-plans, our count

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

The Odyssey as a Kanban board

The board is frozen at one moment, during the seven years on Calypso's island. 2 cards wait in To do, 1 is in progress, 2 are blocked and 3 are done. The card on the critical path is "Get off the island", owned by Odysseus. Blocked: "Leave Calypso's island" and "Get a ship", which the team cannot move on its own.

To do

  • Deal with the suitors
  • Reach Ithaca

In progress

  • Get off the island

Blocked

  • Leave Calypso's island
  • Get a ship

Done

  • Leave Troy
  • Pass the Cyclops
  • Sail past the Sirens

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 Odyssey: the timeline as a Gantt chart

The same work on a timeline: 4 cards, 3 dependencies and the today line at Year 6. 2 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 TroyYear 0Milestone
Island to islandYear 0Year 3
Stuck on Calypso's islandYear 3Year 10
Reach IthacaYear 10Milestone

What happened, in project terms

Within sight of home, the crew opened a bag they had never been told about and blew the fleet back out to sea. The leader carried every decision himself and explained none of them. Brief the team on what not to touch, and why.

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

Lessons for project managers

  1. An unbriefed team can undo the work in sight of the finish

    In Kanbanchi, give every leg of the route its own card with a start and due date, then link the legs with dependencies. When one slips, the Gantt chart shows at once which later legs move with it.

  2. Do not announce yourself before the job is done

    Odysseus shouted his name at the blinded Cyclops as he sailed away, and Polyphemus asked his father Poseidon for revenge. Celebrate after delivery, not during it.

  3. Plan the arrival as carefully as the journey

    At home he did not rush in. He came in disguise, found out who was loyal and planned the final move with his son. The last mile of a project deserves its own 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 crew acts on something it was never briefed about

    Likelihood: highImpact: severe

    Mitigation: Tell the crew what the bag from Aeolus holds and why nobody may open it.

    What happened: Within sight of Ithaca the crew opened the bag of winds while Odysseus slept, and the fleet was blown back out to sea. Materialised

  • The team is lost to a local temptation

    Likelihood: mediumImpact: severe

    Mitigation: Set rules for every stop, agree them before landing and say who enforces them.

    What happened: On Thrinacia the crew ate the cattle of the Sun despite the warning. The last ship was wrecked and only Odysseus survived. Materialised

  • The home base is taken over while the lead is away

    Likelihood: highImpact: high

    Mitigation: Keep the people at home informed, with a date or at least a sign of life.

    What happened: Suitors filled the palace and pressed Penelope to remarry. Odysseus took it back only by arriving in disguise. Absorbed

The Odyssey by the numbers

BookThe Odyssey
AuthorHomer
First publishedc. 8th century BC
SettingThe ancient Aegean
Quest typeJourney
Team12 ships of crew
DurationTen years
OutcomeDelivered at a cost
Handoffs (our count)2
Re-plans (our count)6
Dates on this pageApproximate: the book gives no full timeline, so the Gantt chart uses relative steps

Questions about The Odyssey as a project

What does The Odyssey teach about project management?

An unbriefed team can undo the work in sight of the finish. Do not announce yourself before the job is done, and plan the arrival as carefully as the journey. The full reasoning is in the lessons above.

How long does the quest in The Odyssey take?

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

How would you set up The Odyssey 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, 2 blocked and 3 done. The card to watch is "Get off the island", 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