IT Project Help

Ask us about our enterprise IT services! Just give a short description of your next project, and we'll see what we can do to help.
 

IT Project Blog Extras

About the Author

IT Project Blog

Kathlika Thomas Fontes, head writer of the IT Project Blog, has over a decade of business analysis and PM experience. She has managed numerous international projects and has also developed several workshops and training programs.

IT Project Blog

Current Articles | RSS Feed RSS Feed

Are You Backsliding? How To Deal With Project Setbacks

  
  
  

project setbacksThanks to our readers for all of your feedback and comments on the “Project Changes” article series. It is clearly a topic that is deliberated on by many project managers to help keep their projects running smoothly from start to finish. One topic of consideration that we covered is how to manage changes to project schedules. This sort of adjustment is often needed when project setbacks are faced or when your team experiences negative project progress. Is this issue simply a result of poor planning? What are the causes and what can be done about it?


True enough, project setbacks can be encountered as a result of inadequate preparation for upcoming project work. But even when you think everything is properly planned out, problems still arise. Here are a few tips to head off bumps in the road on your project.


Reduce Project Overload

Most intuitively, too much project work is sure to cause the very best project team to fumble their assignment. An overly aggressive project timeline leaves little room for realistic scheduling throughout planning, design, build, and testing and will increase problems encountered on a project exponentially as time passes. While it may seem the norm in certain industries, overworked resources are counter-productive at the end of the day and will only result in stress to your project’s critical path and increased recidivism. Remember to examine best- and worst-case scenarios when designing your project plan. Alleviating all slack on a timeline is not wise… think of it as your project’s built-in breathing room. It’s better to be under-budget than pressed for time come go-live.


Encourage Proactive Issue Resolution

This suggestion can truly be helpful to the health of your project. Incentivize your teammates to take ownership in the project’s overall success. What does that mean for them? Being on the lookout for issues in design or anticipating issues in build or test will enable them to help you as the project manager to effectively manage the overall project all the more. While some may frown upon project naysayers, no one should be afraid to voice reasonable concerns. After all, that’s what risk management is all about, and it will help to avoid underlying problems that may result in project setbacks.


Shore Up Communication Channels

How clear is your project’s communication plan? Are you often experiencing delays to your project timeline because resources were not properly informed about assignments they should have been addressing? If so, revisit your communication plan. This clear outline of how and when information should be shared is especially key on projects that have cross-departmental impacts. When a clear plan is laid out, you’ll find that less delay from lack of information will be encountered and your timeline will run more smoothly.


These are just a few suggestions on how to avoid common project setbacks. What setbacks do you most often encounter and how does your team face the challenge? Leave your comments below!

Comments

Poorly planned projects are doomed to have setbacks, but even a well planned projects will have set backs as you can only plan for what is foreseeable. The key is having a risk management plan. 
 
As part of the planning process the team needs to identify a list of risks that might arise, what is the likelihood of that risk happening, and what is the cost in time and money should it happen and then develop mitigation plans. If the likelihood and cost are low you would probably accept the risk and do nothing, but at least it wouldn't be a surprise if it happens. However, if the risk is low and the cost very high, or the risk is very high and cost low, the development of mitigation plans may be in order. I have been on projects where we have put assets in place, at considerable cost, we don't expect to use in the event one of the identified risks should happen. It's like buying insurance, the cost of not doing so far exceeds the cost of the insurance. 
 
The biggest mistake I see on projects is the response by the management team when a setback does occur. Instead of evaluating the new set of conditions on the ground and determining how to move forward from there, they go into the blame game and covering their behinds. The people I work with are all professionals and are doing their best, and even if a decision they made led to a setback I'm certain it wasn't intentional. 
 
You can't fix the past, you can only plan for the future.
Posted @ Friday, December 10, 2010 11:36 AM by Stephen Vohs
Thanks, Stephen for that very informative comment! Surely, planning is half the battle when it comes to successful project management and preparing for issues by documenting risks is key -- I wholeheartedly agree.
Posted @ Friday, December 10, 2010 11:54 AM by K Thomas
No matter how good the project planning and estimating were, all projects are at risk of some setbacks. It's the cost of doing projects. The knee jerk reaction is, when a project starts to slip or overrun its budget, everyone points to "poor planning" as the cause. Even this blog suggested not to remove slack in order to keep "breathing room" in the schedule. This thinking incents estimators to inflate their estimates to the 90th or greater percentile of an estimate. Anything less than that is unrealistic. Then Parkinson's Law takes effect. 
 
That is counter-productive and not good project management. Is it better to estimate at the 90th percentile and achieve it or estimate at the 55th percentile and exceed by say 10 points?
Posted @ Friday, December 10, 2010 1:50 PM by David Espina, PMP
Good points, I think Stephen touched on key areas. It is critical for the PM to protect the plan by monitoring closely risks and lessons learned throughout the life of the project. Both elements can enhance the project plan during the execution phase. Also, when setbacks do occur, communicating the issue quickly and providing the solution to the entire management team and stakeholders, is extremely important. I think a good base can be built for dealing with setbacks during the project planning phase by insuring the project team knows they will be evaluated by how quickly they respond to changes and institute corrective action. Hence, the importance of incorporating a culture for ongoing risk management and lessons learned to protect the plan.
Posted @ Friday, December 10, 2010 1:52 PM by Paul Ladouceur
Interesting input, David and Paul. Thanks! @Paul - very intriguing thought to evaluate team members or even stakeholders based on how agile (responsive) they are to necessary changes. Great point!
Posted @ Friday, December 10, 2010 2:05 PM by K Thomas
For those of you wondering what Parkinson's Law is, I just got some clarification from David Espina via LinkedIn: 
 
"Cyril Parkinson published a humorous draft on his observations on the expansion of work. It has been some time since I read the specifics, but it was an observation made regarding the size of government, I believe. He noticed an ongoing growth in the size and expense of government but with little growth on government services. In sum, Parkinson's Law says work expands to fill up time. In a project estimate, all tasks have a minimum, a maximum, and a most likely value. if you plotted this, you would have a triangular distributed histograph. If you priced your project at the most likely value, it would fall somewhere in the 40th to 60th percentile of that distribution, meaning the PM would have between 40% to 60% chance of achieving it. When a PM is rated based on meeting budget and cost, there is an incentive to price your project much higher than the 40th to 60th percentile. You want to increase your odds, so you price at the 80th to 90th percentile. People will procrastinate, op tempo decreases, they'll use every bit of runway given to them. I have observed this phenomenon to take place. 
 
All this does is artificially improve the perceived performance of the PM while raising costs for the customer. Not good..." 
 
I love that there's a name for this.
Posted @ Friday, December 10, 2010 2:44 PM by Gabrielle Guerrera
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics