Jaguar Software Development Process

From UG

(Difference between revisions)
Jump to: navigation, search
(→PLAYERS)
Line 9: Line 9:
== PLAYERS ==
== PLAYERS ==
-
* Module Owners - Business Analyst who oversees and responsible for Business Analysis for entire CT2 module (Examples: Acc, Client, Ops)
+
* [[Module Owners]]
-
  * 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
-
  * Super users - end user who represents a group of users for specific feature
+
* [[Business Analyst]]
-
  * Business Analysts - somebody who is responsible for analyzing/documenting business needs, requirements
+
* [[Systems Analysts]]
-
  * IT Systems Analysts - somebody who is responsible for analyzing/documenting detailed technical design
+
* CT2 Board - top CT2 decision making committee
-
  * 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
-
 
+
-
  * Review Group - group of people who must review a feature/change, each particular feature/change has its own review group
+
== Teams per Component ==
== Teams per Component ==

Revision as of 16:05, 24 May 2010



Contents

Workflow

File:Development process March 26.jpg

PLAYERS

  • Super users - end user who represents a group of users for specific feature
  • 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

Teams per Component

See Mantis fields: 

p_BizAnalyst	  
p_Developer	  
p_ModOwner	 
p_QA	  
p_SysAnalyst


COMMUNICATION OPTIONS 

  * Media: emails, skype call, mantis, in person, etc
 
   * Pattern: all together, as a sequence, etc
Retrieved from "https://wiki.jaguarfreight.com/Jaguar_Software_Development_Process"
Personal tools