StarCraft: From ‘Orcs in Space’ to a real time strategy revolution — A software engineering teaching case

This teaching case examines the turbulent development of StarCraft (1996–1998) by Blizzard Entertainment. Initially conceived as a derivative project aimed at filling a short-term revenue gap (critically dubbed “Orcs in Space”), the project underwent a radical transformation following a poor reception at E3 1996. The narrative chronicles the team’s decision to discard their initial codebase in favor of a complete engine rewrite, and the subsequent challenges of resource management when the entire team was temporarily reassigned to rescue a parallel project ( Diablo ), and the sustained crunch period that preceded the game’s eventual release.. Through this case, students analyse the sociotechnical complexities of software development across three levels of decision-making defined by ISO/IEC 12207:2017: organisational portfolio governance, project-level technical management, and day-to-day operational execution. Core themes include product scope management and its redefinition under uncertainty, portfolio management trade-offs arising from parallel development with shared talent pools, the high cognitive cost of context switching, the accumulation and deliberate acceptance of technical debt, the diminishing returns of crunch mode, and the paradox of team cohesion as both an enabling asset and a structural liability. The case illustrates classic software engineering principles in practice. It is designed for undergraduate and graduate courses in Software Project Management, Software Engineering, and IT Strategy, offering a historical lens on agile principles and team dynamics under extreme pressure.