<<Project Name>>

Master Project Plan

 

Customer Name

 

 

 

Directions for using template:

Read the Guidance (Arial blue font in brackets) to understand the information that should be placed in each section of this template. Then delete the Guidance and replace the placeholder within <<Begin text here>> with your response. There may be additional Guidance in the Appendix of some documents, which should also be deleted once it has been used.

 

Some templates have four levels of headings.  They are not indented, but can be differentiated by font type and size:

You may elect to indent sections for readability.

 

 

 

 

Author

 

Author Position

 

Date

 

 

 

 

 

Version: 1.0

 


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2002 Microsoft Corporation. All rights reserved.

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

Microsoft and Visual Basic are either registered trademarks or trademarks of Microsoft in the United States and/or other countries.

 

 

Revision & Sign-off Sheet

Change Record

Date

Author

Version

Change Reference

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Reviewers

Name

Version Approved

Position

Date

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Distribution

Name

Position

 

 

 

 

 

 

 

 

 

Document Properties

Item

Details

Document Title

Master Project Plan

Author

 

Creation Date

 

Last Updated

 

 


 


Table of Contents

Master Project Plan Summary

Work Breakdown Structure

Individual Plans

Development Plan

Test Plan

Communications Plan

Microsoft Support Plan

Operations Plan

Security Plan

Availability Plan

Capacity Plan

Monitoring Plan

Performance Plan

End-User Support Plan

Deployment Plan

Training Plan

Purchasing & Facilities Plan

Pilot Plan

Budget Plan

Tools


 

 


 

[Introduction to the Template

 

Description: The Master Project Plan is the document into which all subsidiary plans (development, test, etc) are synchronized and presented together as a single plan. It is important to distinguish this plan from the Microsoftģ Projectģ .mpp file, which contains tasks, resources, and schedules, but not the qualitative information contained in many of the subsidiary plans. The types of subsidiary plans included in this master plan will vary depending on the scope and type of project. In MSF, the Master Project Plan is a collection (or ďroll upĒ) of plans developed by the various teams (Program Management, Development, etc) and not an independent plan of its own. It usually contains summaries of each of the subsidiary plans. However, depending on the size of the project, some subsidiary plans may be entirely rolled into this document.

 

Justification: The benefit of presenting these subsidiary plans as one plan is that it:

 

 

The benefit of having a plan that breaks into smaller plans is that it:

 

 

{Team Role Primary: Program Management is accountable for delivering the Master Project Plan by ensuring that all teams have developed and submitted the necessary plans and that those plans are of acceptable quality.

 

Team Role Secondary: All team roles are responsible for developing the plans for their specific functional responsibilities and reviewing the consolidated Master Project Plan to ensure it is executable.}]

 

 


 

Master Project Plan Summary

[Description: The Master Project Plan Summary section provides a quick overview of the Master Project Plan, including a general description of what subsidiary plans are included.

 

Justification: Some readers may need to know only the highlights of the plan, and summarizing creates that user view. It also enables the full reader to know the essence of the document before they examine the details.]

<<Begin text here>>

 

Work Breakdown Structure

[Description: The Work Breakdown Structure section identifies the specific work required to conduct the project, expressed in tasks and deliverables and the relationships among those tasks. The work breakdown structure includes both management and technical activities, and lists all work required of all participating entities (Microsoft, Partners, Customer). The work breakdown structure can exist at multiple levels of detail. The WBS is often expressed in graphic form.

 

Justification: The Work Breakdown Structure (WBS) is the basis for all resource, schedule, and budget planning.  A quality WBS creates clarity and focus for all team members, and provides the detail necessary that leads to individual work accountability.]

<<Begin text here>>

 

Individual Plans

 

Development Plan

[Description: The Development Plan section provides a summary of the development planís key elements. This summary should include information about the development objectives, overall delivery strategy, and key design goals. Other important aspects of the Development Plan may also be included here based on need (e.g. development standards and guidelines).]

<<Begin text here>>

 

Test Plan

[Description: The Test Plan section provides a summary of the test planís key elements. This summary should include information about the testing objectives, overall test approach, expected test results, and test deliverables. Other important aspects of the Test Plan may also be included here based on need (e.g. key test responsibilities, testing procedures, etc.).]

<<Begin text here>>

 

