Book Structure
The book contains thirteen sections each with a number of chapters ranging up to six in each for a total of 41. The chapters are generally short and to the point, often based on previous material that Harvey has written. He claims that the book may be read from cover to cover as a complete guide to practical project management. If you decide on this course, the sections you will cover in order are:[1]
- Setting up the Project management Operation
- Getting started
- Scheduling
- Resource and Workforce Management
- Budgeting and cost control
- Risk management and Contingency
- Maintaining the Plan
- Performance Measurement
- Project Portfolio Management
- Project Management, Enterprise Project Management and Enterprise Resource Planning
- Project Management and Professional Services Automation
- Tools of the Trade
- Making Project Management Work
However, in the Preface, Harvey describes how certain chapters may be selected to satisfy various types of information seekers. For example: For those looking to understand the basics, a subset of 15 chapters is recommended. For specific focused topics in the style of editorials, 10 are recommended. For in-depth topics disclosing the "finer points", another 11 are listed and, finally for a few way-out subjects, three are identified.[2]
True, that as a result of this structure, there is some duplication, but we did not find this objectionable. As Harvey observes:[3]
Project management is a many-faceted discipline. It will usually involve project scoping, task planning and scheduling, resource planning and workforce management, budgeting and cost control, risk and contingency management, change management, and project closeout. And while we are doing this, we will need to apply skills in maintaining quality, avoiding scope creep, and managing extensive and sensitive communication, with numerous stakeholders, in widespread locations.
Actually, we've yet to come across a project manager that actually does all of these things, at the same time, on the same project, at least without a lot of assistance. But Harvey goes on to say:
All of these skills that are specific to project management must
be applied by individuals who are also endowed with the more traditional management
skills:
- The ability to lead and work with others
- The ability to converse with technical experts in their applied field
- The ability to interface with operations, finance, and human resources personnel
- The ability to participate in strategic and operational planning
- The ability to mentor, negotiate, and make decisions.
That is some competence profile, but then he gives us some comfort by adding:
While the breadth of project management is indeed wide, the subject really isn't that complex. Failures in project management are more likely to come from trying to take excessive shortcuts than from not mastering the requisite knowledge.
Cherish that thought!
1. Levine, H.A., Practical Project Management, John Wiley & Sons, Inc., NY, 2002, pp v-vii
2. Ibid. pp xv-xvii
3. Ibid. p xiii-xiv
|