CT2 Development Process
From UG
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 CT2 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 - biz expert who submits detailed biz requirements for the component. (Simon)
Sys analyst - IT expert who translates detailed biz requirements into specs.
- proj manager
- QA
- developer
- graphic designer
- timeboxing
- scoping
