CT2 Development Process

From UG

Revision as of 02:25, 23 July 2009 (edit) Alex (Talk | contribs) ← Older edit		Revision as of 02:51, 23 July 2009 (edit) (undo) Alex (Talk | contribs) (→Actors, Teams and Roles) Newer edit →
Line 13:		Line 13:
	== Actors, Teams and Roles ==		== Actors, Teams and Roles ==
-	All people related to	+	All people related to CT2 Component fall into groups:
		+
		+	* future users of CT2 (operators, management, etc)
		+	* acceptance board
		+	* biz analyst
		+	* sys analyst
		+	* proj manager
		+	* QA
		+	* developer
		+	* graphic designer
		+
		+
		+	* timeboxing
		+	* scoping
	[[Category:PM]]		[[Category:PM]]

---

Revision as of 02:51, 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:

• future users of CT2 (operators, management, etc)
• acceptance board
• biz analyst
• sys analyst
• proj manager
• QA
• developer
• graphic designer

• timeboxing
• scoping