Forming Scrum Teams using Tuckman’s Theory
Forming
A very common scenario in the scrum team during this stage is that they are awkward and aloof with each other. Since all roles are brought together in one small team, it is common that the team members observe and figure out on how they can integrate their individual working styles. At this stage, the scrum master plays an important role. It is the scrum master’s responsibility to guide the team in understanding the concept of agile and a cross-functional team. He can start by facilitating a meeting to create a working agreement to help the team identify their initial approach on how they will work together. The scrum master should make himself available to answer any clarifications the team may have, conduct training for familiarization and give feedback and suggestions for improvement.
Storming
Storming is the most challenging stage of developing teams. This is where conflicts usually arise since they are now confident in what they know and start to challenge each other. The common cause of conflicts falls on each team member’s working style and on how this affects the team goal. The scrum master should be more attentive at this stage as this can be both beneficial and destructive. He should be able to bring the team together by bridging their gaps through positive influencing and creative facilitation in meetings. He should be observant of the characteristics of each team member and be able to suggest activities that can help the team reach a common understanding. This stage emphasizes the importance of the scrum master being able to build a good relationship with the team.
Norming
At this point, the team was able to deliver and work together for a number of sprints already. With this, the team was able to develop a productive working relationship with one another. They now have an idea of what works for them and what doesn’t. They are more open to collaborating, experiment with new techniques they can apply and listen to each other’s opinions and suggestions. They can now give constructive feedback and sort out individual differences. The role of the scrum master at this stage revolves around facilitating discussions, encouraging updates on the working agreement, team building and continue helping the team identify and take action on items for improvement.
Performing
This is the peak of the team’s performance. This indicates that the team can self-organize and be cross-functional. At this stage, the team can consistently maintain their velocity and challenge themselves to stretch their usual capacity. There is minimal supervision needed from the scrum master at this point. He can focus on looking at each team member’s development to sharpen their technical contribution to the team.
Adjourning
Like every project, it will come to an end. During this time, to promote the growth of the team or an individual, team members can be assigned to a new project or team. However, in Agile setup, it is recommended to give a well-established team a new project instead of breaking the team. A team can be more agile and deliver more if they have a good working relationship with each other. For a project to succeed, the team should have all the necessary skills needed and be guided properly. This is key to maximizing the benefits of Agile development and reaping its promise of high quality and quick delivery. With the help of the scrum master, the right mindset (self-organization and being cross-functional) and team culture of trust and collaboration should be developed to ensure productivity and efficiency.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course:
Course Contents
Section 1: Agile Project Management
Section 2: Using the Agile Manifesto to Deliver Change
Section 3: The 12 Agile Principles
Section 4: The Agile Fundamentals
Section 5: The Declaration of Interdependence
Section 6: Agile Development Frameworks
Section 7: Introduction to Scrum
Section 8: Scrum Projects
Section 9: Scrum Project Roles
Section 10: Meet the Scrum Team
Section 11: Building the Scrum Team
Section 12: Scrum in Projects, Programs & Portfolios
Section 13: How to Manage an Agile Project
Section 14: Leadership Styles
Section 15: The Agile Project Life-cycle
Section 16: Business Justification with Agile
Section 17: Calculating the Benefits With Agile
Section 18: Quality in Agile
Section 19: Acceptance Criteria and the Prioritised Product Backlog
Section 20: Quality Management in Scrum
Section 21: Change in Scrum
Section 22: Integrating Change in Scrum
Section 23: Managing Change in Scrum
Section 24: Risk in Scrum
Section 25: Risk Assessment Techniques
Section 26: Initiating an Agile Project
Section 27: Forming the Scrum Team
Section 28: Epics and Personas
Section 29: Creating the Prioritised Product Backlog
Section 30: Conduct Release Planning
Section 31: The Project Business Case
Section 32: Planning in Scrum
Section 33: Scrum Boards
Section 34: Sprint Planning
Section 35: User Stories
Section 36: User Stories and Tasks
Section 37: The Sprint Backlog
Section 38: Implementation of Scrum
Section 39: The Daily Scrum
Section 40: The Product Backlog
Section 41: Scrum Charts
Section 42: Review and Retrospective
Section 43: Scrum of Scrums
Section 44: Validating a Sprint
Section 45: Retrospective Sprint
Section 46: Releasing the Product
Section 47: Project Retrospective
Section 48: The Communication Plan
Section 49: Formal Business Sign-off
Section 50: Scaling Scrum
Section 51: Stakeholders
Section 52: Programs and Portfolios