Answering 'It Depends' | ||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
||||||||||||
 |
[ Login/Subscribe ] | |||||||||||
 |
||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
 |
||||
 |
||||||||||||
Features
Departments
Opinion
Executive
Resources
|
Home > Opinion > Feedback
Merely chasing a standalone methodology is not going to buy you an extra hour on your project. You must empower yourself with a set of tools that give you a workbench to experiment with a bigger improvement picture in mind.
There have been many thought-provoking discussions on effective project management steered by Mark Mullaly and other Projects@Work contributors. I am quite in agreement with Mullaly’s statement that "processes that don't create or sustain value are not going to last very long," and I agree that there is no single right answer when it comes to invoking PMBOK, Prince2, Critical Path or Critical Chain as a success-mantra. As Mullaly says in Keep on Evolving (April 7, 2005), "it depends."
However, what does "it depends" really mean in this context? Is it like a product-positioning activity where you keep trying various positioning statements and eventually one will hit the jackpot for you? It might be worthwhile to stop thinking of project management in isolation.
Please login/register to read the entire article.
| |||||||||||||||||
|
Privacy Policy Contact Us User Agreement