>> Browse services
>_ProductScope StudioFrom an idea to a shareable PRD_> Open_> OpenVALUE MODE
QUALITY GATE
8/8 instrumented · 7 improved
Example mode shows illustrative numbers only. Switch to Your baseline to enter real values. Deltas are not claims until baseline and sample rules are met.
SUGGESTED GATE
PASS
Flow or cost improved and quality did not worsen.
PASS
Throughput or cost improved, change failure rate did not worsen, and no metric is in a failing direction on quality.
WATCH
Mixed signals, insufficient sample, or any metric still marked not instrumented.
FAIL
Change failure rate worsened vs baseline, or total cost per point rose while throughput claims improved.
Suggested gate from quality and economics. Override only with a written reason in the sponsor report.
+2
DEFINITION
Accepted complexity points delivered per engineer in a fixed calendar period. A point counts only when the change meets the accepted-change definition: ticket, implementation, required verification, approval, production release, and no qualifying revert or defect in the defined window.
SYSTEMS OF RECORD
BASELINE · BEFORE
Pull 8–12 historical weeks for the pilot team and repos. Tag each accepted change with a pre-agreed S/M/L/XL weight. Sum points, divide by active engineer-weeks in the same window. Exclude freezes and known outages with a written rule.
AFTER · PILOT
Same definition, same weights, same team and repos. Tag pilot-cohort work explicitly. Compare like calendar lengths (e.g. 4 weeks vs 4 weeks). Publish raw accepted-change count beside the normalized rate.
MIN SAMPLE
At least 20 accepted changes in each compared window, or state that the pilot is directional only.
WHEN NOT TO CLAIM
Major roadmap mix shift (e.g. all platform work vs all features), headcount change above 20%, or complexity weights changed after baseline closed.
GAMING GUARDS
OBJECTION HANDLING
CTO OBJECTION
“This is story points with a new hat. We already game them.”
REPLY · Weights are relative and locked before work starts. We publish raw accepted changes and quality gates beside the rate. If points inflate without quality holding, the gate fails and we do not claim uplift.
CFO OBJECTION
“More points does not mean more business value.”
REPLY · Correct. Throughput is capacity, not revenue. Pair it with cost per accepted point (or VDU) and quality. ROI models use quality-adjusted capacity, not points alone.
-3
-7
-0.5
0
+17
-4
-60
ANTI-GAMING
Never rank individuals by tokens, prompts, or LOC.
Report quality and cost beside every throughput claim.
Lock complexity weights before the pilot cohort starts. Recalibration mid-cohort voids the comparison.
Segment by repo, seniority band, and work type when mix shifts.
Prefer system timestamps over developer self-report.
Publish sample size and exclusion rules with every delta.