<<Project Name>>

Budget 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

Budget Plan

Author

 

Creation Date

 

Last Updated

 

 


 


Table of Contents

Summary

Objectives

Project Estimates

Project Details

Project One

Estimated Timeline

Financial Plan

Project Assumptions

Project Risks

Project Two

Estimated Timeline

Financial Plan

Project Assumptions

Project Risks

Cost Areas

Hardware

WAN Circuits

Software

Development Environment Hardware and Software

Contractors

People

Training

Communications Development


 

 

 

 


 

[Introduction to the Template

 

Description: The Budget defines the solution’s estimated cost to the organization. It may provide information at multiple levels of detail – for the overall solution and for each project or sub-project required to deliver the solution.

 

Justification: This plan provides the cost information necessary for business managers to approve the investment in the solution. This plan also helps to constrain over-spending, as it outlines how much will be spent and on what.

 

{Team Role Primary: Program Management is responsible for the Budget Plan. They draw from the requirements documents and physical design to determine the cost of developing and delivering the solution. They are responsible for ensuring that all the cost areas identified in this document are estimated.

 

Team Role Secondary: Product Management must be literate on the budget to communicate this information to the customer. This will enable them to set expectations appropriately, balancing cost with the vision and benefit of the solution.}]

 

 

 


 

Summary

[Description: Provide an overall summary of the contents of this document.

 

Justification: Some project participants 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>>

 

Objectives

[Description: The Objectives section identifies the objectives of the financial approach to the solution. These objectives may include 1) providing a flexible, managed infrastructure that supports growth and 2) lowering the overall cost of computing across the enterprise by providing a flexible managed infrastructure across the business units. The objectives defined in this section should be created specifically for the customer’s situation.

 

Justification: Identifying objectives signals to the customer that Microsoft has carefully considered their business objectives and created an appropriate budget approach.]

<<Begin text here>>

 

Project Estimates

[Description: The Project Estimates section presents three views of the budget:

 

 

Justification: Each view of this information is important. The customer and program manager need to be able to state the solution’s total cost. The total cost of each project or sub-project creates a framework for the program manager and project managers to work within. And the total cost for each itemized cost area allows the customer and product manager to understand how each element of the solution contributes to the overall budget.]

<<Begin text here>>

 

Project Details

[Description: The Project Details section provides the detailed information about one or more projects associated with the solution. 

 

Justification: Budget information at the detailed level creates accountability within the teams and provides parameters against which they must work. The customer may also be interested in the budget at this level.]

<<Begin text here>>

 

Project One

[Description: The Project One section describes the scope and expected results of the project with sufficient detail to distinguish it from other projects within the solution.]

<<Begin text here>>

 

Estimated Timeline

[Description: The Estimated Timeline section defines the start and completion dates for the project and dates associated with key milestones.]

<<Begin text here>>

 

Financial Plan

[Description: The Financial Plan section provides the itemized costs for the project. This should include all cost items and the total cost per item. This may also include a timeline of costs organized by phase or key milestone.]

<<Begin text here>>

 

Project Assumptions

[Description: The Project Assumptions section lists all assumptions that have been made about the project in estimating its costs. It should also describe how those assumptions will be confirmed.]

<<Begin text here>>

 

Project Risks

[Description: The Project Risks section defines any risks associated with the budget. This information should list the risks, identify their source, calculate their exposure, and suggest mitigation plans.]

<<Begin text here>>

 

Project Two

[Description: The Project Two section describes the scope and expected results of the project with sufficient detail to distinguish it from other projects within the solution.]

<<Begin text here>>

 

Estimated Timeline

[Description: The Estimated Timeline section defines the start and completion dates for the project and dates associated with key milestones.]

<<Begin text here>>

 

Financial Plan

[Description: The Financial Plan section provides the itemized costs for the project. This should include all cost items and the total cost per item. This may also include a timeline of costs organized by phase or key milestone.]

<<Begin text here>>

 

Project Assumptions

[Description: The Project Assumptions section lists all assumptions that have been made about the project in estimating its costs. It should also describe how those assumptions will be confirmed.]

<<Begin text here>>

 

Project Risks

[Description: The Project Risks section defines any risks associated with the budget. This information should list the risks, identify their source, calculate their exposure, and suggest mitigation plans.]

<<Begin text here>>

 

Cost Areas

[Description: The Cost Areas section identifies and describes all the cost areas of the solution. This section summarizes the costs associated with all the projects within the solution.

 

Justification: This cost area information provides the team and customer with a different view of the solution than the project-by-project view.]

<<Begin text here>>

 

Hardware

[Description: The Hardware section identifies every hardware item that must be purchased for the solution. This may include client workstations, server, LAN/WAN, cable plant, or other network-related hardware. Define the number of items required, their unit cost, and the total cost.]

<<Begin text here>>

 

WAN Circuits

[Description: The WAN Circuits section identifies every WAN circuit item that must be purchased for the solution. Define the number of items required, their unit cost, and the total cost.]

<<Begin text here>>

 

Software

[Description: The Software section identifies every software item that must be purchased for the solution. This may include client workstations, server, LAN/WAN, cable plant, or other network-related software. Define the number of items required, their unit cost, and the total cost.]

<<Begin text here>>

 

Development Environment Hardware and Software

[Description: The Development Environment Hardware and Software section identifies every hardware and software item that must be purchased for the development environment. This should include any development tools that will be used. Define the number of items required, their unit cost, and the total cost.]

<<Begin text here>>

 

Contractors

[Description: The Contractors section describes all contractors that will be used for development, testing, training, communications, project management, deployment, or operations support. It should describe their scope of work and the estimated cost of their services.]

<<Begin text here>>

 

People

[Description: The People section describes all non-contractor personnel that will be used for development, testing, training, communications, project management, deployment, or operations support. It should describe their scope of work and the estimated cost of their involvement in the solution.]

<<Begin text here>>

 

Training

[Description: The Training section describes all training cost items. This may include web based training fees, reference books, 3rd party courseware, course fees, instructor fees, and other related materials. Define the number of items required, their unit cost, and the total cost.]

<<Begin text here>>

 

Communications Development

[Description: The Communications Development section describes all items required to develop the communication infrastructure for the project. Define the number of items, their unit cost, and the total cost.]

<<Begin text here>>