Intervention Execution Deliverables"The bulk of the deliverables produced during the project rescue are done in Phase 2. If the planning is done well, this phase essentially implements the solution, producing deliverables that monitor the situation, track progress, identify problems, and produce resolution. The deliverables in the previous phase also need to be maintained to reflect any changes on the ground."
Status Reports"There are several types of status reports. One type is intended to be a permanent record of the project, another is intended to convey information to the project team, and a third format serves as a daily discussion document."
Issues Log"This issues log is one of the most important documents during a project rescue initiative. It captures all the observations from the extended team and uses priority codes to differentiate between activities that need to be done to fulfill the rescue and those that can be phased out."
"Change logs should be included to document all changes to scope along the way."
Revised Project Rescue Plan"This is a daily update of the rescue project plan that was created in the previous phase. This needs to be updated with percentage complete or estimates to complete frequently (for example, at end of day)."
Official Signoffs"During a project rescue, it is sometimes difficult to get that final signoff from a stakeholder and owner. This could occur because of a lack of availability, final nervousness, or simply fear. It would be awful to be ready to deploy an application but miss the delivery date by days because a signature is not forthcoming."
"You need to establish the process for getting a timely signoff. Perhaps an oral acceptance is permitted. This would certainly support a faster process, but what record is there of such a notice being given. Project rescue managers need to document the acceptance process and detail what is considered to be acceptable, and distribute this in an e-mail to the stakeholder. What do the corporate lawyers say is acceptable?"
Deployment Kit"Deploying the solution is a project in itself. The components include the following:
- Deployment plan Also drives the business requirements and test plans.
- User Training plan Identifies the type of training that is available, the users that require it, and a timeline when they are expected to receive it. Training is required for users of the solution, the technical team that supports the solution, and the help desk that is going to respond to user problems.
- Contact list This is a list of all the key contacts and how to reach them around the clock during the deployment phase. This information will be required, so ensure that it is accurate and that the people on the list are well rested before the deployment process begins.
- Letter to users Should come from the project sponsor and be sent to everyone affected by the launch, explaining the detailed process for the deployment.
- Contingency plan Build and test the process that will be followed if the deployment does not go according to plan. The plan should identify the communication that is needed and the steps that need to be followed to make a decision to implement the contingency plan instead of the solution. The plan should also identify the cutoff time for when this needs to be started. This is an undesirable situation and, let's hope, you won't need to invoke it.
- Post-launch test The system may have worked during the final test, but test it again after deployment and before the world sees it to ensure that nothing was missed. You may want to use a streamlined version of the acceptance test so that there is enough time left over after deployment to do this. The major risk factors involve ensuring that all the components of the application have been deployed into production and that the environment is properly configured."
Acceptance Results"This deliverable collects all the results from the different tests, especially the acceptance tests, to demonstrate the quality of the application. This package needs to be reviewed with the sponsors when you are getting signoff from them."
The above is an excerpt from a book written by Sanjiv Purba and
Joseph Zucchero, published by McGraw-Hill/Osborne, 2100 Powell Street,
10th Floor, Emeryville, California 94608 U.S.A. Sanjiv has over 20
years of experience managing large projects and many years engaged in
rescuing ailing projects.