CT2 Resources Demand Supply Allocation

From UG

Revision as of 17:07, 17 May 2010 (edit) Alex (Talk | contribs) (→Ops Reps Component) ← Older edit		Revision as of 17:10, 17 May 2010 (edit) (undo) Alex (Talk | contribs) (→Metrics) Newer edit →
Line 17:		Line 17:
	Assumptions:		Assumptions:
-	* One '''full time employee''' works 8 m/h a day ~ 40 m/h a week ~ 168 m/h a month	+	* One '''full time employee''' works 8 m/h a day ~ 40 m/h a week ~ 160 m/h a month
		+	* One Sprint ~ One month
	The following metrics are suggested:		The following metrics are suggested:

---

Revision as of 17:10, 17 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 Integration with TMS 2.2.2 Trucking Domestic Optimization 2.2.3 Rates 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

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 ~ 160 m/h a month
• One Sprint ~ One 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:
  • emh = 0-10 per week

• project 1) Re-design cost mapping and P&L for CTs, Groups, Masters
  • emh = TBD
  • deadline: asap

• project 2) see Category:Salesman
  • emh = TBD
  • deadline: asap

Client Component

• continuous support/tweaking:
  • emh = 10-20 per week

• project 1) see #0001707 Replace Skype with our own Instant Messaging feature
  • emh = TBD
  • deadline: asap

• project 2) see #0001999 Create Agent Interface component/application
  • emh = TBD
  • deadline: asap

Ops Component

• continuous support/tweaking:
  • emh = 10-20 per week

• project 1) ...
  • emh = TBD

Ops Pdfs Component

• continuous support/tweaking:
  • emh = 10-20 per week

Ops Reps Component

• continuous support/tweaking:
  • emh = when new reports are required then 20-30 per week else 10-20 per week

New Modules

Integration with TMS

Trucking Domestic Optimization

Rates 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