Jaguar Software Development Process

From UG

Revision as of 15:03, 7 May 2010 (edit) Denise (Talk | contribs) (→Teams per Component) ← Older edit		Revision as of 15:56, 24 May 2010 (edit) (undo) Alex (Talk | contribs) (→Teams per Component: replaced with links to mantis foirlds) Newer edit →
Line 3:		Line 3:
	== Teams per Component ==		== Teams per Component ==
-	* Client	+	See Mantis fields:
-	** Module Owner: Simon	+
-	** BA: Tracie	+
-	** SA: Tira	+
-	** Dev: Sasha	+
-	* Acc "Internal" (Purchase, Admin, Reports)	+	p_BizAnalyst
-	** Module Owner: Stephanie	+	p_Developer
-	** BA: Tracie	+	p_ModOwner
-	** SA: TBD	+	p_QA
-	** Dev: Kostya	+	p_SysAnalyst
-		+
-	* Acc "External" (Sales, Rates Interface, Accrual Report)	+
-	** Module Owner: Marc	+
-	** BA: Tracie	+
-	** SA: TBD	+
-	** Dev: Sasha	+
-		+
-	* Ops (Ops, Ops Admin)	+
-	** Module Owner: Marc	+
-	** BA: Denise	+
-	** SA: TBD	+
-	** Dev: Kostya	+
-		+
-	* Ops Docs (Pdf, Xls Docs)	+
-	** Module Owner: Marc	+
-	** BA: Denise	+
-	** SA: Tira	+
-	** Dev: Andriy	+
-		+
-	* Ops Reports (Ops, Statistical Reports)	+
-	** Module Owner: Marc, Simon	+
-	** BA: Denise	+
-	** SA: TBD	+
-	** Dev: Kostya	+
	== Workflow ==		== Workflow ==

---

Revision as of 15:56, 24 May 2010

Contents 1 Teams per Component 2 Workflow 3 PLAYERS 4 COMMUNICATION OPTIONS

Teams per Component

See Mantis fields:

p_BizAnalyst	  
p_Developer	  
p_ModOwner	 
p_QA	  
p_SysAnalyst

Workflow

PLAYERS

* Module Owners - Business Analyst who oversees and responsible for Business Analysis for entire CT2 module (Examples: Acc, Client, Ops)

 * Regional Business Analysts - Business Analyst who represents user's needs/requirements from regional office

 * Super users - end user who represents a group of users for specific feature

 * Business Analysts - somebody who is responsible for analyzing/documenting business needs, requirements

 * IT Systems Analysts - somebody who is responsible for analyzing/documenting detailed technical design

 * CT2 Board - top CT2 decision making committee

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

COMMUNICATION OPTIONS

  * Media: emails, skype call, mantis, in person, etc
 
   * Pattern: all together, as a sequence, etc