Agile

The Magic Triangle, or Triple Constraint, is widely seen as the fundament of project management. Controlling time, money and quality is a basic rule for project-governance. There are several variations, e.g. the Devil’s Quadrant.

This concept is generally accepted without much thought or discussion. But should it be? Is (a variant of) the Magic Triangle always useful?

It is quite common for consultants and trainers in the area of project management to claim they have a way to deliver a project on time and on budget. Ever some suppliers of PRINCE2 training will advertise with this promise.

Delivering on time and on budget is not a goal. Even worse: this attitude will almost certainly make a project fail.

There are several ways to look at organizations and the behaviour of people within organizations. Years ago, I developed a model that has always served me well. When looking at resistance to change and failing projects, I found that it is often about different cultures within organizations. ...

AXELOS has published an extension of PRINCE2: PRINCE2 Agile. Many think they are two polar opposites, PRINCE2 - symbolizing control, accountability, order – and agile – symbolizing self-organization and equality. And they are polar opposites. But for very different reasons. They are opposites because real, proper PRINCE2 is very agile and the Agile movement is based on old-fashioned ineffective Command and Control.

Part of the solution or part of the problem? The IT industry promotes SCRUM as the best way to reach better results in projects. But is that really the case? Or this just a new name for something that has always been there? Or is there a revolutionary new view on IT development? As far as I am concerned the name pretty much indicates what the real issue is that will not be solv ...