Jaguar Software Development Process

From UG

Revision as of 15:03, 7 May 2010 (edit) Denise (Talk | contribs) (→Teams per Component) ← Older edit		Current revision as of 07:00, 7 June 2010 (edit) (undo) Alex (Talk | contribs) m (moved Software Development Process to Jaguar Software Development Process)
(20 intermediate revisions not shown)
Line 1:		Line 1:
-	[[Category:PM (public)]]	+	[[Category:Software Development Processes]]
-	== Teams per Component ==	+	== Intro ==
		+	* parent mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=1768
-	* Client	+	== Workflow ==
-	** Module Owner: Simon	+
-	** BA: Tracie	+
-	** SA: Tira	+
-	** Dev: Sasha	+
-	* Acc "Internal" (Purchase, Admin, Reports)	+	[[File:Development process March 26.jpg]]
-	** Module Owner: Stephanie	+
-	** BA: Tracie	+
-	** SA: TBD	+
-	** Dev: Kostya	+
-	* Acc "External" (Sales, Rates Interface, Accrual Report)	+	=== Main idea ===
-	** Module Owner: Marc	+
-	** BA: Tracie	+
-	** SA: TBD	+
-	** Dev: Sasha	+
-	* Ops (Ops, Ops Admin)	+	At the core of workflow above is a sequence of "translations and furtherer elaborations" from MO to BA, from BA to SA and from SA to Developer. Module Owner formulates Core Need. Business Analyst translates it into Detailed [[Requirement]]s. System Analyst translates them into best possible Detailed Design. Finally, Developer translates design into program.
-	** Module Owner: Marc	+
-	** BA: Denise	+
-	** SA: TBD	+
-	** Dev: Kostya	+
-	* Ops Docs (Pdf, Xls Docs)	+	=== Players ===
-	** Module Owner: Marc	+
-	** BA: Denise	+
-	** SA: Tira	+
-	** Dev: Andriy	+
-	* Ops Reports (Ops, Statistical Reports)	+	* [[Module Owner]] (MO)
-	** Module Owner: Marc, Simon	+
-	** BA: Denise	+
-	** SA: TBD	+
-	** Dev: Kostya	+
-	== Workflow ==	+	* [[Business Analyst]] (BA)
-	[[File:Development process March 26.jpg]]	+	* [[Systems Analyst]] (SA)
-	== PLAYERS ==	+	* [[Systems Architect]]
-	* Module Owners - Business Analyst who oversees and responsible for Business Analysis for entire CT2 module (Examples: Acc, Client, Ops)	+	* [[Project Manager]]
-	* Regional Business Analysts - Business Analyst who represents user's needs/requirements from regional office	+	* CT2 [[Liaison]]
-	* Super users - end user who represents a group of users for specific feature	+	* [[CT2 Board]] - top CT2 decision making committee
-	* Business Analysts - somebody who is responsible for analyzing/documenting business needs, requirements	+	* [[Super user]] or [[Power User]] - end user who represents a group of users for specific feature
-	* IT Systems Analysts - somebody who is responsible for analyzing/documenting detailed technical design	+	* [[Review Group]] - group of people who must review a feature/change, each particular feature/change has its own review group
-	* CT2 Board - top CT2 decision making committee	+	=== Documentation in Wiki and Mantis ===
		+
		+	* see [[Spec_Example]]
		+
		+	== Teams per Component ==
		+
		+	See Mantis fields:
		+
		+	p_BizAnalyst
		+	p_Developer
		+	p_ModOwner
		+	p_QA
		+	p_SysAnalyst
-	* Review Group - group of people who must review a feature/change, each particular feature/change has its own review group
	== COMMUNICATION OPTIONS ==		== COMMUNICATION OPTIONS ==
-	* Media: emails, skype call, mantis, in person, etc	+	* Media: emails, skype call, mantis, in person, etc
-	* Pattern: all together, as a sequence, etc	+	* Pattern: all together, as a sequence, etc
		+
		+	== See Also ==
		+
		+	* [[CT2_Development_Process]]
		+	* [[CT2_Development_Process v2]]

---

Current revision as of 07:00, 7 June 2010

Contents 1 Intro 2 Workflow 2.1 Main idea 2.2 Players 2.3 Documentation in Wiki and Mantis 3 Teams per Component 4 COMMUNICATION OPTIONS 5 See Also

[edit] Intro

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

[edit] Workflow

[edit] Main idea

At the core of workflow above is a sequence of "translations and furtherer elaborations" from MO to BA, from BA to SA and from SA to Developer. Module Owner formulates Core Need. Business Analyst translates it into Detailed Requirements. System Analyst translates them into best possible Detailed Design. Finally, Developer translates design into program.

[edit] Players

• Module Owner (MO)

• Business Analyst (BA)

• Systems Analyst (SA)

• Systems Architect

• Project Manager

• CT2 Liaison

• CT2 Board - top CT2 decision making committee

• Super user or Power User - end user who represents a group of users for specific feature

• Review Group - group of people who must review a feature/change, each particular feature/change has its own review group

[edit] Documentation in Wiki and Mantis

• see Spec_Example

[edit] Teams per Component

See Mantis fields:

p_BizAnalyst	  
p_Developer	  
p_ModOwner	 
p_QA	  
p_SysAnalyst

[edit] COMMUNICATION OPTIONS

• Media: emails, skype call, mantis, in person, etc

• Pattern: all together, as a sequence, etc

[edit] See Also

• CT2_Development_Process
• CT2_Development_Process v2