CT2 Resources Demand Supply Allocation

From UG

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

Metrics

There are 2 types of activities:

• continuous
• projects

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, Support Engineers).

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:

full load

• 1 ftl (full load)

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

medium load

• 3/4 ftl (med load)

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

low load

• 1/2 ftl (low load)

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

very low load

• 1/4 ftl (very low load)

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

2010 June to December Forecast

Existing modules

Acc Component

• continuous support/tweaking (1/4 ftl)

• projects:

need to re-design/fix mapping of cost mapping against CTs and groups of CTs and P/L

sales person feature / commission report

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