CT2 Resources Demand Supply Allocation

From UG

(Difference between revisions)
Jump to: navigation, search
(→Metrics)
(→2010 June to December Forecast)
Line 48: Line 48:
==== Acc Component ====
==== Acc Component ====
-
* ''continuous support/tweaking:''   
+
* ''continuous bug-fix/tweaking:''   
-
** emh = 0-10 per week
+
** emh low = 5 per week
 +
** emh high = 10 per week
* project 1) Re-design cost mapping and P&L for CTs, Groups, Masters
* project 1) Re-design cost mapping and P&L for CTs, Groups, Masters
Line 61: Line 62:
==== Client Component ====
==== Client Component ====
-
* ''continuous support/tweaking:''  
+
* ''continuous bug-fix/tweaking:''    
** emh = 10-20 per week
** emh = 10-20 per week
Line 82: Line 83:
==== Ops Pdfs Component ====
==== Ops Pdfs Component ====
-
* ''continuous support/tweaking:''  
+
* ''continuous bug-fix/tweaking:''    
** emh = 10-20 per week
** emh = 10-20 per week
==== Ops Reps Component ====
==== Ops Reps Component ====
-
* ''continuous support/tweaking:''  
+
* ''continuous bug-fix/tweaking:''    
** emh = when new reports are required then 20-30 per week else 10-20 per week
** emh = when new reports are required then 20-30 per week else 10-20 per week

Revision as of 17:18, 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

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

Client Component

  • continuous bug-fix/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 bug-fix/tweaking:
    • emh = 10-20 per week

Ops Reps Component

  • continuous bug-fix/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

Retrieved from "https://wiki.jaguarfreight.com/CT2_Resources_Demand_Supply_Allocation"
Personal tools