- Hardcover: 496 pages
- Publisher: Wiley; 1 edition (July 18, 2000)
- Language: English
- ISBN-10: 0471363669
- ISBN-13: 978-0471363668
- Product Dimensions: 7.7 x 1.3 x 9.4 inches
- Shipping Weight: 2.3 pounds (View shipping rates and policies)
- Average Customer Review: 8 customer reviews
- Amazon Best Sellers Rank: #3,074,419 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
AntiPatterns in Project Management 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
"Children of Blood and Bone"
Tomi Adeyemi conjures a stunning world of dark magic and danger in her West African-inspired fantasy debut. Pre-order today
Customers who viewed this item also viewed
What other items do customers buy after viewing this item?
Written for the project manager or IT professional, AntiPatterns in Project Management describes 18 "AntiPatterns" that can go wrong in the realm of software project management, plus management techniques and tips to overcome them. Filled with real-world insight and case studies that describe actual projects gone awry, this title gives a solid measure of management expertise that can help you succeed with your next project.
Early sections of the text set the tone with management techniques that stress standards and rigorous software processes. The authors discuss the importance of managing people, technology, and processes for successful project management. While most books on patterns keep descriptions short and almost schematic, an entire chapter--filled with background material on the causes, solutions (or "refactoring") to move beyond it, and examples borrowed from the field--is devoted to each AntiPattern. (The names of companies have been changed, which makes for less dramatic reading, although this was no doubt a legal necessity.)
Anyone who has worked in software development will recognize many of the AntiPatterns here. First, bad management and bad management practices get their due--managers who don't or can't manage, projects that are late and require that staff be added at the last minute, and obstreperous employees (or "corncobs") who can't or won't work in teams.
Descriptions of technology AntiPatterns include troubles with distributed technologies, lack of architecture, demos that grow into unusable "finished" software, and software that hasn't undergone any planning at all. When it comes to process management, things can go wrong, too, as in the case of misapplied software life cycles. (In this section, the book lists no fewer than nine different software life cycles from which you can choose.) Other process AntiPatterns include customers who drive software design all the way through to disaster, the "domino effect" of changes to staff that can destroy team effectiveness, and management that demands adherence to an already late shipping date. Final sections show how these AntiPatterns often occur in conjunction. The book concludes with some "critical aspects" for successful project management.
Although a bit theoretical at times, this title has plenty of practical advice on improving your everyday project-management success. As the authors note, the great majority of software projects today are considered failures. By reading this savvy and well-organized volume, and analyzing what can go wrong, you can improve the odds in your favor in future development efforts. --Richard Dragan
- Introduction to AntiPatterns for project managers
- Standards, refactoring, and solutions for AntiPatterns
- Case studies
- People-management AntiPatterns (Micro-management, Corporate Craziness, The Brawl, Size Isn't Everything, Chaos, and Process Disintegration)
- Technology management AntiPatterns (Batteries Not Included, Distributed Disaster, Gilding the Lily, Wherefore Art Thou Architecture, Killer Demo, and One-Shot Deal)
- Process-management AntiPatterns (Planning 911, Lifecycle Malpractice [including nine software life cycles], The Customer/Too Many Hands in the Soup, One Size Fits All, The Domino Effect, and Myopic Delivery)
- AntiPattern collisions
- Best practices for project management
- Strategies for improving project management
"...an interesting book that contains a lot of material..." "If you care about being a good manager you will read this book..." (Overload, September 2000)
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
However, the book mostly fails to deliver.
For one, the book has imposed a superficial and poorly fit structure to the description of every AntiPattern. The result is that lots of information, like the causes and results of the AntiPattern, will be described two or three times in slightly different forms. This bloats the book needlessly. If a different form had been selected - say, a collection of essays - the book could have been 150 pages instead of the massive ~450 pages it is now.
Another reason the book fails, is that many of the solutions seem firmly planted in old thinking about project management as advocated by SEI, NASA/SEL, and others. Significantly, change is mostly regarded as evil. One of the recommended solutions to change in the Chaos AntiPattern is "Develop a software development plan and stick to it". In the Gilding the Lily AntiPattern (a.k.a. "Gold Plating"), it states that "Often the architects and developers must be physically prevented from making changes." Also, while incremental or iterative development is carefully mentioned in places, most of the solutions fit best with linear, phased, and pretty inflexible development paradigms. The book would have benefited from using solutions from more agile methodology thinking.
A third reason is that some of the solutions don't attack the root causes at all. The one and only solution to the Process Disintegration AntiPattern (where people don't follow the process because it is too heavy) is to institute an internal, no-process-at-all, developer-driven project. But how does this solve the problem for all of the company's normal projects that, presumably, are still expected to follow some normal process? The book doesn't say.
The book is not totally hopeless, though. It can be useful to be aware of most of the AntiPatterns and their causes, as well as some of the solutions.
But in the end I wouldn't recommend this book neither to inexperienced project managers - who wouldn't be able to recognize what solutions are good and what are bad - or experienced project managers, who would be enlightened enough to already know what they can do, or if not, would benefit much more from reading other books.
The book uses the methodology of AntiPatterns, which is a hot topic in the software development community, to analyze problems with project management. This is simultaneously the book's strength and its weakness. Antipatterns are just one tool; one way of looking at the world; one way of analyzing a situation. Another useful addition to the toolkit is always welcome and the book clearly delivers one. On the other hand, if you are looking for the unified theory that will solve all project management problems, it doesn't deliver on that. (I am still looking for that book.)
One reason the book might receive mixed reviews is that it does have a tone of irreverence towards management. For example, in the Executive Summary, it says "The primary cause of software development failure is the lack of appropriate project management." While this may be true, some project managers may not enjoy reading about it. Similarly, the book has a tendency to identify the root cause of problems as "haste, ignorance or sloth", most likely on the part of management. This may be true, but perhaps not all that helpful or enjoyable to read.
Overall, I found the book to provide a valuable perspective on software project management. The book will not solve all of the world's project management problems but that's OK with me.
Read the book and use the principles wisely.
On the other hand, reading this book adds perspective, which may be enough to help one step back from the situation and reevaluate.
In addition, since the authors reference their earlier works frequently, it might be best to read the other books first.