CAPM Calculations: Scope, Schedule & Cost Made Easy

Plan Cost Management is the foundational process establishing how a project's costs will be estimated, budgeted, and controlled. Crucially, the Cost Management Plan contains no actual dollar amounts, distinguishing it directly from the project budget. Instead, it defines the financial "rules of the game," setting specific levels of accuracy, precision, control thresholds, and performance measurement guidelines like Earned Value Management (EVM). The lecture also explores how cost management adapts in agile environments through burn rates and backlog prioritization, ensuring the project remains financially disciplined and aligned with the overarching Business Case.

The Estimate Costs lecture explains how to approximate the financial resources required for a project's activities. It clarifies the critical distinction between estimate accuracy and precision, as well as the difference between undisciplined padding and transparent Contingency Reserves. Project managers calculate these costs using four primary techniques: Analogous, Parametric, Three-Point (PERT), and Bottom-Up Estimating. All financial logic must be formally documented in the Basis of Estimates (BoE). Finally, the lecture contrasts predictive methods with agile environments, which use fixed budgets, Relative Sizing, and Burn Rates to manage prioritized scope.

The Determine Budget lecture explains how to aggregate individual activity estimates into a single, authorized financial roadmap. It highlights the critical difference between the Cost Baseline, which the project manager controls and includes Contingency Reserves for known risks, and the total Project Budget, which adds sponsor-controlled Management Reserves for unforeseen events. By rolling costs up through the WBS hierarchy, managers can accurately plot the time-phased S-Curve and perform Funding Limit Reconciliation to align planned expenditures with available cash. Alternatively, agile environments simplify this by budgeting fixed capacity using a team's burn rate.

The Earned Value Analysis (EVA) lecture explains how to objectively measure project performance, avoiding the trap of simply comparing a budget to actual spending. It introduces three foundational pillars: Planned Value (PV), Actual Cost (AC), and the crucial Earned Value (EV). Project managers use these metrics to calculate Variances (cost/schedule differences) and Indices (efficiency ratios), where a negative variance or an index below 1.0 indicates poor health. The lecture emphasizes that EV must always be the starting point for calculations, and contrasts this predictive method with Agile’s use of Burnup and Burndown Charts.

The Cost Baseline and Funding Concepts lecture explains how to manage a project's financial viability over time. It clarifies that having an approved budget does not guarantee immediate cash availability. The Cost Baseline is a time-phased budget—visualized as an S-Curve—that includes activity estimates and Contingency Reserves, but strictly excludes Management Reserves. Project managers must perform Funding Limit Reconciliation to ensure planned spending never exceeds available funding steps. Finally, the lecture contrasts this with Agile environments, which use fixed-funding models to deliver prioritized value from the backlog.

The Forecasting Basics lecture transitions from current performance to predicting final project costs. It establishes the Budget at Completion (BAC) as the baseline and clarifies the critical difference between the Estimate at Completion (EAC) (total projected cost) and the Estimate to Complete (ETC) (cost of remaining work). Managers forecast using Typical Variances (current trends continue) or Atypical Variances (past issues are anomalies). A negative Variance at Completion (VAC) signals a budget overrun. Finally, it contrasts this mathematical approach with Agile’s use of Velocity and Burndown Charts.

The Plan Quality Management lecture establishes the framework for meeting a project's standards, emphasizing that while a low Grade is acceptable, low Quality is always a failure. It champions Prevention over Inspection, evaluating the Cost of Quality (CoQ) through conformance and non-conformance costs. The process outputs the Quality Management Plan and specific Quality Metrics to prevent unrequested scope additions known as Gold Plating. Agile environments adapt this using the Definition of Done (DoD) and continuous improvement. Ultimately, quality is defined by the exact fulfillment of validated requirements.

