Jaguar Software Development Process
From UG
(Difference between revisions)
(→Teams per Component: replaced with links to mantis foirlds) |
|||
| Line 1: | Line 1: | ||
[[Category:PM (public)]] | [[Category:PM (public)]] | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
== Workflow == | == Workflow == | ||
| Line 30: | Line 22: | ||
* 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 == | ||
| + | |||
| + | See Mantis fields: | ||
| + | |||
| + | p_BizAnalyst | ||
| + | p_Developer | ||
| + | p_ModOwner | ||
| + | p_QA | ||
| + | p_SysAnalyst | ||
| + | |||
== COMMUNICATION OPTIONS == | == COMMUNICATION OPTIONS == | ||
Revision as of 15:57, 24 May 2010
Contents |
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
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
