CT2 Resources Demand Supply Allocation

From UG

(Difference between revisions)

Revision as of 17:27, 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 Software Development! ))

Metrics

ftl

It is proposed to use ftl (full time load) unit of measurement. This is to measure demand for IT staff (SAs, BAs, developers, QAs).

Assumptions:

One full time employee works 8 m/h a day ~ 40 m/h a week ~ 168 m/h a month

The following metrics are suggested:

1 ftl (high/full load)

if average numb of hours required per week is 30-40

3/4 ftl (med load)

if average numb of hours required per week is 20-30

1/2 ftl (low load)

if average numb of hours required per week is 10-20

1/4 ftl (very low load)

if average numb of hours required per week is 0-10

2010 June to December Forecast

Existing modules

Acc Component

Client Component

Ops Component

Ops Pdfs Component

Ops Reps Component

New Modules

Trucking Domestic Optimization

Rates Interface

Agent Interface

EDI

Inventory Management

www.jaguarfreight.com website re-design

Etc

Development based on Requirements not Detailed Design

2 possible options:

Remote Developer (programmer) creates detailed design based on requirements
Remote Designer creates detailed design based on requirements

Both options would increase numb of hours required in Remote Team

@@ Line 9: / Line 9: @@
 === ftl ===
-ftl - full time load
+It is proposed to use '''ftl''' (full time load) unit of measurement. This is to measure demand for IT staff (SAs, BAs, developers, QAs).
 Assumptions:
-* 8 m/h a day ~ 40 m/h a week ~ 168 m/h a month ~ one '''full time employee'''
+* One '''full time employee''' works 8 m/h a day ~ 40 m/h a week ~ 168 m/h a month
 The following metrics are suggested:
@@ Line 27: / Line 27: @@
 * 1/4 ftl (very low load)
 :: if average numb of hours required per week is 0-10
 == 2010 June to December Forecast ==