Rapid Development Taming Wild Software Schedules

The book is widely acclaimed as a highly influential and essential read for anyone in software development. Many reviewers consider it a must-buy, with some purchasing multiple copies for different purposes or immediately replacing a lent copy. It has been described as captivating, with some readers completing it even during demanding work schedules, and inspiring others to attend related courses. Reviewers praise its ability to provide general, philosophical ideas for rapid development, identify classic organizational errors, and present effective methods for increasing speed. It helps readers understand colleagues and customers, appreciate the importance of planning, and manage expectations among stakeholders. The author's approach is noted for being well-researched, drawing on extensive sources and personal experience, rather than just opinion. Its clear, simple language, thoughtful structure, and use of fictional project examples make it an easy and engaging read. Many highlight its focus on the psychological aspects of development, such as managing expectations, avoiding political pitfalls, and controlling change, making it valuable for project managers as well as developers. Some even consider it superior to the author's other highly regarded works and a foundational text for best practices.

Despite its many strengths, a recurring criticism is that the book shows its age. Reviewers note that much of the data and advice stems from experiences in the early 1990s, making some concepts and practices less relevant to modern software development. There are concerns that uninformed readers might be led astray by outdated advice or methodologies that have since proven to be fads. Specific points of contention include its reliance on antiquated estimation practices and occasionally outdated takes on tools and industry best practices, which some feel limit its credibility. A few reviewers found the book excessively verbose, suggesting that its content could be conveyed more effectively in a significantly shorter, better-organized version. The case studies, in particular, were sometimes described as artificial, contrived, and failing to provide new insights beyond the main text. While acknowledging its foundational value, some believe it has not aged as gracefully as other works by the same author, especially in light of more recent paradigm shifts like agile development, leading to a struggle to find certain sections on "Best Practices" entirely applicable today.

In conclusion, while the book's age is a common point of discussion, it is broadly considered a classic and an invaluable resource for understanding the enduring human and managerial challenges in software development. It may not appeal to those solely seeking the absolute latest technological trends or fads, but it offers timeless wisdom on avoiding common pitfalls, managing projects, and fostering effective teams. This book is highly recommended for software developers, project managers, tech leads, and anyone involved in the planning, management, development, or deployment of software. It provides crucial insights into managing expectations, navigating organizational politics, and making sense of the complexities of software projects, making it a foundational read for elevating one's skills to a true engineering level. It serves as an excellent guide for understanding classical development situations and missteps, even if the terminology has evolved over time.