Home
About Us
Site Map
Products
Services
PMP® Certification
PM Tips & Tricks
PM Tools & Techniques
Links
Contact Us
BLOG

 

 

Intervention Planning Deliverables

"In this phase, you are going to either update the project deliverables that were identified in the previous phase or create new ones. Information may be inaccurate or missing in these deliverables. This could have been a source of the problem in the first place. You may also need to create any of the deliverables on the 'must have' list if they do not exist. These documents feed the generation of a new set of deliverables for the project rescue."

Rescue Approach

"This deliverable mirrors the project charter and is intended to persuade everyone involved in the initiative to contribute to the project rescue. This document should show the cost of several different approaches and recommend a direction in which to proceed. It should also identify processes and procedures for the project rescue initiative."

Prioritized Functionality

"This is a list of the functions or units of work that must be completed to satisfy the rescue objectives with associated priorities and 'must have' dates. You will need to work with the sponsors and several stakeholders to go through the original project charter and business requirements to determine what is critical or not, and in what sequence it should be delivered."

"Some stakeholders will want everything on the requirements list, but remember that the alternative is to deliver nothing. If you are new to the project in the role of the rescue manager, you will be better positioned to negotiate in these meetings as you cannot be blamed for past problems on the project."

Rescue Project Plan

"This is a detailed project plan that facilitates regular walkthroughs with different members of the extended project team. This may require several versions of the plan. One version could show the major activities and milestones using a monthly or quarterly time scale so that the entire plan fits onto a page. This document helps to position the business user's understanding by providing meaningful reference points. The other view of the plan could show activities broken into days, so that an early morning meeting can be used to track the progress of the day before. The plan could also be updated at the end of the day to ensure enough progress was made before team members go home."

Architectures

"An integrated architecture is needed to show how all the different pieces of the solution fit together - and whether they actually do fit together. Architectures are useful for understanding and explaining the big picture, to support building the details into the project plan, and to help in calculating the resource costs."

"Three architectures are of interest in this phase: the Application architecture, the Data architecture, and the Technology architecture."

Analysis and Models

"This deliverable analyzes the business requirements and produces models (for example, object models, storyboards, creative mocks) to support detailed design and specifications for the solution. This deliverable can be produced in parallel to the architectures."

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.