CT2 Resources Demand Supply Allocation

From UG

Revision as of 17:27, 11 May 2010 (edit) Alex (Talk | contribs) (→Metrics) ← Older edit		Revision as of 17:33, 11 May 2010 (edit) (undo) Alex (Talk | contribs) (→Metrics) Newer edit →
Line 16:		Line 16:
	The following metrics are suggested:		The following metrics are suggested:
-	* 1 ftl (high/full load)	+	==== full load ====
-	:: if average numb of hours required per week is 30-40	+
		+	* 1 ftl (full load)
		+	:: if average numb of hours required per week is 30 to 40
		+
		+	==== medium load ====
	* 3/4 ftl (med load)		* 3/4 ftl (med load)
-	:: if average numb of hours required per week is 20-30	+	:: if average numb of hours required per week is 20 to 30
		+
		+	==== low load ====
	* 1/2 ftl (low load)		* 1/2 ftl (low load)
-	:: if average numb of hours required per week is 10-20	+	:: if average numb of hours required per week is 10 to 20
		+
		+	==== very low load ====
	* 1/4 ftl (very low load)		* 1/4 ftl (very low load)
-	:: if average numb of hours required per week is 0-10	+	:: if average numb of hours required per week is 0 to 10
	== 2010 June to December Forecast ==		== 2010 June to December Forecast ==

---

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

Contents 1 Metrics 1.1 ftl 1.1.1 full load 1.1.2 medium load 1.1.3 low load 1.1.4 very low load 2 2010 June to December Forecast 2.1 Existing modules 2.1.1 Acc Component 2.1.2 Client Component 2.1.3 Ops Component 2.1.4 Ops Pdfs Component 2.1.5 Ops Reps Component 2.2 New Modules 2.2.1 Trucking Domestic Optimization 2.2.2 Rates Interface 2.2.3 Agent Interface 2.2.4 EDI 2.2.5 Inventory Management 2.2.6 www.jaguarfreight.com website re-design 2.3 Etc 2.3.1 Development based on Requirements not Detailed Design

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:

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

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