The term team is used loosely around business. The book prefers the term jelled team. The idea of a team coming together and acting as one.
If team members are working together, and strongly tied to one another, then they will increase their performance and productivity. The whole is greater than the sum of the parts.
The book recommends that the team have a sense of purpose and a sense of trust in one another.
Team Structure
The best structure often depends upon the management style of the organization.
Closed Paradigm – a traditional hierarchy of structure
Random Paradigm – structured loosely and depends on self motivation. Tends to work well in new areas with technology break throughs, but not as well under normal circumstances.
Open Paradigm – attempts to structure some, so it works in normal environments, but can react better during innovative times.
Synchronous Paradigm – relies on natural compartmentalization and has little communication between members.
Agile Teams
The generic agile team tends to work well, as it encourages competency, and group collaboration. They tend to be self-organizing.
Global Teams
Teams spread out over multiple time zones or even countries will have a harder time communicating and feeling like they are part of a single team/process.
Distance makes for a barrier to communication. But so does language, time zones, etc.
Software Engineering Teams was originally found on Access 2 Learn
