Delivering the Impossible Successful Ways of Seeing Software Project Management (Mark Stringer) (z-library.sk, 1lib.sk, z-lib.sk)

【One-Line Pitch】 A practical, story-driven guide for software project managers who feel trapped between fixed deadlines and fuzzy requirements, showing how swapping your mental model of a project can make the "impossible" deliverable. Best for working PMs, tech leads, and anyone accountable for shipping software in messy human organizations. 【Book Arc】 - **Opening (~0%–9%)**: Frames the core problem — projects that feel impossible because dates were promised before scope was known — and argues the fix is finding better "ways of seeing." - **Early (~9%–28%)**: Makes the case that software is eating the world and that project management is an irrational, emotional business, then previews the book's two-part structure: helpful vs. unhelpful ways of seeing. - **Middle (~28%–53%)**: Part I develops helpful lenses — projects as streams (value streams borrowed from lean manufacturing), swamps, escape attempts, cars (empirical process, stand-ups, retrospectives), and pirate ships (psychological safety, status transactions). - **Late (~53%–75%)**: Continues the helpful lenses with bets and "not bets" — breaking big bets into smaller ones, the hiding hand, project management theater, and games like "Bricks Without Straw." - **Ending (~75%–100%)**: Part II turns to unhelpful ways of seeing — commitment and consistency traps, "all/same/forever/exact match" symmetrical thinking, and how bosses see projects as sources of bad news — closing with practical steps to help everyone see smarter. 【Key Takeaways】 - **Projects feel impossible mainly because of people, not code** (Opening): complexity comes from emotions, incentives, misalignments, and fears; treating it as a human system problem is the book's central reframe. - **There is no single correct lens — there are at least six or seven** (Early): streams, swamps, cars, escape attempts, pirate ships, and bets are offered as interchangeable perspectives, not a methodology to follow. - **Value streams come from manufacturing, and the leap to software is imperfect** (Middle): the book traces lean thinking from Toyota to software, but flags that not all organizations make cars — the metaphor has limits. - **Psychological safety and status transactions shape what gets said** (Middle): the "pirate ship" chapter argues that unspoken blockers persist because raising them is a status risk, and offers tactics like talking side-by-side rather than face-to-face. - **Empirical process (stand-ups, retrospectives, show-and-tell) helps, but software isn't driving a car** (Middle): most car journeys succeed, and it's clear who's driving — neither holds for software projects. - **Commitment and consistency are powerful and dangerous** (Late): the COMMIT chapter shows how the drive to keep promises distorts decisions, and how to make a promise when you really must. - **Symmetrical thinking ("all," "same," "forever," "exact match") makes us dumb** (Late): the ALL chapter argues unconscious symmetry distorts how we judge time, knowledge, choice, speed, cost, and value. - **Bosses often see projects as problems and bad news** (Ending): the BOSS chapter reframes this so leaders can see projects more usefully, and the conclusion gives practical steps to spread smarter ways of seeing. 【Reading Tips】 - **Read the Introduction and Part I preview carefully** (~0%–28%): they set up the book's logic and tell you exactly which lenses are coming, so you can navigate the rest. - **Skim the manufacturing history in the Stream chapter** if you already know lean/Kanban; focus on where the metaphor breaks down for software. - **Deep-read the CAR and SHIP chapters** if you run teams — they contain the most directly actionable material on empirical process and psychological safety. - **Treat Part II as diagnostic, not descriptive**: the COMMIT and ALL chapters are meant to help you spot your own unhelpful defaults, so read them with your current project in mind. - **Don't expect a step-by-step methodology**: the book deliberately offers perspectives, not prescriptions — take away the habit of switching lenses, not a checklist. 【Coverage Limits】 These excerpts cover the front matter, introduction, part structure, and chapter outlines through the middle of the book; the detailed content of later chapters (BET, NOT BET, COMMIT, ALL, BOSS, CONCLUSION) is only visible through headings and previews, so this guide cannot summarize their specific arguments or examples.