Chapter 37 — Further Reading

Scope management is a topic where the best material is not in textbooks. The best material is in postmortems, in retrospective interviews, in honest developer blog posts, and in a handful of books that happen to contain scope-specific chapters. Read selectively. Most designers will get more value from two postmortems on games similar to their own than from any general scope-theory text.

Books on Scope, Production, and Finishing

Jason Schreier — Blood, Sweat, and Pixels (2017) The essential text on modern game-development scope. Each chapter is a postmortem of a shipped AAA or indie game, with Destiny, Halo Wars, Shovel Knight, Stardew Valley, Diablo III, The Witcher 3, Dragon Age: Inquisition, and Star Wars 1313 (cancelled) as the centerpieces. The scope lessons emerge from the reporting. Shovel Knight's exhaustion of Kickstarter funds, Destiny's late-project story rewrite, Stardew Valley's solo marathon — each one teaches scope through a different failure or success. If you read one book on this topic, read this. Clear writing, deep reporting, honest about how much pain is in the game-development process.

Jason Schreier — Press Reset (2021) The follow-up, focused on cancelled projects and studio closures. Chapters on Star Wars 1313, Scalebound, Irrational Games (the closure after BioShock Infinite), Visceral Games (cancelled after the Star Wars project was re-scoped out of existence), and others. The recurring theme: scope decisions, often driven by publishers or leadership changes, that ended projects and studios. Darker than Blood Sweat and Pixels but equally instructive.

Jason Schreier — Play Nice: The Rise, Fall, and Future of Blizzard Entertainment (2024) Blizzard's history is partly a scope-management history, particularly around projects like StarCraft: Ghost (cancelled) and the infamous "Project Titan" which eventually became Overwatch after years of failed attempts. Schreier's access to Blizzard history reveals what happens when a studio's culture values polish so highly that scope decisions become impossibly fraught.

Cliff Bleszinski — Control Freak: My Epic Adventure Making Video Games (2022) CliffyB's memoir includes candid discussion of scope decisions on Gears of War, Unreal Tournament, and his post-Epic studio Boss Key Productions (which closed after LawBreakers and Radical Heights failed to find audience). The post-Epic chapters are particularly useful because they show a veteran designer making scope mistakes even with decades of experience. Hubris is a perpetual scope risk.

Ken Levine and various — no single book, but extensive interviews Ken Levine's interviews about BioShock Infinite's development (multiple cut features, cut multiplayer, a multi-year scope evolution) are a masterclass in how scope gets away from a team. Search for his Gamasutra interviews, his podcasts with Stephanomaly and Game Maker's Toolkit, and the substantial 2014-2020 retrospectives on that game.

Specific Postmortems Worth Reading (or Watching)

Derek Yu — Spelunky (the book, Boss Fight Books series, 2016) Derek Yu's short book on the development of Spelunky from freeware experiment to commercial release. Contains some of the most practical scope thinking in game-development writing, including direct advice on when to cut and when to keep. Yu is a scope minimalist by temperament, and the book transmits that discipline.

Matt Thorson — Celeste postmortems and GDC talks The Celeste team has given multiple GDC talks and written blog posts about their scope decisions, particularly around what was cut from the original four-day jam game as it expanded to a full release. The "assist mode" design is, in effect, a scope decision: deciding what experiences to support and what to let the player customize.

Eric Barone (ConcernedApe) — Stardew Valley interviews and retrospectives ConcernedApe has given many interviews about the four-year solo development of Stardew Valley, and his scope decisions are worth studying in detail. The game shipped with approximately half the planned scope, and his willingness to cut — a genuinely hard thing for a solo developer emotionally invested in every feature — is what made the game ship at all.

Terry Cavanagh — Distractionware blog archive Cavanagh's blog over the past decade contains short, honest posts on the scope of individual projects — VVVVVV, Super Hexagon, Don't Look Back, Dicey Dungeons. His approach of "finish small games frequently" is embodied in the archive. Short reads, high signal-to-noise.

Daniel Cook — Lostgarden blog Cook's essays on game design, including his old pieces on scope, are still relevant. Search for his essays on "designing small" and the economics of indie development. His "Minute to Learn, Lifetime to Master" essay is tangentially related and valuable.

