Roles

From UG

(Difference between revisions)

Jump to: navigation, search

Current revision as of 23:53, 4 July 2010

[edit] About

This article is about Software Dev Team Organization and Roles.

[edit] Intro

It is very important to clearly define roles and responsibilities.

Please note that on small projects, several roles may be performed by one person.

[edit] Roles

[edit] Chief Architect and Chief Project Manager CAPM

Job Descr and Responibilities:

In there are multiple projects, in general, some for the same system and some for others then there is a need for a top manager/engineer who coordinates all projects.

Planning and resource allocation for all projects.

Reporting progress to sponsors / stakeholders. Discussing new projects with them.

Make sure that several independent projects affecting same system are coordinated.

Right now Alex plays this role.

Skills

In there are multiple projects, in general, some for the same system and some for others then there is a need for a top manager/engineer who coordinates all projects.

[edit] Project Manager PM

[edit] Skills

PM could be technical or non-technical. Both options would work. Technical is better but more expensive and rare.

[edit] Systems Analyst SA

[edit] Business Analyst BA

[edit] Development Manager DM

[edit] Quality Engineer QE

[edit] Support Engineer SE

[edit] Documentation Engineer DE

Job Descr and Responibilities: Documentation is critical for distributed teams.

It must be of hight quality and up to date.

It might be initiated by various teams. Doc engineer shoul provide advice at the beginning and at the end he must become an owner and maintain, keep up to date, improve docs.