You are here: Home > UMP life cycle > Project team structuring


	Life cycle model	Development process	Support process	Organizational process	Product
Process structuring \| Team structuring \| Proactive \| Iterative \| Agile \| Cooperation \| Documenting \| ISO/IEC 12207 \| Project types \| Models & Tools

References:

UMP glossary
Bibliography
Conventions & Notation

Project team structuring

1. In any moment every project participant has a definite role.

2. Roles could be incompatible — compatibility matrix:

F - Forbidden
L - Limited, requires reasonable motivation; Or limited scope -- i.e. not allow to program and test one task, but could be allowed to program one and test another (also bad)
A - Allowed

3. Submit subsystem to a small independent group for experiments, detailed design and programming

Rationale: a subsystem shall be small enough (but not smaller) to be implemented rapidly (~1 month) by a limited group (1-4 programmers). Such strategy utilizes the known fact that small groups develop software in less time and/or on a smaller budget.