Team Cherry — Hollow Knight Kickstarter page and developer diary archive The original Kickstarter page is an artifact worth examining alongside the final shipped game; the delta is the scope expansion described in Case Study 37.1. The developer diaries and Ari Gibson's occasional interviews provide additional texture.

GDC Talks on Scope

"Overcoming Scope Creep" — various speakers, GDC Vault Multiple talks under this title have been given over the past fifteen years at GDC. The best of them focus on specific projects rather than general advice. Search the GDC Vault (some are free, most are paid subscription) for talks by Tim Cain (on Fallout and The Outer Worlds), Jennifer Scheurle, Rami Ismail, and Mark Serrels on scope discipline. Mark Serrels' "Nailing Scope" and similar talks are particularly accessible.

"The Four Pillars of Successful Game Design" — various Scope is not always explicitly named, but is embedded in talks on project management, production, and indie survival. Worth searching GDC Vault broadly for "indie postmortem" and spending an afternoon sampling.

Mark Brown — Game Maker's Toolkit (YouTube) Not GDC specifically, but Mark Brown's video essays often touch on scope questions embedded in specific games. His videos on Hollow Knight, Celeste, Hades, Into the Breach, and Baba Is You all include discussion of how those games are scoped tightly around a core mechanic. Accessible for beginners; deep enough for experienced designers to learn from.

Historical and Foundational

Jordan Mechner — The Making of Karateka (2012) and The Making of Prince of Persia (2011) Mechner's published development diaries from the 1980s are fascinating historical documents. Karateka (1984) was a one-man project whose scope, by modern standards, was tiny — a few minutes of gameplay. And yet Mechner's diaries show the same scope tensions that contemporary developers feel: features he wanted to add but cut, timelines he missed, trade-offs between ambition and completion. The Prince of Persia diary is longer and more detailed. Both are short and readable in an afternoon. Recommended for the historical perspective: these problems are not new.

Steve Meretzky, Don Daglow, Brian Moriarty — Infocom and early-80s-developer interviews The early adventure-game developers worked under savage constraints — tiny memory budgets, text-only interfaces, single-person teams. Their scope decisions are the purest version of the discipline: every line of prose had to justify its existence in memory. Interviews collected in publications like The Digital Antiquarian (Jimmy Maher's blog) are excellent reading.

Practical Production Resources

Clinton Keith — Agile Game Development with Scrum (2nd ed., 2020) If you want the formal production-methodology angle, Keith's book is the standard game-adapted Scrum text. It treats scope management as part of sprint planning and backlog management. More useful for team-based projects than solo; useful for understanding how bigger studios think about scope formally.

Rami Ismail — Game Dev Diary posts and interviews Ismail, co-founder of Vlambeer (Nuclear Throne, Ridiculous Fishing), has written and spoken extensively on indie scope and shipping discipline. His "Let's Make a Game: A Pitch for Pitches" and similar talks emphasize scope honesty as a professional requirement. Ismail is also notably candid about projects that didn't work and why.

Pixelpunk / Game Dev Twitter / Indie dev communities Not a single resource but a genre. Following active indie developers on social media — particularly around launch periods — provides ongoing visibility into how other people manage scope. Postmortem threads after a release are often more informative than the released postmortem article. Search for threads after releases of games comparable to yours.

On the Ethics of Scope

UK Advertising Standards Authority rulings on game marketing The ASA has ruled on several gaming cases where pre-launch promises and shipped content diverged (No Man's Sky, Colonial Marines, others). These rulings are publicly available and give a regulatory perspective on where pre-launch scope claims cross legal or ethical lines.

Kotaku and Polygon longform reporting on cancelled and troubled projects Ongoing journalism on projects like Star Citizen, Anthem, Fallout 76, and others provides living case studies in scope failure. Read as they appear; the collective picture is instructive.

Derek Yu — Finishing a Game (blog post, 2011) A short, frequently-cited post on the psychology of finishing. Not about scope management per se, but about the emotional discipline that scope management requires. Findable through search; one of the most-quoted short essays in indie development.

One-Sentence Summary of the Reading List

If you only read one thing on scope, read Jason Schreier's Blood, Sweat, and Pixels; if you only watch one thing, watch Mark Brown on Hollow Knight; if you only follow one approach, follow Terry Cavanagh's example of shipping small games frequently.