Calculator
EDPA step by step
A concrete calculation example with real numbers.
From inputs to derived hours — verifiable by hand.
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 level of involvement (CW) on different items.
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) |
|---|---|---|---|---|
S-1 Auth service | 8 | 0.3 / 0.8 | 1 / 1 | — |
S-2 API endpoints | 5 | — | 1 / 1 | 0.25 / 0.6 |
S-3 Architecture review | 3 | 1 / 1 | 0.25 / 0.6 | 0.2 / 0.5 |
S-4 Project planning | 2 | 0.15 / 0.5 | — | 1 / 1 |
CW = Contribution Weight (level of involvement). RS = Relevance Signal (in Full mode).
Shown as CW / RS.
Score = JobSize × CW
DerivedHours = (Score / ΣScores) × Capacity
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
| Item | JS | CW | RS | Score |
|---|---|---|---|---|
S-3 | 3 | 1 | 1 | 3.00 |
S-1 | 8 | 0.3 | 0.8 | 2.40 |
S-4 | 2 | 0.15 | 0.5 | 0.30 |
| Σ 5.70 |
Bob
Developer · 40h
| Item | JS | CW | RS | Score |
|---|---|---|---|---|
S-1 | 8 | 1 | 1 | 8.00 |
S-2 | 5 | 1 | 1 | 5.00 |
S-3 | 3 | 0.25 | 0.6 | 0.75 |
| Σ 13.75 |
Carol
PM · 20h
| Item | JS | CW | RS | Score |
|---|---|---|---|---|
S-4 | 2 | 1 | 1 | 2.00 |
S-2 | 5 | 0.25 | 0.6 | 1.25 |
S-3 | 3 | 0.2 | 0.5 | 0.60 |
| Σ 3.85 |
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
| Item | Score | Computation | Ratio | Hours | |
|---|---|---|---|---|---|
S-3 Architecture review | 3.00 | 3.00 / 5.70 × 30 | 52.6% | 15.8h | |
S-1 Auth service | 2.40 | 2.40 / 5.70 × 30 | 42.1% | 12.6h | |
S-4 Project planning | 0.30 | 0.30 / 5.70 × 30 | 5.3% | 1.6h | |
| Total | 5.70 | 100% | 30.0h |
Bob Developer
✓
Σ = 40.0h = 40h
| Item | Score | Computation | Ratio | Hours | |
|---|---|---|---|---|---|
S-1 Auth service | 8.00 | 8.00 / 13.75 × 40 | 58.2% | 23.3h | |
S-2 API endpoints | 5.00 | 5.00 / 13.75 × 40 | 36.4% | 14.5h | |
S-3 Architecture review | 0.75 | 0.75 / 13.75 × 40 | 5.5% | 2.2h | |
| Total | 13.75 | 100% | 40.0h |
Carol PM
✓
Σ = 20.0h = 20h
| Item | Score | Computation | Ratio | Hours | |
|---|---|---|---|---|---|
S-4 Project planning | 2.00 | 2.00 / 3.85 × 20 | 51.9% | 10.4h | |
S-2 API endpoints | 1.25 | 1.25 / 3.85 × 20 | 32.5% | 6.5h | |
S-3 Architecture review | 0.60 | 0.60 / 3.85 × 20 | 15.6% | 3.1h | |
| Total | 3.85 | 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 | Person | Role | CW | Hours | Share | |
|---|---|---|---|---|---|
| Bob | Developer | 1 | 23.3h | 64.8% | |
| Alice | Architect | 0.3 | 12.6h | 35.2% | |
| Total | 35.9h | 100% | |||
S-2 API endpoints | Person | Role | CW | Hours | Share | |
|---|---|---|---|---|---|
| Bob | Developer | 1 | 14.5h | 69.1% | |
| Carol | PM | 0.25 | 6.5h | 30.9% | |
| Total | 21.0h | 100% | |||
S-3 Architecture review | Person | Role | CW | Hours | Share | |
|---|---|---|---|---|---|
| Alice | Architect | 1 | 15.8h | 74.9% | |
| Carol | PM | 0.2 | 3.1h | 14.8% | |
| Bob | Developer | 0.25 | 2.2h | 10.3% | |
| Total | 21.1h | 100% | |||
S-4 Project planning | Person | Role | CW | Hours | Share | |
|---|---|---|---|---|---|
| Carol | PM | 1 | 10.4h | 86.8% | |
| Alice | Architect | 0.15 | 1.6h | 13.2% | |
| Total | 12.0h | 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.
Proportional allocation guarantees that the sum of ratios = 1.0 and the sum of hours = capacity.
Want to see EDPA on real data?