Do you know what pigs and chickens have in common with Scrum roles?

Take this short quiz to know more about Scrum roles and farm animals.
Start the Quiz

How many roles do we have in Scrum?

« back

There are three roles!

Yeah, only 3 roles, we are not free to create new roles.

The roles in Scrum are quite different from the traditional software methods. Clearly defined roles and expectations help individuals perform their tasks more efficiently.

next >>

What are Scrum roles?

« back

Product Owner, Development Team, and Scrum Master!

Scrum Team

Together they are known as the Scrum Team, which is the fundamental Scrum unit

Up to 10 people
The Scrum Team should be up to 10 people, it helps with communication and management.
Creating a valuable and useful increment
The Scrum Team is responsible for creating a valuable and useful increment in each sprint, therefore this team is responsible for all activities related to the product (collaboration with stakeholders, maintenance, research, development, etc).
Self-managed
The Scrum Team is self-managed, which means that the team decides who does what, when, and how.
Click 'next' to know more about the roles and responsibilities.
next >>

Product Owner

It's a person
It’s a person (yes, only one person!), who is totally oriented by the business, not a Tech Lead.
Most business value for the product

They are responsible for achieving the most business value for the product

Customers' needs
They are also responsible for the customers’ needs.
Scrum Team delivering value
Product Owner is responsible for the Scrum Team delivering value.
Priority changes
No one besides the Product Owner is allowed to talk to the Development Team about priority changes.
Product backlog
Responsible for the product backlog.
Product goals
Responsible for creating and communicating the product goals.
Backlog items
Responsible for creating and communicating clearly the backlog items.
Organize product backlog
Responsible for organizing and prioritizing the backlog items.
Everyone should respect their decisions
The entire organization should respect the Product Owner's decisions, no one, not even the CEO, should nullify their decisions.
Product backlog still their responsibility
The Product Owner can delegate some activities, for example, ask a developer to create a backlog item, but it is still their responsibility.
Click 'next' to know more about the other roles
next >>

Scrum Master

It's a person
It’s a person (again, only one person!). They are a master in Scrum practice, also not a Tech Lead.
Scrum practice

The Scrum Master guides, facilitates, and teaches all Scrum practices to everyone involved in the process. They remove impediments and ensure that scrum components are followed by everyone.

Servant Leader
The Scrum Master is a facilitator and Servant Leader who encourages and demands self-organization from the Development Team.
Team protection
A Scrum Master protects the team from external and internal distractions.
Remove impediments
A Scrum Master removes impediments so the team can focus on the work at hand and follow Scrum practices.
Influential leader
A Scrum Master is not typically a manager or lead, but he is an influential leader and coach who does not do direct command and control.
Click 'next' to know better the last role
next >>

Development Team

It's a group of people

It’s a group of people who are committed to creating useful and valuable increments in each interaction.

They work in the sprint backlog.

Have enough knowledge
They should have enough knowledge to deliver all items from the sprint backlog.
Self-organized
They are self-organized, which means they don’t need to receive someone else’s commands. In other words, no one should specify what each person will do in the sprint, they are free to organize and pick tasks from the sprint backlog.
Know all product goals
They should know all product goals.
There is no individual work

Although a task is handled by a single developer, everyone is responsible for the task, there is no individual work, everyone collaborates on the project.

Avoid changes

The team composition should not be changed frequently, if it's necessary to change it, it should be done after the sprint is concluded. (note. all team changes impact directly on the team performance)

It's not only developers
The name “Development Team” doesn't mean that is composed only of software developers, everyone who works to develop the product is part of the Development Team (ex: QA, Product Designer, etc)
Sprint backlog
They work in the sprint backlog.

We are almost done...

Do you remember our main question about farm animals and Scrum roles?
Click on 'next' to continue our journey
next >>

You are one click away...

Now that we know everything about Scrum roles, you are one click away from knowing what pigs and chickens have in common with Scrum roles.
« back