Category: Project Action Principles

You’ve probably read the keystone article about the 5 Project Action Principles, and one or more of the pillar articles that describes each principle in more detail. If not then see the references at the end of this page....

The concept of ‘Deliverables Management’ has been present during much of my Project Management life but I’ve (almost) never seen any detailed codification of what this means or how to use the concept in anything more than...

Following on from the initial post on Project Acceleration, this post covers the second aspect of accelerating any project, which is to have a precise and current understanding of your project’s status and outlook against...

Last post was a short clarification of the scope and purpose of the initial post on Project Acceleration, This post covers the first key aspect of accelerating any project, which is to have a plan for how you are going to go...

This short post clarifiies the objective of the Project Acceleration series of posts. It outlines three types of Project Acceleration activity and identifies the Change Request type as the objective of this series.

the end result of a project is not the technical components created by a bunch of technologists, it is the value created by the end customer who puts that capability to use. It’s so easy for that to get lost along the way, as the exigencies of real-world project delivery strike the project. But if the value is not recognised and maintained all the way through. The secret is simple: discipline and focus

The “Project Action Principles” (PAPs) most likely were triggered by the #noestimates dialog on Twitter a couple of years ago. The proposition behind #noestimates was that in modern agile software development,...

The Paradigm Trap A “paradigm trap” is a situation in which people, teams or organisations can’t think outside a particular paradigm that they have been using. This “trap” therefore actively prevents them finding...