The Scrum Team :
- Scrum Team delivers Products in two ways to maximize opportunities for feedback :
- The Scrum Team Model is built to optimize
- Adding new resources to the Team will lead to a temporary reduction in productivity because new member needs time to be familiar with team’s environment, culture and the product and old members need to collaborate on new member’s onboarding. Furthermore, a bigger Team does not mean that it can create more value. It is recommended to change Team composition at the beginning of the Sprints.
- When a person works in two or more teams, (s)he will pay the context-switching cost. It means (s)he should pay warmup and preparation time and resource for each switch. Therefore, she will be less productive rather than when (s)he just focuses on one piece of work.
- In a Scrum Team, all members collaborate continuously. Therefore, anytime if the Development Team needs feedback from the Product Owner, can ask him/her. From another side, anytime the Product Owner asks to see the work, Development Team would show the work. In addition, according to the Scrum definition, Development Team demonstrates done work to the Product Owner, Scrum Master, and stakeholders in the Sprint Review meeting.
Scrum Team composition :
- Self-organizing team consisting of the Product Owner, Development Team, and Scrum Master.
- 1. Product Owner
- 2. Development Team
- 3. Scrum Master
- The Scrum Team consists only of the following roles. No other roles, no Project Managers or Functional Managers exist within the Scrum Team.
- According to the Scrum rules, there are just three roles in a Scrum Team as the Scrum Master, the Product Owner, and the Development Team and nothing else. The project manager’s duties are distributed among three pre-defined Scrum roles.
- All team members could be part-time or full-time but dedicated members are recommended for the Development Team members. On the other hand, these are the roles not assigned people. It means one member could have two roles at the same time for example as a Product Owner and a Development Team member.
Scrum Team Values :
- Scrum is based upon five core values: Commitment, Focus, Openness, Respect, Courage.
High-performance Scrum Team :
- A high-performance Scrum Team lives the Scrum Values deeply. Mistakes are mandatory and when they are made, they are celebrated. There are many constructive conflicts based on trust in the Team. Instead of living by the rules, they make the rules. They help their customers become more successful. The team can release the Increment with just one press of a button through an automated continuous delivery pipeline. They evolve DoD (Definition of Done) over time and add more stringent criteria to it continuously and adhere to it completely. Almost every Sprint, the team reaches the Sprint Goal and sometimes they exceed expectations. You can obviously see a high level of creativity, productivity, and accountability in the Team. Members are highly knowledgeable, autonomous, and self-organizing and use continuous improvement in all aspects of their processes and environment.
- On the other hand, if a team accepts other top managers’ work, they interrupt their focus and they do not know if they are creating a valuable output for the customer or not. The sole source of the Development Team’s work is the Product Backlog and its owner is the Product Owner. Therefore, they should refer the top managers to the Product Owner.
- There is no assigned Role (e.g. QA) who conducts the Test Cases. Members of the Development Team are responsible for writing and executing the Test Cases.
- Stakeholder is a person external to the Scrum Team with a specific interest in and knowledge of a Product that is required for incremental discovery.
More informations for the Scrum PSD certification here.