Communications Plan

[Description: The Communications Plan section provides a summary of the communication planís key elements. This summary should include information about the overall communication objectives, any sensitivities or confidentialities that must be accommodated, and key communication subjects and audiences for both internal and external communications. Other important aspects of the Communication Plan may also be included here based on need.]

<<Begin text here>>

 

Microsoft Support Plan

[Description: The Microsoft Support Plan section provides a summary of the support planís key elements. This summary should include information about the support objectives and how those requirements will be satisfied in the operational environment. Other important aspects of the Microsoft Support Plan may also be included here based on need.]

<<Begin text here>>

 

Operations Plan

[Description: The Operations Plan section provides a summary of the operation planís key elements. This summary should include information about the operational objectives, operations infrastructure, skill requirements, and key operational activities. Other important aspects of the Operational Plan may also be included here based on need.]

<<Begin text here>>

 

Security Plan

[Description: The Security Plan section provides a summary of the security planís key elements. This summary should include information about the security objectives and an overview of management, operational, and technical control processes. Other important aspects of the Security Plan may also be included here based on need.]

<<Begin text here>>

 

Availability Plan

[Description: The Availability Plan section provides a summary of the availability planís key elements. This summary should include information about the availability objectives and goal and an overview of how the hardware and software availability will be maintained. Other important aspects of the Availability Plan may also be included here based on need.]

<<Begin text here>>

 

Capacity Plan

[Description: The Capacity Plan section provides a summary of the capacity planís key elements. This summary should include information about the capacity objectives, users, loads, growth, and monitoring. Other important aspects of the Capacity Plan may also be included here based on need.]

<<Begin text here>>

 

Monitoring Plan

[Description: The Monitoring Plan section provides a summary of the monitoring planís key elements. This summary should include information about the monitoring objectives and the key monitoring processes (anticipating, detecting, diagnosing, etc). Other important aspects of the Monitoring Plan may also be included here based on need.]

<<Begin text here>>

 

Performance Plan

[Description: The Performance Plan section provides a summary of the performance planís key elements. This summary should include information on the performance requirements and the overall objectives for meeting those requirements as well as the key tools, infrastructure, and methodologies used to maintain performance. Other important aspects of the Performance Plan may also be included here based on need.]

<<Begin text here>>

 

End-User Support Plan

[Description: The End-User Support Plan section provides a summary of the end-user support planís key elements. This summary should include information about the end-user support objectives, the usability requirements, how those requirements will be satisfied in the operational environment. Other important aspects of the End-User Support Plan may also be included here based on need.]

<<Begin text here>>

 

Deployment Plan

[Description: The Deployment Plan section provides a summary of the deployment planís key elements. This summary should include information about deployment objectives; the scope, strategy, and schedule for deployment; and describe the site installation process. Other important aspects of the Deployment Plan may also be included here based on need.]

<<Begin text here>>

 

Training Plan

[Description: The Training Plan section provides a summary of the training planís key elements. This summary should include information about training objectives, the specific training requirements, the training schedule, and training methods. Other important aspects of the Training Plan may also be included here based on need.]

<<Begin text here>>

 

Purchasing & Facilities Plan

[Description: The Purchasing & Facilities Plan section provides a summary of the purchasing and facilities planís key elements. This summary should include information about the purchasing requirements and the objectives and plan to fulfill those requirements. It should also include information about the facilities requirements. Other important aspects of the Purchasing and Facilities Plan may also be included here based on need.]

<<Begin text here>>

 

Pilot Plan

[Description: The Pilot Plan section provides a summary of the pilot planís key elements. This summary should include information about the pilotís scope and success factors, transition plan, and the process used to evaluate the pilot. Other important aspects of the Pilot Plan may also be included here based on need.]

<<Begin text here>>

 

Budget Plan

[Description: The Budget Plan section provides a summary of the budget planís key elements. This summary should include an estimate of the total budget and estimates for each project (or sub-project) required to deliver the solution. This summary can also include a listing of the key cost areas (hardware, software, etc). Other important aspects of the Budget Plan may also be included here based on need.]

<<Begin text here>>

 

Tools

[Description: The Tools section lists and describes the tools that can assist the project in the detailed planning process. These may include forecasting and budget tracking tools.]

<<Begin text here>>