Calculator

EDPA step by step

A concrete calculation example with real numbers.
From inputs to derived hours — verifiable by hand.

Score = JobSize × CW
Configuration
Alice 30h · Bob 40h · Carol 20h
Alice 150h · Bob 200h · Carol 100h
01

Inputs

Team and work items

Three people with different capacities work on four Stories in one iteration. Each person has a different share (CW) on different items. CW is a per-item normalized share — the sum of all CWs on a single item = 1.0.

Alice
Architect
0.75 FTE 30h / iteration
Bob
Developer
1 FTE 40h / iteration
Carol
PM
0.5 FTE 20h / iteration
Work items & Contribution Weight (CW)
Item JS Alice (Arch) Bob (Dev) Carol (PM) Σ CW
S-1 Auth service 8 0.23 0.77 — 1.00
S-2 API endpoints 5 — 0.8 0.2 1.00
S-3 Architecture review 3 0.69 0.17 0.14 1.00
S-4 Project planning 2 0.13 — 0.87 1.00
CW = Contribution Weight (per-item normalized share). In the full pipeline, CW is computed from evidence (PRs, commits, reviews, comments, /contribute directives) in detect_contributors.py and the engine consumes it verbatim.
Score = JobSize × CW
DerivedHours = (Score / ΣScores) × Capacity
02

Score

Score computation

For each (person, item) pair, we multiply JobSize × CW. The result is a raw Score that determines the relative share of capacity.

Alice
Architect · 30h
ItemJSCWScore
S-3 3 0.69 2.07
S-1 8 0.23 1.84
S-4 2 0.13 0.26
Total Σ 4.17
Bob
Developer · 40h
ItemJSCWScore
S-1 8 0.77 6.16
S-2 5 0.8 4.00
S-3 3 0.17 0.51
Total Σ 10.67
Carol
PM · 20h
ItemJSCWScore
S-4 2 0.87 1.74
S-2 5 0.2 1.00
S-3 3 0.14 0.42
Total Σ 3.16
03

Per-Person

Derived hours

Each Score is divided by the total sum and multiplied by capacity. Result: how many hours a person spent on each item.

Alice Architect
✓ Σ = 30.0h = 30h
ItemScoreComputationRatioHours
S-3 Architecture review 2.07 2.07 / 4.17 × 30 49.6% 14.9h
S-1 Auth service 1.84 1.84 / 4.17 × 30 44.1% 13.2h
S-4 Project planning 0.26 0.26 / 4.17 × 30 6.2% 1.9h
Total 4.17 100% 30.0h
Bob Developer
✓ Σ = 40.0h = 40h
ItemScoreComputationRatioHours
S-1 Auth service 6.16 6.16 / 10.67 × 40 57.7% 23.1h
S-2 API endpoints 4.00 4.00 / 10.67 × 40 37.5% 15.0h
S-3 Architecture review 0.51 0.51 / 10.67 × 40 4.8% 1.9h
Total 10.67 100% 40.0h
Carol PM
✓ Σ = 20.0h = 20h
ItemScoreComputationRatioHours
S-4 Project planning 1.74 1.74 / 3.16 × 20 55.1% 11.0h
S-2 API endpoints 1.00 1.00 / 3.16 × 20 31.6% 6.3h
S-3 Architecture review 0.42 0.42 / 3.16 × 20 13.3% 2.7h
Total 3.16 100% 20.0h
04

Per-Item

How much did each item cost?

Same data, different perspective. For each item we see who contributed and how many hours. Shares always sum to 100%.

S-1 Auth service
JS 8
PersonRoleCWHoursShare
Bob Developer 0.77 23.1h 63.6%
Alice Architect 0.23 13.2h 36.4%
Total 36.3h 100%
S-2 API endpoints
JS 5
PersonRoleCWHoursShare
Bob Developer 0.8 15.0h 70.3%
Carol PM 0.2 6.3h 29.7%
Total 21.3h 100%
S-3 Architecture review
JS 3
PersonRoleCWHoursShare
Alice Architect 0.69 14.9h 76.5%
Carol PM 0.14 2.7h 13.7%
Bob Developer 0.17 1.9h 9.8%
Total 19.5h 100%
S-4 Project planning
JS 2
PersonRoleCWHoursShare
Carol PM 0.87 11.0h 85.5%
Alice Architect 0.13 1.9h 14.5%
Total 12.9h 100%
05

Guarantee

Mathematical guarantee

Alice
✓
Σ 30.0h = 30h
Capacity
Bob
✓
Σ 40.0h = 40h
Capacity
Carol
✓
Σ 20.0h = 20h
Capacity
Σ DerivedHours = Capacity — always, no exceptions.
Proportional allocation guarantees that the sum of ratios = 1.0 and the sum of hours = capacity.

Want to see EDPA on real data?

Dashboard demo Methodology Evaluation & tests