CT2 Development Process

From UG

Revision as of 03:50, 23 July 2009 (edit) Alex (Talk | contribs) (→Software Development (Vendor) team) ← Older edit		Revision as of 03:50, 23 July 2009 (edit) (undo) Alex (Talk | contribs) (→Software Development (Vendor) team) Newer edit →
Line 58:		Line 58:
	''' graphic designer'''		''' graphic designer'''
-
-
	== timeboxing ==		== timeboxing ==

---

Revision as of 03:50, 23 July 2009

This article defines what methodology, roles, workflow, etc we use.

Contents 1 Overview 2 Methodology 3 Users 4 Business (Client/Sponsor) Team 5 Software Development (Vendor) team 6 timeboxing 7 scoping

Overview

CT2 System consists of CT2 components (Client App, Ops, OpsReps, Acc. etc).

We developmen 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.

(in italic example given for Client App component)

Users

Future users of CT2 - operators, management, etc. (non jag operators and management)

Business (Client/Sponsor) Team

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)

• 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
• gets regular updates from developer, QA, graphic designer regarding deadlines
• if there is a chance for ETA to be postponed then he immediately notifies Project Manager and they both decide what to do: move tasks around, add resources or push ETA forward

QA engineer

• makes sure that specs are complete
• creates test plans
• runs test plans
• forwards bugs to developer
• provides ETA for his work to Development Lead
• must immedialy notify Development Lead if his ETA can slip

developer

• makes sure specs are complete
• implements new sub-components, changes, tweaks, bug fixes
• deploy, forwards his work to QA
• provides ETA for his work to Development Lead
• must immedialy notify Development Lead if his ETA can slip

graphic designer

timeboxing

scoping