Projekt Jednorożec
Powieść o szansie w epoce przewrotów cyfrowych
Author: Gene Kim
I read the Polish translation of this book, which serves as a modern sequel to The Phoenix Project . While the core philosophy remains the same, this new volume updates the technical landscape-replacing references to palmtops with contemporary tools like Kubernetes and Docker. If you’ve already read the original, this feels like a timely refresh rather than a complete retread.
The book is structured as a novel, weaving practical DevOps and agile principles into relatable (and sometimes humorous) character situations. This narrative approach makes the lessons more digestible than a traditional management textbook. You learn alongside the characters as they face real workplace challenges. I worked in a company which was selling car parts and I could literally name book characters in the real life 🤣
The book centers on an improvement model built on five key ideals:
Locality and Simplicity: Teams should be able to modify their code and systems independently, minimizing dependencies and coordination overhead with other teams.
Focus, Flow, and Fun: Create an environment free from constant interruptions so developers can achieve productive “flow” states and actually enjoy their work.
Improvement of Daily Work: Prioritize reducing technical debt and improving internal processes over simply shipping new features at all costs.
Psychological Safety: Build a culture where failure is a learning opportunity, not a cause for punishment-where people feel safe speaking up about problems.
Customer Focus: Keep every action and technical decision grounded in delivering genuine value to the end user, not just internal metrics.
Note
I noted below a quick reference of key practices:
- Reduce handoffs and dependencies between teams to increase autonomy.
- Eliminate interruptions that break developer focus and flow.
- Schedule time for technical debt reduction on par with feature development.
- Create safe-to-fail environments where experimentation is encouraged.
- Measure success by customer value, not velocity or lines of code.
- Invest in automation to reduce toil and manual processes.
- Foster cross-functional collaboration while maintaining team independence.
- Regularly reflect on daily work and remove bottlenecks.
A solid, accessible read for anyone with DevOps responsibilities or interest in modern software development culture. The novel format makes it both engaging and practical-you can immediately apply the Five Ideals to your own organization.