The views expressed in this article are strictly those of Max Wideman.
The contents of the book under review are the copyright property of the author.
US spelling adopted throughout.
Published here March 2016.

Introduction | Book Structure | What We Liked
Downside | Summary

Book Structure

The contents of this book are set out in two Parts of nine and seven Chapters respectively. It also includes an extensive Bibliography, all as follows:

 

1.

Introduction

Part I — THE PROJECT LIFECYCLE

 

2.

Identifying a Project

 

3.

Justification and Approval for a Project

 

4.

Getting Started

 

5.

Requirements

 

6.

Design

 

7.

Build

 

8.

Validation and Test

 

9.

Going Live

 

10.

Post-Live Realization of Changes

Part II — COMMON STRANDS

 

11.

Quality

 

12.

Planning and Execution

 

13.

HR

 

14.

Finance

 

15.

Reporting

 

16.

Benefits

 

17.

Conclusions

 

Bibliography

The book has a total of 213 pages and one Appendix and is illustrated by a number of Figures and Tables. It does not include a Glossary of Terms. The book is well written in straight forward English and, as the author explains:[4]

"This book is deliberately practical and pragmatic. It is based on the professional experience of the author covering nearly 30 years of project-related work and consulting. ... Its aim is to be of direct use to both business and project professionals [and] is written so as to be applicable to all types of project and thus uses neutral language which is slightly abstract."

However:[5]

"It is not meant to be read from cover to cover. Most readers will be at a particular stage in a project or come from a particular specialism. The relevant chapters covering that lifecycle phase and that specialism may be all that they read. That's OK — the book will still have served its purpose."

Of course, for review purposes, we did read this book from cover to cover — and enjoyed almost every page. That's because the author takes the problem of the clash between the business world and the project world head on. Indeed, we strongly recommend that the first time any one picks up this book, they should at least first read the Introduction,[6] because there the author sets the scene by explaining "The Business Viewpoint"; "The Project Viewpoint" and the effect of "The Interaction between the two worlds".

Introduction  Introduction

4. Ibid, p. xi
5. Ibid, p. Xii
6. Ibid, pp1-4
 
Home | Issacons | PM Glossary | Papers & Books | Max's Musings
Guest Articles | Contact Info | Search My Site | Site Map | Top of Page