CT2 Resources Demand Supply Allocation

From UG

(Difference between revisions)

Jump to: navigation, search

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

Metrics

There are 2 types of activities:

continuous: bugfix, tweaking (small to medium changes)
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: 30 to 40 per week ~ 120-160 per month

medium load

3/4 ftl (med load)

if average numb of hours required: 20 to 30 per week ~ 80-120 per month

low load

1/2 ftl (low load)

if average numb of hours required: 10 to 20 per week ~ 40-80 per month

very low load

1/4 ftl (very low load)

if average numb of hours required: 1 to 10 per week ~ 4-40 per month

2010 June to December Forecast

Existing modules

Acc Component

continuous bug-fix/tweaking:
- emh low = 5 per week
- emh high = 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 bug-fix/tweaking:
- emh low = 10 per week
- emh high = 30 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 bug-fix/tweaking:
- emh low = 20 per week
- emh high = 40 per week (could be even more)

projects: TBD
- emh = TBD

Ops Pdfs Component

continuous bug-fix/tweaking:
- emh low = 10 per week (will be getting lower soon)
- emh high = 20 per week (will be getting lower soon)

projects: TBD
- emh = TBD

Ops Reps Component

continuous bug-fix/tweaking:
- emh low = 10 per week (will be getting lower soon)
- emh high = 30 per week (will be lower if no new reports requested)

projects: #0001998 Have all CT fields available on all CT reports
- emh = TBD

New Modules

Integration with TMS

Jaguar is planning to purchase a large TMS system that has to be integrated with CT2. This would mean:

supporting real time integration / flow of data between 2 systems (one or both directions)
potentially adding additional fields and features to support above

Estimates
- start: mid June
- length: 1-3 month
- emh low = 20 per week
- emh high = 40 per week

Trucking Domestic Optimization (TMS features)

Jaguar plans to add a number of complex TMS features to CT2

Estimates
- start: July-September
- length: 6-12 months
- emh low = 20 per week
- emh high = 40 per week

Rates Interface

Jaguar plans to add Rates Interface.

Estimates
- start: July-September
- length: 2-3 months
- emh low = 20 per week
- emh high = 40 per week

EDI

Jaguar plans to integrate with Clients, Vendors, etc through EDI (for example receive Traffic Sheets, send Invoices)

Estimates
- start: asap
- length: TBD
- emh low = 20 per week
- emh high = 40 per week

Inventory Management

Jaguar plans to create Inventory Management components (as a CT2 feature or stand alone application)

Estimates
- start: TBD
- length: TBD
- emh low = 20 per week
- emh high = 40 per week

www.jaguarfreight.com website re-design