Cost Aggregation

The process of rolling up detailed work package cost estimates to a chosen WBS level or to a specific cost control account by adding them together.

Key Points

  • Combines work package cost estimates to form higher-level budgets.
  • Performed at a selected WBS level or for designated cost control accounts.
  • Supports creation of the cost baseline and funding requirements.
  • Relies on accurate, bottom-up estimates and consistent coding in the WBS.

Example

A project has three work packages under the "Design" control account with estimated costs of USD 20,000, USD 15,000, and USD 5,000. Using cost aggregation, the project manager sums these to report a USD 40,000 budget for the Design control account and rolls that figure up to the next WBS level for overall phase budgeting.

PMP Example Question

Which technique is used to add up work package cost estimates to establish the budget at a specific WBS level or control account?

  1. Parametric estimating
  2. Reserve analysis
  3. Cost aggregation
  4. Earned value analysis

Correct Answer: C — Cost aggregation

Explanation: Cost aggregation is the roll-up of lower-level work package cost estimates to a chosen WBS level or control account to form the budget baseline.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Build an ICS/OT cybersecurity foundation that fits the real environment

Standard IT controls can disrupt the industrial systems they are meant to protect. Learn how to assess OT risk, design zones and conduits, apply IEC 62443 security levels, use MITRE ATT&CK for ICS, and establish passive asset visibility without risking production. Eight reconstructed incidents connect attacker techniques to the controls that failed, giving you the vocabulary and judgment to make credible security decisions from day one.

Explore the Course