Software company

For example, having sub-teams spread in different time zones may allow a 24-hour company working day, if the teams, systems, and procedures are well established.

In bigger organizations, there are in general two models of the hierarchy: All the teams are fully independent and they work separately on the different projects.

The structure is quite simple and all the employees reports to one person, what make the situation quite clear however it is not a good solution in terms of knowledge exchange and optimal usage of human resources.

These can include: There are also some methodologies which combine both, such as the spiral model, Rational Unified Process (RUP)[7] or MSF.

The UML sequence diagram of interaction between these groups may look like: At each stage a different group plays a key role, however each type of role must be involved throughout the whole development process: Software companies possess various systems and procedures implemented and working internally across all the sub-teams.

Typical structure of a software company
Matrix structure
The general interaction between the four main groups
Pyramid showing risk, time, and financial cost of introducing changes