Dr. Andrew Makar is an IT program manager and is the author of the Microsoft Project Made Easy series. For more project management advice, visit the website TacticalProjectManagement.com.
Have you ever struggled with supporting a newly deployed application while managing subsequent releases? Enterprise projects and programs often have multiple releases to various countries and business units. Project teams run the risk of becoming lost in transition when the initial release is not properly transitioned to an operation support model.
In this scenario, the project team continues to work on the next release while struggling with the production support role. The project team ineffectively juggles operational activities with key project deliverables. Without defined operational roles and responsibilities, project teams endanger future releases as well suffer from role confusion. This article provides several recommendations to avoid becoming “lost in transition”.
During a recent project, an IT organization was implementing a new financial accounting package over six months with two planned releases. The first release was implemented to 1/3 of the company and the second release was scoped for the remainder of the company. The first launch was a challenged launch as the system experienced production support issues and the business partners were not comfortable that the system was stable enough to support the remaining 2/3 of the organization. As the team approached the launch decision for the second release, the business partners and the
"Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so."