Even the smoothest running projects will face challenges as they move toward closeout. You know the scenario .... you and your team have faced your fair share of issues on the project no project is without issues and rough spots. But for the most part, things have progressed rather well. Even user acceptance testing went off without too much of a hitch.
Now you're almost ready for implementation, and post-deployment activities and things are becoming harder to control.
This should be the easy part, right?
I call this the 'Steve Blass Syndrome' of project management (after the 1960's and 1970's Pittsburgh Pirates pitcher who was very good and then suddenly couldn't get the ball over the plate ok, so maybe I'm the only one who remembers him....).
So why would things suddenly become difficult so close to the end of successful project?
Here are a few reasons why this is often the case.
- Start-up problems with new products or new designs
- Thorough identification and agreement on all remaining deliverables
- Loss of control of the charges to the project as things are winding down people start doing 'whatever it takes' to get through the final push often damaging the project budget
- Hand-off issues in transition to tech support
Project Team Challenges
- Loss of team functionality as some members complete their tasks
- Project team members become heavily involved in startup activities on new projects
- Loss of interest in tasks such as documentation and administrative work
- Fear of no future work team members and consultants may drag their feet
- Agreement on what outstanding commitments still exist
- Absence of a clear hand-off strategy
- Change of responsible personnel at critical transition points
- Unavailability of key personnel
- Difficulty agreeing on signoff on remaining punch-list issues
That final push should be easy but it isn't. This list probably isn't all-inclusive in fact I know it's not and I welcome your thoughts and input on this. From my experience on projects that final push has become the most difficult when a few remaining issues exist. What looked like a day's work to resolve minor outstanding technical issues can sometimes becomes weeks full of effort trying to go to an agreed upon stopping point. This is often due to the customer feeling like they'll be left out in the cold if they agree to signoff and allow implementation with anything left on the table in terms of issues.
Don't miss out: Project Closeout Checklist
Likewise, there can be billing issues that remain outstanding and keep a project from coming to a swift and happy implementation and shutdown. Vendors are apprehensive about deploying the final solution if there is a hint that they might not get paid very soon for final efforts.