Roles
From UG
(Difference between revisions)
(→Documentation Engineer) |
(→Roles) |
||
| Line 14: | Line 14: | ||
== Roles == | == Roles == | ||
| - | === Project Manager === | + | === Project Manager PM === |
| - | === Systems Analyst === | + | === Systems Analyst SA === |
| + | === Business Analyst BA === | ||
| + | === Development Manager DM === | ||
| - | === Documentation Engineer === | + | * Systems Architect - same person? |
| + | |||
| + | === Quality Engineer QE === | ||
| + | |||
| + | === Support Engineer SE === | ||
| + | |||
| + | === Documentation Engineer DE === | ||
'''Job Descr and Responibilities:''' | '''Job Descr and Responibilities:''' | ||
Revision as of 23:42, 4 July 2010
Contents |
About
This article is about Software Dev Team Organization and Roles.
Intro
It is very important to clearly define roles and responsibilities.
Please note that small projects, several roles may be performed by one person.
Roles
Project Manager PM
Systems Analyst SA
Business Analyst BA
Development Manager DM
- Systems Architect - same person?
Quality Engineer QE
Support Engineer SE
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.
Skills
- good command of language (primary language of documentation)
- very good writing skills
- clarity in thinking
- analytical
- hands on experience in technology he is writing about (he is an engineer!)
- creativity
