Archive for the “Exploding the project myths” category
Exploding the project myths – 6
by jed simms on June 29, 2011
Projects don’t deliver outcomes or benefits. They only deliver outputs Projects are commissioned to deliver business benefits. Benefits are realized in the business and are at least partly dependent on business endeavours not entirely within the control of the project (…)
Exploding the project myths – 5
by jed simms on June 23, 2011
Projects exist to solve problems There are definitions of projects that assert that ‘projects exist to solve problems’. Many project methodologies start with “The problem statement”. This is too narrow a view of projects and leads to sub-optimal behaviour and (…)
Exploding the project myths – 4
by jed simms on June 15, 2011
‘Time – cost – specification’ — you can only have two out of the three ‘Time-cost-specification’ – is called the ‘iron triangle’ for projects. The goal is to deliver any project on time, on budget, and to specification. However, it (…)
Exploding the project myths – 3
by jed simms on June 8, 2011
Myths – 3 Project management methodologies directly control the results delivered Business and portfolio management’s reaction to continuing poor project results is invariably to improve the project management tools and methodologies used in the organization in the belief that this (…)
Exploding the project myths – 2
by jed simms on June 1, 2011
Myth 2 The project management (and other) standards are ‘best practice’ Bodies of knowledge (PMBOK, BABOK) and methodologies (Prince2, MSP, et al) have been developed and widely promoted as ‘best practice’. Many project professionals firmly believe that if you just (…)