CT2 Resources Demand Supply Allocation
From UG
(Difference between revisions)
(→Metrics) |
|||
Line 14: | Line 14: | ||
The following metrics are suggested: | The following metrics are suggested: | ||
- | * 1 | + | * 1 ftdev (high/full load) |
:: if average numb of hours required per week is 30-40 | :: if average numb of hours required per week is 30-40 | ||
- | * 3/4 | + | * 3/4 ftdev (med load) |
:: if average numb of hours required per week is 20-30 | :: if average numb of hours required per week is 20-30 | ||
- | * 1/2 | + | * 1/2 ftdev (low load) |
:: if average numb of hours required per week is 10-20 | :: if average numb of hours required per week is 10-20 | ||
- | * 1/4 | + | * 1/4 ftdev (very low load) |
:: if average numb of hours required per week is 0-10 | :: if average numb of hours required per week is 0-10 | ||
Revision as of 16:05, 11 May 2010
This article is about Demand for CT2 features and related Supply / Allocation of Human Resources.
We need to build smart Supply Chain for CT2! ))
Contents |
Metrics
ftdev
Assumptions:
- 8 m/h a day ~ 40 m/h a week ~ 168 m/h a month ~ one full time developer (ftdev)
The following metrics are suggested:
- 1 ftdev (high/full load)
- if average numb of hours required per week is 30-40
- 3/4 ftdev (med load)
- if average numb of hours required per week is 20-30
- 1/2 ftdev (low load)
- if average numb of hours required per week is 10-20
- 1/4 ftdev (very low load)
- if average numb of hours required per week is 0-10
BAs, SAs, QAs
TBD
2010 May Forecast
Error margin: TBD.