Which trio forms the core Scrum team and what is each role primarily responsible for?

Which trio forms the core Scrum team and what is each role primarily responsible for?

• A. The team does not coordinate with the ScrumMaster
• B. The product owner handles implementation
• C. The team does the work, the ScrumMaster helps facilitate, and the product owner defines the direction for the team
• D. The ScrumMaster approves backlog items

Answer: (C)

In Scrum, the core trio that forms the Scrum Team is the group that actually builds the product, the facilitator who keeps the process healthy, and the person responsible for guiding what to build and in what order. The description in the answer matches this shape: the team does the work, the Scrum Master helps facilitate, and the Product Owner defines the direction for the team. Think of it this way: the Developers are the cross-functional group who turn ideas into increments every Sprint. The Product Owner owns the Product Backlog, clarifies requirements, and prioritizes work to maximize value, providing the direction the team follows. The Scrum Master acts as a servant-leader who helps the team adopt and follow Scrum, removes impediments, and shields the team from external distractions, ensuring the process runs smoothly. This arrangement is essential because it keeps clear responsibilities: backlog decisions and value come from the Product Owner, execution comes from the Developers, and process health comes from the Scrum Master. Other options imply means of control or activity that don’t align with Scrum roles—e.g., the Scrum Master approving backlog items or the Product Owner doing the implementation—so they miss the intended balance of accountability and collaboration.

In Scrum, the core trio that forms the Scrum Team is the group that actually builds the product, the facilitator who keeps the process healthy, and the person responsible for guiding what to build and in what order. The description in the answer matches this shape: the team does the work, the Scrum Master helps facilitate, and the Product Owner defines the direction for the team.

Think of it this way: the Developers are the cross-functional group who turn ideas into increments every Sprint. The Product Owner owns the Product Backlog, clarifies requirements, and prioritizes work to maximize value, providing the direction the team follows. The Scrum Master acts as a servant-leader who helps the team adopt and follow Scrum, removes impediments, and shields the team from external distractions, ensuring the process runs smoothly.

This arrangement is essential because it keeps clear responsibilities: backlog decisions and value come from the Product Owner, execution comes from the Developers, and process health comes from the Scrum Master. Other options imply means of control or activity that don’t align with Scrum roles—e.g., the Scrum Master approving backlog items or the Product Owner doing the implementation—so they miss the intended balance of accountability and collaboration.