When comparing Rapid Development vs The Effective Executive by Peter Drucker, the Slant community recommends Rapid Development for most people. In the question“What are the best books on technical leadership in software projects?” Rapid Development is ranked 3rd while The Effective Executive by Peter Drucker is ranked 5th. The most important reason people chose Rapid Development is:
The author discusses how haste and unrealistic schedules will negatively impact a project. Causing the deadline to extend well past what it could have, had a realistic time frame been put in place initially.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Covers improving development schedules in detail
The author discusses how haste and unrealistic schedules will negatively impact a project. Causing the deadline to extend well past what it could have, had a realistic time frame been put in place initially.
Pro Lists out "Best Practices" to summarize the lessons
This is a large book at 680 pages, so having the lessons summed up is quite beneficial. 27 "Best Practices" are discussed, including the pros and cons of them.
Pro Focused on implementable lessons
Rather than discuss only the theory behind leadership, and author focuses on providing real examples and lessons that can be applied.
Pro Catches most mistakes a new executive would make
Pro Examples span most of the last century, across cultures
These examples are old enough for us to see whether a decision regarded as brilliant is still brilliant or has it started to strangle the company (Drucker himself points out some cases, like GM's reorganization being brilliant for its time, but something which needs to change for it to move ahead).
Pro By the master of management, Peter F Drucker.
The author, Peter Drucker is sometimes referred to as "the founder of modern management".
He has 39 published books and was well known for his consulting work with management, working with large companies (such as IBM and General Motors).
Pro Entertaining writer
Pro Very thin
It's just 174 pages.
Cons
Con Outdated methodologies
This book was published in 1996 and discusses methodologies that were popular at the time (such as the waterfall model).
Con It's not specific to "technical leadership in software projects"
I.e. it does not answer the question specifically.