Scrum Team

A single, cross-functional unit in Scrum made up of the Product Owner, Scrum Master, and Developers who collaborate to deliver value each Sprint.

Key Points

  • Includes the Product Owner, Scrum Master, and Developers as one cohesive unit.
  • Self-managing and cross-functional, with shared accountability for delivering value and meeting the Sprint Goal.
  • Creates a usable, Done Increment every Sprint and adapts through Scrum events.
  • Works transparently with no sub-teams or special titles within Developers.

Example

A fintech company forms a Scrum Team with a Product Owner from the business, a Scrum Master, and six developers (frontend, backend, QA, UX). They run 2-week Sprints, plan work together, hold a Daily Scrum, and demonstrate a working payment feature at the Sprint Review.

PMP Example Question

Which group in Scrum combines the Product Owner, Scrum Master, and Developers into a single unit focused on delivering value each Sprint?

  1. Project Management Office (PMO)
  2. Scrum Team
  3. Steering Committee
  4. Release Train

Correct Answer: B — Scrum Team

Explanation: The Scrum Team is the unified group consisting of the Product Owner, Scrum Master, and Developers who collaborate to deliver value each Sprint.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Launch your Agile career!

HK School of Management helps you learn Agile and Scrum with practical playbooks, AI-powered prompts, and real-world workflows for planning and delivery. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More