Frankenstein as a project: Kanban board and Gantt chart
Victor Frankenstein, a student at Ingolstadt, spends close to two years in secret building a creature and bringing it to life. There is no sponsor, no review and no plan for what happens once it works.
- 1team
- About two years to buildduration (approximate)
- Not deliveredoutcome
- 1handoffs, our count
- 2re-plans, our count
Start your free trial7 days, every feature, on your Google or Microsoft account.
Frankenstein as a Kanban board
The board is frozen at one moment, the night the creature wakes. 2 cards wait in To do, 1 is in progress, 1 is blocked and 3 are done. The card on the critical path is "Bring it to life", owned by Victor. Blocked: "Get a second opinion", which the team cannot move on its own.
To do
- Look after what you built
- Tell anyone at all
In progress
- Bring it to life
Blocked
- Get a second opinion
Done
- Study natural philosophy
- Collect the materials
- Assemble the body
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.
Frankenstein: the timeline as a Gantt chart
The same work on a timeline: 6 cards, 4 dependencies and the today line at Month 27. 1 card is a milestone, drawn as a diamond. 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.
| Card | Start | Due |
|---|---|---|
| Study at Ingolstadt | Month 0 | Month 10 |
| Collect the materials | Month 10 | Month 13 |
| Assemble the body | Month 13 | Month 23 |
| It wakes | Month 23 | Milestone |
| Handover and care | Month 23 | Month 26 |
| The creature on its own | Month 24 | Month 30 |
What happened, in project terms
Victor Frankenstein spent close to two years building his creature in secret, with no review, no sponsor and no plan for what happened once it worked. When it opened its eyes, he fled. Everything that followed came from that missing handover. Decide who looks after the thing you are building before you finish building it.
By our count the quest has 1 handoff, moments where work changes hands, and 2 re-plans: fewer re-plans than most books on this page.
Lessons for project managers
Shipping is not the end: plan the handover and the support
In Kanbanchi, add the acceptance check as its own card at the end of the build, with an owner who did not build the thing. A card in Done should mean someone else has looked at it.
Tell someone
Secrecy felt safe and made every problem bigger. Report early, even when the news is embarrassing, so others can help.
Do not restart a cancelled build under pressure
Victor agreed to build a second creature, then destroyed it half-finished, in front of the first. Decide on a second phase calmly, and keep your word once you do.
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.
Nobody reviews the work
Mitigation: Show the work to someone qualified before it goes live.
What happened: Victor worked alone and told no one. Nobody had a chance to question the idea before it was too late. Materialised
The builder walks away after launch
Mitigation: Decide who looks after the result before you finish building it.
What happened: When the creature opened its eyes, Victor fled. It went out into the world alone, and everything that followed came from there. Materialised
Silence makes the damage worse
Mitigation: When something goes wrong, tell the people affected.
What happened: Victor knew who had killed his brother but said nothing, and Justine was executed for the crime. Materialised
Frankenstein by the numbers
| Book | Frankenstein |
|---|---|
| Author | Mary Shelley |
| First published | 1818 |
| Setting | Geneva and Ingolstadt, 1790s |
| Quest type | Build |
| Team | 1, working alone |
| Duration | About two years to build |
| Outcome | Not delivered |
| Handoffs (our count) | 1 |
| Re-plans (our count) | 2 |
| Dates on this page | Approximate: the book gives no full timeline, so the Gantt chart uses relative steps |
Questions about Frankenstein as a project
What does Frankenstein teach about project management?
Shipping is not the end: plan the handover and the support. Tell someone, and do not restart a cancelled build under pressure. The full reasoning is in the lessons above.
How long does the quest in Frankenstein take?
About two years to build. The book gives no full timeline, so the Gantt chart on this page uses approximate, relative steps.
How would you set up Frankenstein 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 "Bring it to life", 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 trialBoard and Gantt chart on the same cards. Plan your own quest.
Start your free trial