
Scrum Project Roles – Part 3
Tuckman’s Theory
For most team members, this process begins as the team forms. The formation stage happens when a team assembles for a specific purpose or project. This can include members who have previous experience together and are adding new members, or a group of people who have never worked together before. In the beginning, there may be some disagreements between team members. Inevitably, team members will work through the disagreements to achieve their mutual goal. As time passes, overcoming these differences results in better cohesion between members. This improved cohesion yields better performance from the team.
Developers often experience the stages of Tuckman’s Theory in some specific ways. Soon after the team forms, developers may be criticized for taking too long on tasks, producing code with errors, or failing to fix problems. Many of these problems are less on the individual developer and more on their interaction with other developers and other roles on the team. As developers learn each other’s styles, they can work more effectively together on the same code. They also begin to think more like the testers and analysts on the team. This yields better communication, and fewer problems between roles. As developers learn their team, they work more effectively. Teams that have consistently worked together begin to outperform new teams that first come together.
The self-organizing teams of Scrum often work more efficiently than mandated teams, but this practice is not without issues. Each role must be able to work with the other roles, developers included. There are often hurdles that new teams must overcome. As the same team members work together, however, Tuckman’s Theory suggests that they become more efficient and cohesive to better handle new features and requests.
59 Seconds Training Video
Master of Agile – Agile Scrum Tester With 59 Seconds Agile (Video Training Course)
Introductory Offer: Free Course
Master of Agile – Agile Scrum Tester With 59 Seconds Agile (Video Training Course)
What is this course?
This ‘Master of Agile – Agile Scrum Tester With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Tester roles and responsibilities
You will explore the Agile Scrum project life-cycle, including how an Agile User Story is created, to how we know when it is ‘done’
This course is aimed at those with or without prior knowledge and experience of the Agile values and principles
During this course you will learn the tools needed to succeed as an Agile Scrum Tester
What will you learn?
You will gain an in-depth understanding of the Agile Scrum Tester roles and responsibilities, and you will be able to
- Fully understand the role of the Agile Scrum Tester
- Understand the roles involved in an Agile project
- Create an effective Product Backlog
- Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
- Identify the roles involves in the Scrum Team
- Fully understand the role of the Agile Scrum Developer
- Understand the roles involved in an Agile project
- Create an effective Product Backlog
- Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
- Identify the roles involves in the Scrum Team

What topics are covered within this course
You will cover the following topics during this course:
- An Introduction to Agile Project Management (Tester)
- The 12 Agile Principles (Tester)
- Introduction to Scrum (Tester)
- Scrum Projects (Tester)
- Scrum Project Roles (Tester)
- Quality in Agile (Tester)
- Acceptance Criteria and the Prioritised Product Backlog (Tester)
- Quality Management in Scrum (Tester)
- Epics and Personas (Tester)
- Planning in Scrum (Tester)
- Scrum Boards (Tester)
- User Stories (Tester)
- The Daily Scrum (Tester)
- The Product Backlog (Tester)
- Review and Retrospective (Tester)
- Validating a Sprint (Tester)
Our Book Recommendations
We found these books great for finding out more information on Agile Scrum: