CT2 Resources Demand Supply Allocation
From UG
(Difference between revisions)
(→2010 Forecast) |
|||
Line 24: | Line 24: | ||
:: if average numb of hours required per week is 0-10 | :: if average numb of hours required per week is 0-10 | ||
- | == 2010 Forecast == | + | == 2010 May Forecast == |
+ | |||
+ | Error margin: TBD. | ||
+ | |||
+ | === Acc Core === | ||
+ | |||
+ | === Client === | ||
+ | |||
+ | === Ops === | ||
+ | |||
+ | === Ops Acc === | ||
+ | |||
+ | === Ops Pdfs === | ||
+ | |||
+ | === Ops Reps === | ||
+ | |||
+ | === Inventory Management === | ||
+ | |||
+ | === Etc === | ||
+ | |||
+ | |||
+ | == 2010 June Forecast == | ||
+ | |||
+ | === Acc Core === | ||
+ | |||
+ | === Client === | ||
+ | |||
+ | === Ops === | ||
+ | |||
+ | === Ops Acc === | ||
+ | |||
+ | === Ops Pdfs === | ||
+ | |||
+ | === Ops Reps === | ||
+ | |||
+ | === Inventory Management === | ||
+ | |||
+ | === Etc === | ||
+ | |||
+ | |||
+ | == 2010 July to December Forecast == | ||
+ | |||
+ | |||
+ | === Acc Core === | ||
+ | |||
+ | === Client === | ||
+ | |||
+ | === Ops === | ||
+ | |||
+ | === Ops Acc === | ||
+ | |||
+ | === Ops Pdfs === | ||
+ | |||
+ | === Ops Reps === | ||
+ | |||
+ | === Inventory Management === | ||
+ | |||
+ | === Etc === |
Revision as of 01:54, 5 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 |
ftd
Assumptions:
- 8 m/h a day ~ 40 m/h a week ~ 168 m/h a month ~ one full time developer (ftd)
The following metrics are suggested:
- 1 ftd (high/full load)
- if average numb of hours required per week is 30-40
- 3/4 ftd (med load)
- if average numb of hours required per week is 20-30
- 1/2 ftd (low load)
- if average numb of hours required per week is 10-20
- 1/4 ftd (very low load)
- if average numb of hours required per week is 0-10
2010 May Forecast
Error margin: TBD.