CT2 Resources Demand Supply Allocation

From UG

(Difference between revisions)
Jump to: navigation, search
(Metrics)
Line 14: Line 14:
The following metrics are suggested:
The following metrics are suggested:
-
* 1 ftd (high/full load)
+
* 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 ftd (med load)
+
* 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 ftd (low load)
+
* 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 ftd (very low load)
+
* 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.

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

Personal tools