There are a number of different models that describe the stages of team development. In my experience, I have been exposed to agile frameworks and waterfall frameworks in the development of applications. I traditional model of team development transcends the framework the team is utilizing to build the application. Traditionally team development has 4 main stages and the differences between the frameworks used are not that significant.
Try to focus on the models of team development they are very basic concepts I have used in the past:
1.Origination.
When team members are assembled in their team for the first time, they experience many different feelings. Some are enthusiastic and optimistic, while others may be more cautious. I have never at this stage seen team members display outright anger or resentment. Sometimes they question the validity of the project, but they are careful because the level of trust and commitment is typically low.
2.Opposition.
The opposition will happen on all projects to a certain degree. Once team members begin to know each other better, team members begin to feel more comfortable, open up and speak their minds. Remember at this stage team members form alliances during the opposition stage and informal work groups begin to appear.
WARNING: The unfortunate aspect of the opposition stage is that due to a high degree of discomfort and conflict, many teams stall out and never move forward. Don’t let this happen to you stay positive and vigilant, keep communication channels open at all times.
3.Inclusion.
Finally, in the inclusion stage, team members finally overcome their difficulties with each other, start to accept each other and accept their roles on the project team. This is when the sharing of information and ideas is common, Commitment and trust increase.
4.High-Speed Performance.
This stage is the ultimate for the project team. Members form a cohesive unit and strengths are used to maximum advantage. It is a natural state that all team members enjoy. Usually, in agile frameworks, I have found that by stage two (opposition) that the team is acting as a cohesive, co-located, communicating agile team.
Caution
Teams can revert back to different stages, sometimes this happens when a new member joins your team or a different ScrumMaster/project manager is appointed, your team may move from the inclusion stage back to the opposition stage because of new team dynamics. Also, don’t let changing circumstances which happen in ALL projects revert your team back to stage one.