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. I'm assuming you are at this page because you...
Project Action Principles
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 a superficial way in my projects. The one...
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 your plan. If you are going to make material...
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 about assessing and executing this change....
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.
time is of the essence when kicking off a project. you lose more time at the beginning than anywhere else. but you can prevent it by being pro-active.
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, estimates were not only not required, but were counter to...
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 alternative solutions to their problems. It could...
Sign up for the AOP Newsletter
Each week Adam writes about interesting and varied topics for Project Managers everywhere and curates useful articles, books and papers from other sources.
- The Project Manager’s “Predator Helmet”: Nine diagnostic filters for your projects
- The Hysteresis of Hysteria – The 11-Step Cycle of a System Crisis
- The Gradient of Terror – Project management and non-linear forces
- Rethinking the (Work) Breakdown Structure – Part 2.4: Summarising the pivot points
- Rethinking the Work Breakdown Structure Part 2.3: Leveraging a broader range of tools
- Adam Reads
- Agile Concepts
- Agile Documentation
- Anti-Teaming Behaviour
- Breakdown Structures
- Customer Advocacy
- Customer Service
- Customer Value
- Deliverables Management
- Gradient of Terror
- Manifesto for Action
- PAP #1
- PM Twitter Lists
- Principle-based Project Management
- Project Action Hacks
- Project Action Principles
- Project Execution
- Project Management Community
- Project Management Concepts
- Project Management Data
- Project Management Models
- Project Management Skills
- Project Management Tools
- Project Planning
- Quick Posts
- Self-Organising teams
- Software Projects
- State of Project Management
- Systems Integration