Project Management

Misunderstood, Underestimated...or Both?

Richard McKenzie, PMP
linkedin twitter facebook print Request to reuse this   Work Breakdown Structures (WBS)  
Is the project misunderstood, underestimated…or both?
 
(S)ituation
Consider the following hypothetical project management scenario, which may seem all too familiar, and is written in the “S.O.A.R.” format. Let’s say you are a project manager in the PMO or a consulting PM assigned to an IT project with a specific goal such as implementing a key ERP module, a data warehouse, a data center move or implement a new task automation tool. You are simultaneously nervous and excited and know you can do this. So far, you like your team, and the sponsor appears supportive enough. As a bonus, the technical lead and sponsor collaborated on a statement of work that you easily convert to a charter. Good to go, right? Maybe, maybe not…
 
Set-up for (O)bstacles
You are told you are to implement a turn-key task automation tool. You reread the charter and stop by the sponsor’s office and ask if he or she “just wants the automation tool implemented” or if there are other aspects to the project. Your sponsor says it’s clear enough, “We’re putting in the new tool.” Now you are a bit concerned, but don’t know yet exactly why. You have some random thoughts about training, process inputs and outputs, possibly even envision a workflow.
 
Next, you schedule the first two-hour WBS session with…

Please log in or sign up below to read the rest of the article.

ADVERTISEMENT

Continue reading...

Log In
OR
Sign Up
ADVERTISEMENTS

"Humanity has advanced, when it has advanced, not because it has been sober, responsible and cautious, but because it has been playful, rebellious and immature."

- Tom Robbins

ADVERTISEMENT

Sponsors