The multitude of Agile methodologies, frameworks, and practices such as Kanban, Scrum, Extreme Programming, SAFe, and others, all share a core element – the team. Consider the team as a jigsaw puzzle, where each piece is unique, yet when assembled, they form a complete and ideal picture. Similarly, team members are diverse and possess cross-functional skills, making them collectively the perfect fit for a project's requirements.
Let’s see how a team is formed, how the team can progress properly, and what happens after the project is finished, in the article below.
Within Scrum, the team consists of the Scrum Master, the Product Owner, and the Development Team, with an ideal size ranging from 3 to 10 individuals. From the moment the team is formed until its dissolution, it will continuously progress and reshape itself, ultimately achieving a high level of performance and self-sufficiency. The following famous team development model and see how it creates the basis of Agile methodologies.
One of the most famous team development models was introduced in 1965 by Bruce Wayne Tuckman. Tuckman initially identified four distinct phases that every team typically experiences as it matures: Forming, Storming, Norming, and Performing.
The forming stage of the team development cycle marks a pivotal beginning. It is the moment when the team members converge, bringing their unique skills and perspectives to create what is known as a cross-functional team.
This phase is characterized by excitement, exploration, and low conflicts since team members are just getting to know each other and they seek to understand how their contributions will fit into the larger picture. They must identify their shared objectives and develop plans on how to accomplish these goals.
The Scrum Master plays a very important role during the early stages of team development since the team should get to the performing stage as soon as possible. In the Forming phase particularly, the Scrum Master establishes the processes, ensures that the roles and responsibilities are clearly understood, and facilitates the mutual knowledge of the team members and the building of relationships.
In the forming stage, several tools and concepts are particularly useful in helping the team establish a strong foundation for their work ahead.
During this stage, tensions among team members begin to appear. Conflicts, competition, and the need for structure characterize the Storming phase.
The Scrum Master intervenes to settle these conflicts and helps to solve the problems. It encourages open communication, and constructive feedback within the team, all while steering the group toward their shared objective.
The Storming phase, while challenging, is a necessary step for the team to work through differences and establish a more effective way of collaborating.
Some of the tools that help the team navigate through challenges are:
While the Storming phase is often marked by conflict, in Norming, the team reaches a state of stability, with bonds between members becoming more solidified. Team members begin to appreciate each other's strengths and weaknesses, and learn how to work together efficiently, fostering a positive and supportive environment.
The Scrum Master persists in providing support, removing impediments, guiding the team to operate more independently, and encouraging team members to take ownership of their roles and responsibilities.
This Norming phase is characterized by clarity, establishing of norms, and acceptance.
At this phase, the team achieves high performance and effectiveness. With autonomy at its core, the team's members have a deep understanding of each other's capabilities and limitations and seamlessly integrate their skills to meet team objectives collectively.
As the team functions at its optimal level, the Scrum Master's role shifts more towards maintaining the environment that allows for this high performance, rather than direct facilitation.
Any change within the team, whether it involves ramping up or ramping down, impacts its developmental trajectory, and no matter the team's current phase, the process reverts to the initial stage of forming.
Later, in 1977, Tuckman added a fifth stage, namely:
The Adjourning stage, also known as the mourning phase, is characterized by the deconstruction of the team. After achieving their project goals, team members prepare to move on to new assignments or projects.
This final stage is often accompanied by reflection on the team's achievements and the experiences shared. It can be an emotional period as team members say goodbye, but it also offers an opportunity for celebration and closure.
The Scrum Master can facilitate this transition by:
A team’s journey from its inception to its closure is dynamic and transformative, and the Scrum Master plays an essential role in guiding the team, from establishing foundational processes and facilitating conflict resolution to fostering stability and encouraging high performance.
This life cycle of a team is not just a series of steps but expresses the power of collaboration, continuous improvement, and the essence of Agile principles.
At eSolutions, we pay a lot of attention to the team formation process for each project as we consider that the correct composition of the team is essential to ensure the success of the projects.
Once the team has been established, the next step for the projects I manage is to prepare the project charter.
The project charter serves as a comprehensive overview for all individuals involved in the project, providing a bird's-eye view of its entirety. It adheres to a structured format and includes several essential elements:
This document lays the groundwork for the project kickoff meeting, an important event that marks the beginning of the project's journey during the forming phase. The project charter aligns stakeholders with essential details including the project's purpose, vision, objectives, roles, duties, schedule, budget, and other relevant information.
Open communication is a critical element that we emphasize from the initial stages of team formation, with particular focus as we transition into the storming phase. Our commitment to maintaining a constant dialogue with our clients is facilitated through a variety of communication platforms, including Rocket Chat, Slack, Zoom, Microsoft Teams, and Google Meet. Each team selects the communication method that best fits the project's requirements, ensuring that our collaborative efforts are tailored to meet the unique needs of the project.
Last but not least the most valuable ceremony that fosters team evolution throughout the project is the retrospective. Through this ritual, the team has the opportunity to explore strategies for refining processes, enhancing communication, and elevating the quality of the deliverables.
Our retrospectives are equally entertaining and valuable. I use fresh and creative techniques all the time to keep the audience engaged, and if I run out of ideas, the facilitator's role can always be passed to a team member. This sparks a burst of creativity and fresh perspectives.
We encourage an atmosphere where ideas can be openly shared and every voice is heard. By doing so, we not only build teams that are well-equipped to tackle the challenges of any project but also foster a workplace culture that values collaboration, respect, and continuous learning.
We can help you achieve the same in your organization through our Agile offerings.
Madalina Grigoras has been coordinating software development projects from various industries, such as retail, healthcare, and automotive, using Agile Project Management methodologies, for 7+ years. She currently holds the position of Project Manager/Agile Consultant at eSolutions and boasts several certifications, such as: ITIL Foundation Certification, Scrum Fundamentals Certification (SFC), AI & Agility: A Comprehensive Introduction Certification.
Get a detailed snapshot of your organisation.
By choosing eSolutions Agile Work Assessment, you can check the Agile maturity of your teams, identify potential growth areas, refine processes, and boost agility.
RO
EN
