In 1965, Bruce Tuckerman postulated the 4 stages of group development when building a team. It’s important to understand these stages as a team developer. Each one consists of different behaviors which are driven by the team members’ needs. Understanding these needs and behaviors are essential in guiding the team to success.
These development stages show up repeatedly on an SAP project, not only when it starts but throughout as phases, deliverables and personnel change.
Stage 1: Forming (Getting to Know Each Other)
This is the first stage of forming a team. This is when the team first meets each other and is on their best behavior. As part of a new group, individuals seek acceptance from their new teammates and try to develop bonds through common interests. They are also looking for an individual to take the lead.
During this stage, it is important for leadership to define objectives, roles, and tasks so that members feel their contributions are significant. That way, team members will begin to establish a sense of purpose and commitment to the team. In addition to the onboarding process, team building activities need to be incorporated to help team members form bonds required for team efficiency.
As with all the stages it is important to recognize that forming occurs whenever a new team is created. In a typical NSPRO engagement teams are formed and dissolved throughout the project lifecycle hence the ongoing need to provide leadership and guidance.
Stage 2: Storming (People Start Butting Heads)
Now that the team is past the introductory stage, personalities can start to conflict due to differing opinions and approaches. Team members will begin to question things such as responsibilities, rules, and criteria for success. […]