This Quality Control Measurements Software Development document shows how Lucas Park (QA Engineer) and Eduardo Montes tracked all quality metrics for the ProjectAdm SaaS platform across 28 sprints — covering PHPUnit test results, response time measurements, accessibility compliance scores, cross-browser test results, and code quality metrics. This Excel workbook provided the quantitative quality evidence that supported milestone acceptance decisions at all five gates.

What Are Quality Control Measurements?

Quality Control Measurements are a PMBOK 8 output in the Delivery Performance Domain that document the results of quality control activities — the actual measured values compared to the planned quality standards. They include test results, inspection findings, defect rates, and performance metrics that provide objective evidence of whether deliverables meet acceptance criteria. Quality control measurements are the inputs to quality reports, milestone acceptance decisions, and lessons learned — without them, quality acceptance is subjective and unauditable.

What This Quality Control Measurements Software Development Includes

The ProjectAdm Quality Control Measurements workbook tracks all quality dimensions across 28 sprints:

• PHPUnit Test Results (Sheet 1) — Sprint-by-sprint test count and pass rate: Sprint 1 (22 tests, 100%), Sprint 8 (142 tests, 100% — M2 threshold), Sprint 14 (187 tests, 100% — M3), Sprint 22 (278 tests, 100% — M4), Sprint 28 (321 tests, 100% — M5); no sprint ended with <100% pass rate; 0 test regressions across all 28 sprints; runtime trend: Sprint 1 (1.2 min) → Sprint 28 (8.4 min)
• Response Time Measurements (Sheet 2) — p95 response time measured biweekly against 300ms threshold; Sprint 13: 4,200ms (ISS-002 — threshold breach); Sprint 19 (post-optimization): 280ms (passing); Sprint 28 (production load test, 500 concurrent users): 210ms avg, 265ms p95; all primary user actions measured: board load, task create, Gantt render, AI suggestion
• Cross-Browser Test Results (Sheet 3) — Tested: Chrome 124+, Firefox 125+, Safari 17.4+, Edge 124+; Sprint 9 (ISS-003 resolution): Safari Kanban drag-drop PASS on iOS 17.4 + macOS Sonoma 14.4; Sprint 14: Gantt chart CR-002 — PASS all browsers; Sprint 22: WBS view CR-004 — PASS all browsers; Sprint 28: full regression — PASS all 4 browsers on all 12 features
• Accessibility Measurements (Sheet 4) — WCAG 2.1 AA compliance checked via automated (axe-core) + manual review per milestone; M2: 94% compliance (6 issues found, 5 resolved, 1 deferred); M3: 97% (3 issues); M4: 99% (1 minor color contrast issue deferred); M5: 100% compliance confirmed by Lucas Park and Camila Rocha joint review
• Code Quality Metrics (Sheet 5) — PHP-CS-Fixer violations: 0 (enforced in CI pipeline since Sprint 1); Cyclomatic complexity: average 4.2 per function (target <10); Code coverage: 68% overall (321 PHPUnit tests / estimated 472 testable functions); Duplicate code: 2.1% (target <5%); Technical debt ratio (SonarQube equivalent): 3.8 days (target <5 days)
• Security Measurements (Sheet 6) — Penetration test (Sprint 26): 0 critical findings, 2 medium findings (both resolved before M5), 3 low findings (1 resolved, 2 accepted as low risk); OWASP Top 10 self-assessment: all 10 categories addressed; data encryption: verified at rest (AES-256) and in transit (TLS 1.3)

How Eduardo Montes Used This Quality Control Measurements Software Development

Lucas Park updated the Quality Control Measurements Software Development workbook after every sprint review, adding the new PHPUnit count and the latest response time measurements. Eduardo Montes used the Sprint 13 p95 breach (4,200ms) as the quantitative trigger for the ISS-002 corrective action — he could point to an exact measurement that failed the 300ms acceptance criterion, making the Advanced Filtering deferral decision at M3 an objective quality control decision rather than a subjective judgment call.

How to Use This Quality Control Measurements Software Development Document

Use this example to understand how to build a Quality Control Measurements Software Development register that supports objective milestone acceptance. Every measurement in the ProjectAdm register has a pre-defined threshold from the Requirements Documentation — making the pass/fail determination automatic rather than negotiated at each milestone gate.

Download the Template and Deepen Your Knowledge

Ready to create your own quality control measurements? Download the blank Quality Control Measurements Template (PMBOK 8).

• Download the Quality Control Measurements Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Quality Control Measurements 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: Delivery