The Manage Quality vs Control Quality lecture clarifies the critical distinction between evaluating a project's process versus its product. Manage Quality (Quality Assurance) is a proactive, execution-phase activity focusing on the "how"—ensuring the team follows correct procedures and utilizing Quality Audits to prevent defects. Conversely, Control Quality (Quality Control) is a reactive, monitoring activity focusing on the "what"—inspecting finished work against metrics to produce Verified Deliverables. The lecture also explores how agile teams blend these disciplines through Test-Driven Development (TDD) and the Definition of Done (DoD).

The Quality Tools You Should Recognize lecture dispels the myth that quality tools are strictly for manufacturing. It explores essential diagnostic instruments: the Cause-and-Effect (Fishbone) Diagram for root-cause analysis, Flowcharts (SIPOC) for process mapping, and Checksheets for data collection. A crucial exam distinction is made between standard Histograms and Pareto Diagrams, which use the 80/20 rule to prioritize the "vital few" defects. It also covers Control Charts for monitoring process stability (noting the Rule of Seven) and Scatter Diagrams for tracking correlation. Agile teams adapt these tools into Visual Radiators to drive continuous improvement.

This lecture details the transition from planning to execution through Estimate Activity Resources and Acquire Resources. It explains determining necessary assets using techniques like bottom-up estimating and organizing them via the Resource Breakdown Structure (RBS). During acquisition, project managers rely heavily on Negotiation with functional managers to secure staff and may utilize Virtual Teams. A crucial distinction is made between Resource Requirements (what is needed) and Resource Calendars (when they are available). Finally, agile environments contrast this by focusing on acquiring stable, cross-functional teams rather than task-specific individuals.

This lecture distinguishes between building a team's capability (Develop Team) and steering its performance (Manage Team). Develop Team is proactive, using tools like Colocation and Training to create synergy and prevent conflict by establishing a Team Charter. Conversely, Manage Team is reactive, focusing on tracking performance, providing feedback, and resolving active conflicts using interpersonal skills and Emotional Intelligence. Finally, the lecture highlights Agile environments, where traditional managers become Servant Leaders who remove impediments while empowering Self-Organizing teams to manage their own peer-to-peer performance and daily conflicts.

The Team Development Models lecture explores the Tuckman Ladder, a framework detailing how teams evolve through five stages: Forming, Storming, Norming, Performing, and Adjourning. A critical insight is that Storming represents healthy project progress, not failure, requiring the project manager to actively facilitate conflict resolution. As trust builds, leadership shifts from directive guidance to supportive coaching. The lecture also highlights how Business Analysts must adapt their elicitation techniques to the team's current stage, and how Agile teams accelerate this developmental growth using Sprint Retrospectives and Servant Leadership.

The Plan Communications Management lecture highlights the critical distinction between human-centered Communication and the technical tools of Communications. The process outputs the Communications Management Plan, serving as the definitive guide for project information flow based on a thorough Communication Requirements Analysis. It explores the Communication Model (Sender, Receiver, Noise) and clarifies the difference between communication technology and specific methods—Push, Pull, and Interactive. Finally, the lecture contrasts traditional planning with Agile environments, which rely on Information Radiators and face-to-face interactions to achieve continuous "Radical Transparency".

This lecture explains how communication complexity increases as team size grows, using the formula n(n−1)/2 to calculate communication channels. It emphasizes that adding team members significantly increases coordination overhead and clarifies that the project manager must always be included in “n.” The lecture then categorizes communication methods into Interactive, Push, and Pull, explaining when each is most effective. It also connects these methods to Agile practices and business analysis activities, highlighting that selecting the right communication approach is essential for minimizing confusion and maintaining efficient information flow.

This lecture distinguishes between executing communication activities and evaluating their effectiveness. Manage Communications focuses on creating and distributing information as per the plan, while Monitor Communications ensures that stakeholder needs are actually being met. A key insight is that both processes occur simultaneously, not sequentially. The lecture highlights outputs such as project communications and change requests, and introduces the “Action vs Assessment” exam rule. It also connects these concepts to Agile feedback loops and business analysis validation, emphasizing continuous improvement in communication effectiveness.