CT2 Resources Demand Supply Allocation

From UG

Revision as of 17:47, 11 May 2010 (edit) Alex (Talk | contribs) (→2010 June to December Forecast) ← Older edit		Current revision as of 07:54, 5 July 2010 (edit) (undo) Alex (Talk | contribs)
(31 intermediate revisions not shown)
Line 1:		Line 1:
	[[Category:PM (public)]]		[[Category:PM (public)]]
		+
		+	== General Info ==
	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 Software Development!  ))		We need to build smart Supply Chain for Software Development!  ))
		+
		+	* parent mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=2054
		+
		+	== 2009 Forecast spreadsheet ==
		+
		+	See spreadsheet attached to http://mantis.jaguarfreight.com/mantis/view.php?id=2054
	== Metrics ==		== Metrics ==
-	=== ftl ===	+	=== Assumptions ===
-	It is proposed to use '''ftl''' (full time load) unit of measurement. This is to measure demand for IT staff (SAs, BAs, developers, QAs).	+	* One '''full time employee''' works 8 m/h a day ~ 40 m/h a week ~ 160 m/h a month
		+	* One Sprint ~ One month
-	Assumptions:	+	=== Types of load ===
-	* 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:	+	There are 2 types of activities:
-	==== full load ====	+	* continuous: bugfix, tweaking (small to medium changes)
		+	* projects
-	* 1 ftl (full load)	+	=== FTD ===
-	:: if average numb of hours required per week is 30 to 40	+
-	==== medium load ====	+	FTD = full time developer
-	* 3/4 ftl (med load)	+	==== 1 FTD ====
-	:: if average numb of hours required per week is 20 to 30	+
-	==== low load ====	+	40 h per week ~ 160 per month
-	* 1/2 ftl (low load)	+	==== 1/4 FTD ====
-	:: if average numb of hours required per week is 10 to 20	+
-	==== very low load ====	+	10 h per week ~ 40 per month
-	* 1/4 ftl (very low load)	+	==== 1/2 FTD ====
-	:: if average numb of hours required per week is 0 to 10	+
		+	20 h per week ~ 80 per month
	== 2010 June to December Forecast ==		== 2010 June to December Forecast ==
Line 42:		Line 49:
	==== Acc Component ====		==== Acc Component ====
-	* continuous support/tweaking (1/4 ftl)	+	* ''continuous bug-fix/tweaking:''
		+	** emh low = 5 per week
		+	** emh high = 10 per week
-	* projects:	+	* project: ''P&L Re-design''
-	:: need to re-design/fix mapping of cost mapping against CTs and groups of CTs and P/L	+	** Re-design cost mapping and P&L for CTs, Groups, Masters
-	:: sales person feature / commission report	+	** emh = TBD
		+	** deadline: asap
		+
		+	* project  ''Salesman module''
		+	** see [[:Category:Salesman]]
		+	** emh = TBD
		+	** deadline: asap
	==== Client Component ====		==== Client Component ====
		+
		+	* ''continuous bug-fix/tweaking:''
		+	** emh low = 10 per week
		+	** emh high = 30 per week
		+
		+	* project: ''IM feature''
		+	** see #0001707 Replace Skype with our own Instant Messaging feature
		+	** emh = TBD
		+	** deadline: asap
		+
		+	* project: ''Agent Interface''
		+	** see #0001999 Create Agent Interface component/application
		+	** emh = TBD
		+	** deadline: asap
	==== Ops Component ====		==== Ops Component ====
		+
		+	* ''continuous bug-fix/tweaking:''
		+	** emh low = 20 per week
		+	** emh high = 40 per week (could be even more)
		+
		+	* project:  TBD
		+	** emh = TBD
	==== Ops Pdfs Component ====		==== 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)
		+
		+	* project:  TBD
		+	** emh = TBD
	==== Ops Reps Component ====		==== 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)
		+
		+	* project: ''All fields''
		+	** #0001998  Have all CT fields available on all CT reports
		+	** emh = TBD
	=== New Modules ===		=== New Modules ===
-	==== Trucking Domestic Optimization ====	+	==== TMS Integration ====
		+
		+	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: June-Aug
		+	** length low: 1 month
		+	** length high: 3 month
		+	** emh low = 30 per week
		+	** emh high = 40 per week
		+
		+	==== CT2 TMS features (Trucking Domestic Optimization) ====
		+
		+	Jaguar plans to add a number of complex TMS features to CT2
		+
		+	* Estimates
		+	** start: July-September
		+	** length low: 6 month
		+	** length high: 12 month
		+	** emh low = 20 per week
		+	** emh high = 40 per week
	==== Rates Interface ====		==== Rates Interface ====
