Effective Work Breakdown Structures

This book is short and sweet. It is easy to read and to understand. It gives full details about WBS and it is a real help for PM.

Clear, concise, and to the point. I would still like to study some effective examples of fully developed WBSs for commercial construction.

I've just bought this book last month while implementing SAP Project system. It is very helpful for me to design suitable WBS in my company.

A total of 100 pages, which would seem a bit pricey, but in the 100 pages Haugan does a very competent job of covering the subject. Most of the critical concepts in PM are really pretty basic, and most projects and PM texts fail on understanding and executing on those basic concepts. This book is very clear and succinct on the basics of WBS. I very much admire Haugan's approach. I expect my copy will be around for a long time, marked-up, with yellow sticky-notes protruding out.

Of the three books that focus solely on work breakdown structures this is the most complete. The other two are "Nuts and Bolts Series 1--How to Build a Work Breakdown Structure" by Carl L. Pritchard, and "Project Management Institute Practice Standard for Work Breakdown Structures". The burning question is how do they compare and which is best. For a no-nonsense and pragmatic book the "Nuts and Bolts Series" book wins. It has the distinction of being the first book on the subject, and is one that I used as a reference for the past 4 years. If you are planning to certify as a PMP, your best bet is the PMI Practice Standard, because you're sure to encounter exam questions that are based on that book. However, if you want a comprehensive book that covers every facet of principles and practice, this is the book to get.What sets this one apart from the other two (all other factors being equal) is the clearer descriptions of the principles, and the checklists. I also like the way that the author goes deeper into details about how to align the WBS to various project types (product-, service- and results-oriented projects), and the more complete life cycle view that this book provides. As an aside, a results-oriented project, previously mentioned, is a project such as organizational change management, which doesn't produce a tangible deliverable in the same manner as, for example, a software development project does.To put into context the comparison among the three books, I favor this one because of personal preferences. Each merits, in my opinion, equal value, and any of the three will give you the knowledge necessary to develop a work breakdown structure.