This Work Performance Information Software Development workbook is where Eduardo Montes transformed ProjectAdm's raw sprint measurements into actionable management intelligence — calculating EV, PV, AC, SPI, CPI, SV, and CV for every sprint, identifying the root causes behind the numbers, and translating those findings into the decisions that kept a $280,000 SaaS platform development project on track despite ISS-002's 3-sprint delay and four approved change requests.

What Is Work Performance Information?

Work Performance Information is a PMBOK 8 output in the Measurement Performance Domain representing performance data collected from various controlling processes, analyzed in context, and integrated based on relationships across areas. It transforms raw Work Performance Data (facts) into interpreted results (meaning): instead of "AC = $28,400 in Sprint 8," Work Performance Information says "CPI = 0.94 in Sprint 8 — 6% over budget this sprint; root cause: ISS-002 investigation overtime; trend: recovering since Sprint 6 low of 0.87; forecast CPI at project close: 0.97 if recovery holds." Work Performance Information feeds Work Performance Reports — it is the analytical layer between data collection and communication. PMBOK 8 is explicit that Work Performance Information requires judgment and context, not just formula application.

What This Work Performance Information Software Development Includes

The ProjectAdm Work Performance Information workbook contains five analytical worksheets:

• EVM Dashboard — Sprint-by-sprint EV, PV, AC, SV (SV = EV − PV), CV (CV = EV − AC), SPI (SPI = EV ÷ PV), CPI (CPI = EV ÷ AC); cumulative values and periodic (sprint) values; EAC calculated by three methods (EAC = BAC ÷ CPI; EAC = AC + (BAC − EV); EAC = AC + (BAC − EV) ÷ (CPI × SPI)); consensus EAC used for steering committee reporting; BAC = $280,000
• Variance Analysis — SV and CV annotations for every sprint with significant variance (|SV| or |CV| > $5,000); root cause classification (Issue, Change Request, Estimation Error, External); corrective action taken; result of corrective action in subsequent sprints
• Trend Analysis — 3-sprint rolling averages for SPI and CPI; forecast trendlines through project close; early warning flag logic (flag raised when SPI < 0.90 or CPI < 0.90 for 2 consecutive sprints); ISS-002 flag raised Sprint 5, cleared Sprint 12
• Scope Performance — Sprint-by-sprint story points completed vs. committed; velocity trend; backlog burn-down rate; scope change impact: CR-001 (+147 story points), CR-002 (+218 story points), CR-003 (−89 story points), CR-004 (+121 story points); net scope increase: +397 story points absorbed within budget via CPI recovery
• Quality Performance — Defect escape rate trend (defects found in UAT ÷ total defects found); PHPUnit test coverage trend (target ≥ 80%; achieved Sprint 12, maintained through Sprint 28); ISS-006 (PHPUnit runtime 47 min) resolved Sprint 18 by Lucas Park, reducing runtime to 8 min

How Eduardo Montes Used This Work Performance Information Software Development

Eduardo Montes updated the Work Performance Information workbook every Friday evening after importing the raw data into the Work Performance Data workbook, and presented the EVM Dashboard to Henry Douglas every Sprint Review. The variance analysis tab was the most valuable tool in the project's crisis management: when ISS-002 drove SPI to 0.71 in Sprint 5, the root cause annotation ("MariaDB I/O bottleneck — index redesign in progress, ETA Sprint 7") gave Henry Douglas enough context to approve the recovery strategy without requesting a schedule baseline change. The trend analysis tab's 3-sprint rolling average smoothed out sprint-to-sprint noise — preventing false alarms when a single sprint underperformed due to a holiday week or a planned architecture refactoring sprint. By Sprint 28, final SPI = 1.03, final CPI = 0.98, EAC = $274,400 vs. BAC $280,000 — $5,600 under budget.

How to Use This Work Performance Information Software Development Document

When building your own Work Performance Information Software Development analysis system, invest in the variance analysis tab's root-cause classification. Projects that track numbers without annotating root causes lose institutional memory — six months into a project, a CPI of 0.87 in Sprint 5 is meaningless without the annotation that explains it was caused by a specific technical issue that has since been resolved. The ProjectAdm variance log became a project history artifact that Eduardo Montes used in the Lessons Learned Register — three of the top five lessons learned referenced specific sprint variance annotations as evidence. The workbook is also the best single artifact for future project estimation: the actual-vs-estimated data across 214 activities is a calibration dataset that makes future software development estimates more accurate.

Ready to create your own work performance information system? Download the blank Work Performance Information Template (PMBOK 8).

• Download the Work Performance Information Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Work Performance Information in PMBOK 8

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.

Format: Microsoft Excel (.xlsx) | Project: Software Development (SaaS Platform) | PMBOK Edition: 8th (2025) | Domain: Measurement