CT2 Development Process
From UG
(→Actors, Teams and Roles) |
(→Actors, Teams and Roles) |
||
| Line 13: | Line 13: | ||
== Actors, Teams and Roles == | == Actors, Teams and Roles == | ||
| - | All people related to CT2 Component fall into groups: (in italic example given for Client App | + | All people related to CT2 Component fall into groups: (in italic example given for Client App component) |
'''Future users of CT2''' - operators, management, etc. (''non jag operators and management'') | '''Future users of CT2''' - operators, management, etc. (''non jag operators and management'') | ||
Revision as of 03:24, 23 July 2009
This article defines what methodology, roles, workflow, etc we use.
Overview
CT2 System consists of CT2 components (Client App, Ops, OpsReps, Acc. etc).
We development each component separately. It has its own team, project plan, etc.
Methodology
We use our own methodology that is influenced by Scrum, Agile, Waterfall, Mantis, Outsourcing
Actors, Teams and Roles
All people related to CT2 Component fall into groups: (in italic example given for Client App component)
Future users of CT2 - operators, management, etc. (non jag operators and management)
Acceptance board (demo meeting) - group of people who makes final decision about acceptance, tweaks, course of the project. (sometimes Simon alone, sometimes Simon, Marc, Alex, Tira together)
Biz analyst/architect - biz expert (Simon)
- submits detailed biz requirements for the component.
Sys analyst/Architect - IT expert (Tira)
- translates detailed biz requirements into specs.
Project manager - time/scope management expert (Tira)
- accountable for reaching the stated project objectives
- managing high level of proj plan
Development Lead - leader of the development team,
- QA
- developer
- graphic designer
- timeboxing
- scoping
