Jaguar Software Development Process

From UG

(Difference between revisions)
Jump to: navigation, search
 
(18 intermediate revisions not shown)
Line 1: Line 1:
-
[[Category:PM (public)]]
+
[[Category:Software Development Processes]]
-
 
+
 +
== Intro ==
 +
* parent mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=1768
== Workflow ==
== Workflow ==
Line 7: Line 8:
[[File:Development process March 26.jpg]]
[[File:Development process March 26.jpg]]
-
== PLAYERS ==
+
=== Main idea ===
-
* Module Owners - Business Analyst who oversees and responsible for Business Analysis for entire CT2 module (Examples: Acc, Client, Ops)
+
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.
-
  * Regional Business Analysts - Business Analyst who represents user's needs/requirements from regional office
+
=== Players ===
-
  * Super users - end user who represents a group of users for specific feature
+
* [[Module Owner]] (MO)
-
  * Business Analysts - somebody who is responsible for analyzing/documenting business needs, requirements
+
* [[Business Analyst]] (BA)
-
  * IT Systems Analysts - somebody who is responsible for analyzing/documenting detailed technical design
+
* [[Systems Analyst]] (SA)
-
  * CT2 Board - top CT2 decision making committee
+
* [[Systems Architect]]
-
  * Review Group - group of people who must review a feature/change, each particular feature/change has its own review group
+
* [[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
 +
 
 +
=== Documentation in Wiki and Mantis ===
 +
 
 +
* see [[Spec_Example]]
== Teams per Component ==
== Teams per Component ==
Line 36: Line 49:
== 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

[edit] Intro

[edit] Workflow

File:Development process March 26.jpg

[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

  • 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

[edit] Documentation in Wiki and Mantis

[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

Personal tools