In managing a project or program, we start with an objective, work in the details, get buying, put together a schedule, and implement. Of course, that is a very simplified version of what happens in project and program management but what I’m trying to say is that in the process of doing all that, we are making assumptions. At each stage, assumptions are made that are carried through to the next stage of a project or program. Given that these are the roots of where we may be at any given time on the project or program, what happens if we have made the wrong assumptions?

Assuming Incorrectly
Sometimes, for one reason or another, some incorrect assumptions have been made. Whether there were simply not enough information, not enough thought, not enough input from stakeholders, or some other reason, some underlying assumptions were simply incorrect and we need to make adjustments. While making the adjustments may be difficult, I think the most difficult thing is discovering that the wrong assumptions were made and admitting - collectively, not just the project manager - that the mistake was made. Only this kind of personal accountability across the project can pave the way to move forward on a sounder basis of assumptions.
The Assumptions Were Correct But Now They Have Changed
It may be that the assumptions made at each stage of the project were correct at that time. The problem is that business conditions change, the economy changes, markets change, tastes and preference change, people change, and proccesses change. All of this change brings up a key point of our assumptions. Whenever we make our assumptions, we take a risk. One of the corner stones of professional project management is the handling of risks in our risk management practices. One of the best things we can do is thoroughly review every assumption that is being made at each stage of the project. Only by so doing can we create a proactive way of recognizing that what we assumed has now changed and that we need to change course on the project or program.
We always need to watch what we assume but the reality is that we need to assume something in order to move forward. It is important for us to carefully document our assumptions and make them part of our risk management effort. We need to be proactive by monitoring not only progress on our projects but changes in the conditions upon which our project was based. We need to monitor our assumptions, recognize when changes are occuring, be honest with ourselves and others about these changes, and then take the appropriate actions.
______________________
John Reiling, PMP
Project Management Training Online
Lean Six Sigma Training Online






3 responses so far ↓
1 pawelbrodzinski // Jan 7, 2009 at 7:45 am
The biggest problems with most assumptions we make is that we make them unconsciously. E.g. a PM thinks the client will act the same way as the previous one. A surprise is they have much more formalized process and acceptance tests take 3 months instead of 3 weeks. A developer creates UI the same way he used to, but this time the client expects something more fancy. Unfortunately there was nothing about that in requirements because that was client’s assumption. The list can go on and on. We all know a lot of examples.
To check all those assumptions we have to be conscious we’ve made them. This is the place where we usually fail.
2 Project Management Blog Post Review 2 | Project Management Guide // Jan 9, 2009 at 10:19 am
[…] changing - it just took time to come to light. John Reiling has a post at the PMCrunch blog, Check Your Assumptions, that discusses this in more […]
3 Avoid Unconscious Assumptions // Dec 16, 2009 at 8:31 pm
[…] management. Since software projects and business requirements are ever-changing we should regularly check if our assumptions are still good. But first of all we should try to make them consciously. This definitely […]
You must log in to post a comment.