-	==== Agent Interface ====	+	Jaguar plans to add Rates Interface.
		+
		+	* Estimates
		+	** start: July-September
		+	** length low: 2 month
		+	** length high: 3 month
		+	** emh low = 20 per week
		+	** emh high = 30 per week
	==== EDI ====		==== EDI ====
		+
		+	Jaguar plans to integrate with Clients, Vendors, etc through EDI (for example receive Traffic Sheets, send Invoices). Please note that there many companies Jaguar interface so if this is successful then EDI could be a constant task.
		+
		+	* Estimates
		+	** start: asap
		+	** length low: 2 month
		+	** length high: 12 month
		+	** emh low = 20 per week
		+	** emh high = 40 per week
	==== Inventory Management ====		==== Inventory Management ====
		+
		+	Jaguar plans to create Inventory Management components (as a CT2 feature or stand alone application)
		+
		+	* Estimates
		+	** start: July - Aug
		+	** length low: 6 month
		+	** length high: 12 month
		+	** emh low = 20 per week
		+	** emh high = 40 per week
	==== www.jaguarfreight.com website re-design ====		==== www.jaguarfreight.com website re-design ====
		+
		+	Jaguar plans to integrate with Clients, Vendors, etc through EDI (for example receive Traffic Sheets, send Invoices)
		+
		+	* Estimates
		+	** start: asap
		+	** length low: 2 month
		+	** length high: 4 month
		+	** emh low = 20 per week
		+	** emh high = 40 per week
		+
		+	==== Help system ====
		+
		+	We need "help system" for CT2
		+
		+	Mantis: 2087 (CT2 Help System) http://mantis.jaguarfreight.com/mantis/view.php?id=2087
		+
		+	* Estimates
		+	** Start: when resources have free time
		+	** Prio-ty: low
		+	** start: asap
		+	** length low: 2 month
		+	** length high: 4 month
		+	** emh low = 20 per week
		+	** emh high = 40 per week
	=== Etc ===		=== Etc ===
-	==== Development based on Requirements not Detailed Design ====	+	== Misc ==
		+
		+	=== Development based on Requirements not Detailed Design ===
	2 possible options:		2 possible options:
Line 79:		Line 203:
	Both options would increase numb of hours required in Remote Team		Both options would increase numb of hours required in Remote Team
		+
		+	== History ==
		+	=== Ver 1 ===
		+	completed.

---

Current revision as of 07:54, 5 July 2010

Contents 1 General Info 2 2009 Forecast spreadsheet 3 Metrics 3.1 Assumptions 3.2 Types of load 3.3 FTD 3.3.1 1 FTD 3.3.2 1/4 FTD 3.3.3 1/2 FTD 4 2010 June to December Forecast 4.1 Existing modules 4.1.1 Acc Component 4.1.2 Client Component 4.1.3 Ops Component 4.1.4 Ops Pdfs Component 4.1.5 Ops Reps Component 4.2 New Modules 4.2.1 TMS Integration 4.2.2 CT2 TMS features (Trucking Domestic Optimization) 4.2.3 Rates Interface 4.2.4 EDI 4.2.5 Inventory Management 4.2.6 www.jaguarfreight.com website re-design 4.2.7 Help system 4.3 Etc 5 Misc 5.1 Development based on Requirements not Detailed Design 6 History 6.1 Ver 1

[edit] General Info

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! ))

• parent mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=2054

[edit] 2009 Forecast spreadsheet

See spreadsheet attached to http://mantis.jaguarfreight.com/mantis/view.php?id=2054

[edit] Metrics

[edit] 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

[edit] Types of load

There are 2 types of activities:

• continuous: bugfix, tweaking (small to medium changes)
• projects

[edit] FTD

FTD = full time developer

[edit] 1 FTD

40 h per week ~ 160 per month

[edit] 1/4 FTD

10 h per week ~ 40 per month

[edit] 1/2 FTD

20 h per week ~ 80 per month

[edit] 2010 June to December Forecast

[edit] Existing modules

[edit] Acc Component

• continuous bug-fix/tweaking:
  • emh low = 5 per week
  • emh high = 10 per week

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

• project Salesman module
  • see Category:Salesman
  • emh = TBD
  • deadline: asap

[edit] Client Component

• continuous bug-fix/tweaking:
  • emh low = 10 per week
  • emh high = 30 per week

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

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

[edit] Ops Component

• continuous bug-fix/tweaking:
  • emh low = 20 per week
  • emh high = 40 per week (could be even more)

• project: TBD
  • emh = TBD

[edit] 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)

• project: TBD
  • emh = TBD

[edit] 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)

• project: All fields
  • #0001998 Have all CT fields available on all CT reports
  • emh = TBD

[edit] New Modules

[edit] TMS Integration

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: June-Aug
  • length low: 1 month
  • length high: 3 month
  • emh low = 30 per week
  • emh high = 40 per week

[edit] CT2 TMS features (Trucking Domestic Optimization)

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

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

[edit] Rates Interface

Jaguar plans to add Rates Interface.

• Estimates
  • start: July-September
  • length low: 2 month
  • length high: 3 month
  • emh low = 20 per week
  • emh high = 30 per week

[edit] EDI

Jaguar plans to integrate with Clients, Vendors, etc through EDI (for example receive Traffic Sheets, send Invoices). Please note that there many companies Jaguar interface so if this is successful then EDI could be a constant task.

• Estimates
  • start: asap
  • length low: 2 month
  • length high: 12 month
  • emh low = 20 per week
  • emh high = 40 per week

[edit] Inventory Management

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

• Estimates
  • start: July - Aug
  • length low: 6 month
  • length high: 12 month
  • emh low = 20 per week
  • emh high = 40 per week

[edit] www.jaguarfreight.com website re-design

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

• Estimates
  • start: asap
  • length low: 2 month
  • length high: 4 month
  • emh low = 20 per week
  • emh high = 40 per week

[edit] Help system

We need "help system" for CT2

Mantis: 2087 (CT2 Help System) http://mantis.jaguarfreight.com/mantis/view.php?id=2087

• Estimates
  • Start: when resources have free time
  • Prio-ty: low
  • start: asap
  • length low: 2 month
  • length high: 4 month
  • emh low = 20 per week
  • emh high = 40 per week

[edit] Etc

[edit] Misc

[edit] 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

[edit] History

[edit] Ver 1

completed.