Why Does Software Cost So Much?

Why Does Software Cost So Much? examines the economic and management challenges in software development through a collection of essays. DeMarco draws from his consulting experience to analyze why software projects frequently exceed budgets and timelines. The book addresses core issues like productivity measurement, team dynamics, and organizational politics in software companies. Through case studies and observations, DeMarco explores the disconnect between traditional management approaches and the realities of software development work. The essays cover topics including estimation methods, quality control, project leadership, and the human factors affecting software development costs. DeMarco presents practical strategies for improving project outcomes while acknowledging the inherent complexities of software creation. The book challenges conventional wisdom about software project management while making a broader statement about the need to rethink how knowledge work is measured and valued in organizations. Its analysis remains relevant for understanding today's software development landscape.

Readers describe this as a collection of essays that holds up decades later, with insights into software development economics and team dynamics. The pieces on productivity measurement and estimation remain relevant according to multiple reviewers. What readers liked: - Clear explanations of complex cost factors - Practical advice on measuring productivity - Humorous writing style and examples - Short, focused chapters What readers disliked: - Some dated references and examples - Repetitive themes across essays - Limited concrete solutions offered - Price high for relatively short book Review Stats: Goodreads: 3.9/5 (108 ratings) Amazon: 4.2/5 (21 ratings) Notable reader comments: "The essay on why software quality can save money is worth the price alone" - Amazon reviewer "Still applicable today though written in 1995" - Goodreads review "Good insights but needed more practical recommendations" - Software Dev Blog review

The Mythical Man-Month by Fred Brooks The exploration of software project management includes case studies from IBM's OS/360 project and insights into communication overhead, team dynamics, and planning fallacies.

Death March by Edward Yourdon This text presents strategies and observations for managing troubled software projects with impossible deadlines, inadequate resources, and unrealistic expectations.

Peopleware: Productive Projects and Teams by Tom DeMarco, Timothy Lister The book focuses on the human factors in software development, examining team formation, workplace environment, and organizational culture impact on productivity.

The Psychology of Computer Programming by Gerald M. Weinberg This work examines the human aspects of programming through studies of programmers' behaviors, thought processes, and interactions in development environments.

Software Engineering Economics by Barry W. Boehm The text presents frameworks for software cost estimation, risk analysis, and project management decisions based on empirical studies and industry data.

📚 Tom DeMarco co-created the Structured Analysis and System Specification methodology, which revolutionized how software requirements are documented and analyzed. 💡 The book was published in 1995 but predicted many modern software development challenges, including the importance of team dynamics and the fallacy of using overtime to meet deadlines. 🔍 DeMarco coined the famous phrase "You can't control what you can't measure," which became a fundamental principle in software project management. 👥 The author later reversed his position on software metrics and measurement in his 2009 paper "Software Engineering: An Idea Whose Time Has Come and Gone," showing his willingness to evolve with the industry. 💻 The book was one of the first to address the human factors in software development, moving beyond purely technical considerations to explore workplace culture, team motivation, and organizational politics.