So Little Time, So Much To Do!

Here’s the first part of the next series of five abstracts from articles about the Top 10 Obstacles to Project Success from the MüTō Performance Corp. survey many of you participated in a few weeks ago. To read the Full Article click here!

And now, we bring you the most recently disquieting subject of a Challenging Schedule!

One of the interesting changes between last year’s survey and this year’s, is the movement in the obstacle we know as the challenging schedule. In 2008, our respondents claimed it as obstacle #8, this year over 78% of our respondents voted it obstacle #2!

There may be many reasons why this obstacle is critical for most of our respondents, and some may seem obvious. Project managers are feeling the pressure to finish projects on-time, but by and large, they feel the time allotted is insufficient.

There’s only one true definition to this obstacle and that is that the date for delivery of the project’s solution makes it difficult to deliver on time. By definition however, according to any reasonable project process, the date of delivery of a project is a function of the project’s planning process.

Sounds good. This may have been the case last year, but this year, our respondents are claiming that the date of a delivery of a project is actually a requirement instead!

Comment away!

There's Nothing Creepy About Scope Creep!

When 83% of our survey participants responded that scope creep reared its ugly head on almost every one of their projects, we immediately said, "here we go again!" Scope creep is the scapegoat for most of our troubles with projects. Our analysis showed that there are two types of changes to the scope of a project; those that are legitimate, and those that are illegitimate.

Each has its own impact, causes, early detection symptoms, and solutions. Suffice to say, that illegitimate scope creep must be stopped, and legitimate scope creep must be managed effectively otherwise, the obstacle will manifest! Legitimate scope creep cannot possibly damage your project, so let's be careful about blaming it for our project's demise.

We may not like where the blame winds up sticking.

For the FULL ARTICLE, CLICK HERE!

For a complete listing of MüTō Articles, CLICK HERE!