|Microsoft Office Project 2003
Microsoft Office Project Server 2003
Microsoft Project 2000 and 2002
Monitoring your project's costs is critical to your project's financial success. Monitoring costs involves reviewing the basic cost information on a repeated basis, as well as performing a more detailed analysis of cost information.
To keep your project on budget (budget: The estimated cost of a project that you establish in Project with your baseline plan.), you may want to identify cost problems by reviewing cost totals (total cost: The calculated cost of a project, task, resource, or assignment over the life of the project.) and cost variances (CV: The difference between the budgeted cost of work performed [BCWP] on a task and the actual cost of work performed [ACWP]. If the CV is positive, the cost is currently under the budgeted amount; if the CV is negative, the task is currently over budget.) that occur over time, so you can make adjustments, if needed.
Tip This article is part of a series of articles that describe a broad set of project management activities. We call these activities "goals" because they are organized around the project management life cycle: Build a plan, track and manage a project, and close a project. The project life cycle is outlined in The Project Map, where you can find a link to an article about each project management goal. Most of the articles include links to supporting information or procedures that you perform in Project or Project Server. These "goal" articles were designed to help you not only use Project but also better understand project management.
Previous goal Next goal
See all goals on the Project Map
Review the project costs By examining the project's current (scheduled or current cost: The latest cost of tasks, resources, assignments, and the entire project, which is displayed in the cost field as cost or total cost. It is kept up to date with cost adjustments that you make and with the project's progress.), actual (actual cost: The cost that has actually been incurred to date for a task, resource, or assignment. For example, if the only resource assigned to a task gets paid $20 per hour and has worked for two hours, the actual cost to date for the task is $40.), baseline (baseline cost: The original project, resource, and assignment cost as shown in the baseline plan. The baseline cost is a snapshot of the cost at the time when the baseline plan was saved.), and remaining (remaining cost: The estimated cost that is yet to be incurred for a task, resource, or assignment.) cost totals, you can establish whether your project will stay within budget.
Review the cost variances If you set a baseline for your project, you can quickly see where the current (or scheduled) cost totals differ from the budgeted costs for tasks (task: An activity that has a beginning and an end. Project plans are made up of tasks.), resources (resources: The people, equipment, and material that are used to complete tasks in a project.), or assignments (assignment: A specific resource that is assigned to a particular task.).
Find the costs that are over budget If you set a baseline for your project, you can quickly focus on the tasks or resources with cost overruns.
Analyze cost performance By using earned value analysis to compare your expected progress and costs with the actual progress and costs to date for tasks that have resources assigned, you can determine if you will run out of money before the tasks are completed.
Analyze or model costs If you are using Project Server, you can analyze project costs by using the Portfolio Analyzer and Portfolio Modeler, within a project or across projects.