December 10, 2006

PMI Cost Management Processes

The cost management processes are all about the cost of the resources necessary to complete the project activities. The three processes in the Project Cost Management knowledge area are:

  1. Cost Estimating – Cost Estimating is the process of developing an estimated cost for the resources needed to complete project activities. Cost Estimating normally occurs in the planning process group.
  2. Cost Budgeting – Cost Budgeting is the process of summarizing the estimated costs of individual activities or work packages to establish a cost baseline. Cost Budgeting normally occurs in the planning process group.
  3. Cost Control – Cost Control is how the cost variances and other changes to the project are managed and controlled. Cost Control occurs in the monitoring and controlling process group.

So how does one go about cost planning? Cost Planning activities should occur prior to engaging in estimating and budgeting cost. In order to plan a couple of agreements in how to qualify and quantify cost are necessary, those agreements are:
  • A determination of the precision level for schedule activity cost estimates - Schedule activity cost estimates will comply with a rounding of the data to a predetermined precision based on the size of the project and the scope of the activity. (Remember that contingencies may be factored in here.)
  • Establishment of a unit of measure for each of the resources – During estimation, it is necessary for the project management team to agree on a standard unit of measure for each resource. For example, the unit of measure for a particular task may be staff-days or staff-weeks.
  • Establishment of direct tie ins to organizational procedures - A control account is normally established to control project cost accounting. Individual control accounts are given a code or an account number that is directly linked to your general ledger account system.
  • Definition of control thresholds - Planning items for controlling costs should include control thresholds for costs. For example, if a threshold for a given activity is set at $5,000, the project manager must be alerted before the costs exceed this amount.
  • Definition of earned value rules – The Earned Value Formulas for computing earned value which determine the estimate to complete are identified.
  • Development of the formats for the various cost reports – Standardized reporting formats are established by the Cost Management Plan. Reports are provided to the stakeholders. It is good to use an organizational template here.
  • Documentation of each of the three Project Cost Management processes - The three cost management processes should be documented in the Project Management Plan as they relate to the specific project.

The purpose of planning activities is to increase the efficiency and effectiveness in how an organization and project manager manage project costs.

Posted by Elyse at December 10, 2006 1:24 PM
Comments

I knew you would eventually get here ;)

For developers/architects, this is where the rubber meets the road. A major input to your cost estimate is going to be the size estimate of the actual project. If you think about it, all other costs in your project have at least some impact from this estimate, although some are unknowable at the outset. Specifically your costs of conceiving the project from the beginning.

I have found that estimating the size of software is where most of the academic approaches to project management (cmmi, rup, xp, etc) seem to leave you hanging. They generally have an "insert estimation method of choice here" space, yet they bury that spot in tons of process.

After investigating all sorts of methods of software size determination (sloc, cocomo ii, function points, etc), I'd have to say that the best method I have found so far has been function point counting. Unfortunately, it's a non-trivial task for most projects and rarely can it be used in a project that is being contracted for. That's really too bad.

There are also limitations when trying to build your estimate very early in the project life-cycle. You know those moments when someone in management just wants a "back-of-the-napkin guestimate". Which, of course, will subsequently be carved in stone.

I put together a few posts on my blog about estimating software size through use cases. Take a peek to see if it might fit into your process. http://mrmx.blogspot.com/2005/05/software-estimation-part-1-what-method.html

Posted by: Mike Rankin at December 11, 2006 11:04 AM

It is always so comforting when you see you're not alone on this rough planet :-)

Posted by: Christian Gosch at May 29, 2007 1:53 PM
Post a comment









Remember personal info?