Project Management

How do you know that your project plan is fully baked?

From the Easy in theory, difficult in practice Blog
by
My musings on project management, project portfolio management and change management. I'm a firm believer that a pragmatic approach to organizational change that addresses process & technology, but primarily, people will maximize chances for success. This blog contains articles which I've previously written and published as well as new content.

About this Blog

RSS

Recent Posts

Leading Through Crisis Means Leading Through Context

"It's the end. But the moment has been prepared for." - retirement lessons from the Doctor

Just because they are non-critical, doesn't mean they are not risky!

Just because they are non-critical, doesn't mean they are not risky!

How will YOU avoid these AI-related cognitive biases?

Categories

Agile, Artificial Intelligence, Career Development, Change Management, Communications Management, Decision Making, Governance, Hiring, Kanban, Lessons Learned, Personal Development, PMO, Portfolio Management, Project Management, Resource Management, Risk Management, Risk Management, Schedule Management, Scheduling, Tools

Date

linkedin twitter facebook Request to reuse this  

Categories: Project Management


“It’s the question that drives us, Neo. It’s the question that brought you here. You know the question, just as I did.” 

No, it’s not “What is the Matrix?” but rather, how do you know when your team has done enough project planning to feel confident that commitments can be made to your customer?

Isn’t there an app for that?

Wouldn’t it be wonderful if there was the equivalent of a meat thermometer that could let you know if further planning is required or if you are at risk of realizing business value shoe leather?

There is no expert system which codifies the shared knowledge of the world’s project management experts to help you know when enough is enough. The essence of projects is uncertainty, and it is that uncertainty which stymies the best efforts of project teams to find the sweet spot.

While we may not be able to perfectly time it, here are a few tell-tale signs which could tell you that it’s either too soon or that you may have gone too far.

When should you put your project plan back in the oven to bake some more?

  • When more than just your risk averse team members are expressing concerns
  • When you are not sure that you have identified and assessed needs and wants of all key stakeholders
  • When there are still some shaky assumptions supporting the foundation of your plan
  • When a second (or third) pair of fresh eyes hasn’t reviewed key elements of the plan
  • When resource estimates are based on the work being done by very specific individuals and their availability is still questionable
  • When each day brings new information resulting in meaningful shifts to approach or estimates

When is your project at risk of getting burnt from too much planning?

  • When team members are dwelling on details of activities which are in the distant future
  • When only your risk averse team members are feeling concerned that it’s still not quite ready
  • When a variety of different techniques support the estimates where commitments are going to be made
  • Once response plans have been successfully implemented for all key risks
  • Once commitments are in place for all key resources
  • When the number of new revelations impacting estimates is few and far between

Professional chefs are able to use a dash of this or a splash of that while novice cooks must practice strict adherence to recipes. With experience, our intuition for knowing when we are ready to get started improves. However, introduce sufficient change into the scope or context for a project and even seasoned project managers will need to fall back on signs such as these.

(Note: I baked this article in February 2015 on my personal blog, kbondale.wordpress.com)


Posted on: August 23, 2018 06:59 AM | Permalink

Comments (24)

Page: 1 2 <prev

Please login or join to subscribe to this item
avatar
Anish Abraham Privacy Program Manager| University of Washington Auburn, Wa, United States
Good one, and thanks for sharing Kiron!

avatar
Henry Hattenrath Project Consultant| Tectonic Engineering MSA LLC New York, Ny, United States
Thank you Kiron!

Since we are baking the project plan, there should be historical metrics used by the Owner’s Planning Department to gauge temperature and time when the project is ready for initiation or where continued resistance indicates the project will not reach confidence level for initiation. The metrics can include duration spent in planning, quantity of revisions to the project plan, and the acceptable fluctuation thresholds in scope, budget, and schedule from the original proposed plan. If the planning passes the metric thresholds individually or combined, the projects should be shelved.

Henry

avatar
Girija Ramakrishnan Chennai, Tamilnadu, India
Too good post, Kiron. Thanks !

avatar
RAJESH K L Project Manager, PMP| Bharat Electronics, Bengaluru, India Bengaluru, Karnataka, India
Thanks for sharing

Page: 1 2 <prev

Please Login/Register to leave a comment.

ADVERTISEMENTS

"If you pick up a starving dog and make him prosperous, he will not bite you. This is the principal difference between a dog and a man."

- Mark Twain

ADVERTISEMENT

Sponsors