How much longer will the project take? Let’s be realistic. In an article at PM Hut, the timing issues of project management are put into perspective. In sum, nothing on the planet is a zero-time activity. And yet, we often hear co-workers and associates use that flinch-worthy phrase “I just have to…” Here’s how this PM Hut blogger states it:
Well, you know what they say: in any software project, 90% of the work is completed in the first half of the schedule. To complete the rest 10%, it requires the rest half of the schedule, plus another 50% schedule overrun, plus x extra resources, everyone working overtime and oh yeah, we’ll ship the documentation later because we were focusing on delivering the functionality… you get the point.
To be realistic, we have to stick to our ABC’s: Always be Collecting. In other words, it’s the tunnel-vision of being involved in any project than can blindside even a seasoned taskmaster. Staying aware of project metrics and other pertinent information can help us keep our heads out of the sand. Collecting data can help us recognize when a problem is really just a fact that must be dealt with.
That brings us to another point: scope. PM Hut suggests this word be used in place of the I-just-have-to’s. Sometimes the best way to manage a project snag is to know when to keep over-ambitious plans and the temptation to use unnecessary resources at bay. One could think of recognizing scope as a preemptive approach to the ABC method.
And of course, we all know Murphy’s Law – about the most realistic approach to any undertaking. Everybody loves to cite Murphy’s Law when something goes wrong, so why don’t we start to take the guy seriously? By accounting for problems in advance, we can be realistic about finishing tasks or projects in our work lives and personal lives alike.
Read the full article here: http://devops.com/blogs/organizational-dysfunction-the-original-vulnerability/