CT2 Development Process

From UG

Revision as of 03:24, 23 July 2009 (edit) Alex (Talk | contribs) (→Actors, Teams and Roles) ← Older edit		Revision as of 03:28, 23 July 2009 (edit) (undo) Alex (Talk | contribs) (→Actors, Teams and Roles) Newer edit →
Line 20:		Line 20:
	'''Biz analyst/architect''' - biz expert (''Simon'')		'''Biz analyst/architect''' - biz expert (''Simon'')
-	* submits detailed '''biz requirements''' for the component.	+	* invents detailed '''biz requirements''' for the component
		+	* transfers these requirements to Sys Analyst
	'''Sys analyst/Architect''' - IT expert (''Tira'')		'''Sys analyst/Architect''' - IT expert (''Tira'')
-	* translates detailed biz requirements into '''specs'''.	+	* translates detailed biz requirements into '''specs'''
		+	* transfers specs to development team
	'''Project manager''' - time/scope management expert (''Tira'')		'''Project manager''' - time/scope management expert (''Tira'')
	* accountable for reaching the stated project objectives		* accountable for reaching the stated project objectives
	* managing '''high level''' of proj plan		* managing '''high level''' of proj plan
		+
		+	'''Development team''' consists of:
		+	* nnn
	'''Development Lead''' - leader of the development team,		'''Development Lead''' - leader of the development team,

---

Revision as of 03:28, 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)

• 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

Development team consists of:
* nnn

Development Lead - leader of the development team,

• QA
• developer
• graphic designer

• timeboxing
• scoping