I spent twelve years in the Air Force. By the end, I was an application developer and database designer working for the Chief of Air Force Materiel in Canberra, where the Air Force’s major and minor projects were managed. This was the mid-1980s, early in my career and before the business cases I’ve written about here.
The project management method was called Spectrum. Like most standards of its kind, it was put out by Defence rather than the Air Force. It took up two shelves of a bookcase, in green binders.
They mostly sat on the shelf.
I wasn’t a project officer on any of the major projects, so I can’t say how well it was enforced at the time. The organisation was changing, and I suspect Spectrum belonged to an earlier way of managing projects. It remained the formal doctrine, but I couldn’t tell from those binders how much of it was still reflected in everyday practice.
That distinction has stayed with me. A method can remain formally current without telling you how projects are being managed.
When an organisation changes, how does it know whether its established project management standards still describe the way projects are actually run?
Want more like this? Rick writes about the go/no-go decision: for the people who assess business cases, and the founders who have to make them.
All writing