CT2 Resources Demand Supply Allocation
From UG
(Difference between revisions)
Line 3: | Line 3: | ||
This article is about Demand for CT2 features and related Supply / Allocation of Human Resources. | This article is about Demand for CT2 features and related Supply / Allocation of Human Resources. | ||
- | We need to build smart Supply Chain for | + | We need to build smart Supply Chain for Software Development! )) |
== Metrics == | == Metrics == |
Revision as of 16:28, 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 |
Metrics
ftl
ftl - full time load
Assumptions:
- 8 m/h a day ~ 40 m/h a week ~ 168 m/h a month ~ one full time employee
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