CT2 Development Process
From UG
This article defines what methodology, roles, workflow, etc we use.
Contents |
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)
Business (Client/Sponsor) Team
Biz analyst/architect - biz expert (Simon)
- invents detailed biz requirements for the component
- transfers these requirements to Sys Analyst
Sys analyst/Architect - IT expert (Tira)
- translates detailed biz requirements into specs
- transfers specs to development team
Project manager - time/scope management expert (Tira)
- accountable for reaching the stated project objectives
- managing high level of proj plan
Software Development (Vendor) team
Development Lead - leader of the development team (Slava)
- coordinates development effort
- manages resources
- manages detailed development schedule that includes development, bugfix, QA, graphics
QA engineer
- makes sure that specs are complete
- creates test plans
- runs test plans
- forwards bugs to developer
developer
- makes sure specs are complete
- implements new sub-components, changes, tweaks, bug fixes
- graphic designer
- timeboxing
- scoping
