Elizabeth Harrin has outlined what project management means by highlighting the terms of budgetary constraints, project ownership, project scope, change management, version control, post-project reviews, risk identification, requirements analysis, understanding team culture, stakeholder analysis, motivating the team to keep performance levels high and identifying the project's critical path.
I found the requirements analysis chapter interesting. The Mental Model Mismatch has been included whereby the understanding of what the user requires should be perfectly aligned with the designer's and architect's perceptions provided communication is effective between these three individuals User --Interface--> Designer --Interface--> Architect. The chapter on risk identification is also interesting with a risk impact matrix shown as part of risk assessment. The chapter on stakeholder analysis highlights the importance of mapping each stakeholder interest and influence from where it is currently standing to where it should be taken i.e. Averse-->Uncooperative-->Indifferent-->Supportive-->Enthusiastic.
Harrin has portrayed a well-organised list of important points on what project management is really about. In addition, Harrin discusses certain PRINCE2 processes as well as making those important points more informative by bringing in examples from experience. However, a big part of the various project management methodologies the book addresses appeals to IT professionals from all over the world.