Agile Sapiens

A Literary Business Analysis

Read online for free. Texts also available in formats EPUB and PDF.

Main text

  1. Preface: On the Method of Literary Analysis of BusinessPreface to *Agile Sapiens* — on the Literary Analysis of Business method and why classical fiction turned out to be more accurate than any consultant.
  2. Phileas Fogg Invented What Is Now Killing Modern CorporationsHow a fictional English gentleman of 1872 intuitively applied the principles that the modern Agile industry has commercialized, distorted, and sold back at a cost of billions
  3. Chapter 1: Jules Verne ProgramsHow the adventure literature of the nineteenth century laid down the patterns of project management — from *Twenty Thousand Leagues* to the sprints of Silicon Valley.
  4. Chapter 2: Frankenstein Manages a ProjectHow the novel by an eighteen-year-old Mary Shelley became the most precise post-mortem of corporate failure: from FBI Sentinel to Healthcare.gov.
  5. Chapter 3: Sherlock Holmes Makes a DiagnosisThe deductive method for recognizing corporate pathologies: seven signs your project is dying — from Knight Capital to Target Canada.
  6. Intermezzo I. The Consulting SuiteA satirical diagnosis of the agile theater through Carroll and Bulgakov. A consultancy where forty-three teams, two hundred and eight sprints, and twelve hundred retros a month do not produce a single product. Sprints for the sake of retros, retros for the sake of planning the next sprints. «Seven roles coordinating the work of one person with himself» — and that is called a mature process.
  7. Chapter 4: Borges Counts Story PointsHow measurements meant to make teams more agile turn into a lottery — from the Spotify Model to the OKR theater, from velocity gaming to the retrospective ritual.
  8. Chapter 5: Cyrus Smith Builds a CivilizationBootstrap leadership: how a small autonomous team outstrips corporate bureaucracy. The engineers of *The Mysterious Island* as the prototype of every successful tiger team.
  9. Chapter 6: Mina Harker Takes the NotesThe Victorian-era distributed team: phonograph, shorthand, telegraph, and one typewriter against an invisible enemy. The Crew of Light in Bram Stoker as an early prototype of the cross-functional team with a single source of truth.
  10. Chapter 7: Doctor JekyllCorporate duality from Stevenson to Argyris. Dr Jekyll is the manifesto — corporate values on the meeting-room wall. Mr Hyde is what teams actually do at the third hour of a Friday sprint. Doctor Lanyon is the senior who sees both and does not survive the seeing. Argyris and Schön (1974), Goffman (1959) and Koreiko from The Little Golden Calf.
  11. Chapter 8: Don Quixote and Sancho — The Birth of Team MythThe finale of Act II. Karl Weick showed in 1995 what Cervantes had shown in 1605: organizations are held together not by org structures and not by procedures, but by a shared story about who they are and where they are going. Four laws of team mythology, three modes (generative, defensive, reconciling), one Russian twin, and one death, in which Sancho weeps not for the loss of a partner but for the loss of a shared meaning.
  12. Intermezzo II. The Production BasementA production basement: two hundred and thirty-seven bugs hanging, one hundred and eighty-nine P0s recoded to P1, P1 to P2, P2 to technical debt, technical debt to a workshop in the next quarter (which is still being planned). Agile methodology as the formalized avoidance of programming. Four huddles a day to synchronize a team that produces nothing between them. A satire sharper than any post-mortem.
  13. Chapter 9: The Time Machine and the Horizons of LaborIn 1895 Wells is describing not a journey to the year 802,701 but the mechanism by which labor is rearranged under the pressure of technology. The Eloi and the Morlocks are the logic of workforce differentiation carried to its limit. A century later economists rediscover the same mechanism under the names «job polarization» (Autor) and «political economy of distribution» (Acemoglu and Johnson). Platonov in 1930 adds a third reading: labor severed from its outcome turns into a pit that eats itself.
  14. Chapter 10: Monday Begins on Saturday — NIICHAVO as the Ideal Agile TeamFour laws of a self-organizing R&D team from the Strugatsky brothers: meaning as entry filter, dual leadership, specialist against administrator, immersion instead of training. NIICHAVO as a utopia of meaningful labor and a diagnosis of bureaucracy in a team.
  15. Chapter 11: The Plague — How a Team Forms in Sustained CrisisAlbert Camus's *La Peste* (1947) — the *communauté* of Doctor Rieux, Tarrou, Castel, Rambert, Grand, and Paneloux: four laws of sustained work under crisis without a victory horizon — refusal as obligation, common decency instead of heroism, convergence without hierarchy, the discipline of continuation.
  16. Intermezzo III. The Transformation ElevatorA one-hundred-and-twenty-seven-story elevator of agile transformation. They ascend one floor per iteration with a retrospective between each; «press the button for 127» is waterfall thinking. The apotheosis of agile absurdism: the vertical decomposition of movement, the adaptive planning of the simplest action. A caricature of digital transformation initiatives in which the process of transformation has become its only product.
  17. Afterword. Eleven QuestionsAfterword to Agile Sapiens — a synthesis of twelve chapters into eleven diagnostic questions, with a frame from the pilot chapter. Not commands, but questions.

Apparatus

  1. AcknowledgmentsRecognition of all who helped in the making of this book
  2. MethodologyPrinciples of research, standards of verification, approaches to analysis
  3. SourcesFull bibliography of sources used, grouped by chapter
  4. Subject IndexAlphabetical index of key concepts, characters, and categories from Agile Sapiens — with references to chapters and appendices
  5. AI Transparency StatementTransparent disclosure of AI assistance in content creation per EU AI Act Article 50
  6. ColophonPublishing information — who, when, how this book was created