Scrum has exactly three roles. Not five. Not “senior developers” or “tech leads.” Three. Each role has a clear purpose, specific responsibilities, and distinct accountabilities.
Understanding these roles isn't just academic. When roles blur, teams struggle. When they're clear, teams ship. Here's what each role actually does.
The Three Roles
Product Owner
The Voice of the Customer
Maximizes the value of the product by managing the backlog and ensuring the team builds the right things.
Responsibilities
- •Manage and prioritize the product backlog
- •Define and communicate the product vision
- •Make decisions on features and scope
- •Accept or reject completed work
- •Engage with stakeholders and customers
- •Ensure ROI and business value delivery
Key Skills
- ✓Business acumen and market knowledge
- ✓Strong communication and negotiation
- ✓Decision-making under uncertainty
- ✓Stakeholder management
- ✓User story writing
- ✓Strategic thinking
A Day in the Life
- →Reviewing and refining backlog items
- →Meeting with stakeholders to gather requirements
- →Answering team questions during development
- →Participating in sprint ceremonies
- →Analyzing metrics and user feedback
- →Planning upcoming features and releases
Common Anti-Pattern
Becoming an order-taker who just writes down what stakeholders want without prioritization or vision.
Scrum Master
The Process Guardian
Serves the team by removing impediments, facilitating ceremonies, and coaching everyone on Scrum practices.
Responsibilities
- •Facilitate Scrum ceremonies and events
- •Remove blockers and impediments
- •Coach the team on agile principles
- •Protect the team from distractions
- •Foster continuous improvement
- •Ensure Scrum is understood and enacted
Key Skills
- ✓Facilitation and conflict resolution
- ✓Servant leadership mindset
- ✓Deep knowledge of Scrum framework
- ✓Coaching and mentoring abilities
- ✓Problem-solving and creativity
- ✓Emotional intelligence
A Day in the Life
- →Facilitating the daily standup
- →Unblocking team members
- →Organizing and preparing for ceremonies
- →One-on-ones with team members
- →Working with other departments to resolve issues
- →Tracking and removing organizational impediments
Common Anti-Pattern
Acting as a project manager or task master who controls the team instead of serving them.
Development Team
The Builders
Self-organizing professionals who turn backlog items into working increments of product every sprint.
Responsibilities
- •Deliver a potentially shippable increment each sprint
- •Self-organize to accomplish sprint goals
- •Estimate and commit to work
- •Maintain code quality and technical standards
- •Collaborate daily to solve problems
- •Participate actively in all ceremonies
Key Skills
- ✓Technical expertise in their domain
- ✓Cross-functional collaboration
- ✓Estimation and planning
- ✓Problem-solving and debugging
- ✓Testing and quality assurance
- ✓Continuous learning mindset
A Day in the Life
- →Writing code, tests, and documentation
- →Code reviews and pair programming
- →Participating in daily standups
- →Breaking down user stories into tasks
- →Fixing bugs and refactoring
- →Collaborating with team members on complex problems
Common Anti-Pattern
Working in silos, hoarding knowledge, or waiting to be told what to do instead of self-organizing.
Who Does What: Quick Reference
| Task | PO | SM | Dev |
|---|---|---|---|
| Prioritizes the backlog | ✓ | — | — |
| Removes impediments | — | ✓ | — |
| Writes code | — | — | ✓ |
| Defines acceptance criteria | ✓ | — | — |
| Facilitates ceremonies | — | ✓ | — |
| Estimates story points | — | — | ✓ |
| Makes technical decisions | — | — | ✓ |
| Engages stakeholders | ✓ | — | — |
Common Role Confusions
Myth: Product Owner is the boss
Reality: PO owns the "what" and "why," but the team owns the "how." It's collaboration, not command.
Myth: Scrum Master is a project manager
Reality: Scrum Masters don't manage tasks or timelines. They serve the team and protect the process.
Myth: Developers just code what they're told
Reality: Development teams are self-organizing. They decide how to build and own technical decisions.
Myth: One person can be PO and Scrum Master
Reality: This creates conflicts of interest. The roles have fundamentally different focuses.
Myth: Scrum Master is only needed part-time
Reality: For new or struggling teams, it's a full-time role. Even mature teams benefit from dedicated focus.
How They Work Together
PO + Dev Team
PO defines what and why. Team figures out how and estimates effort. Constant collaboration during backlog refinement and sprint planning.
SM + Dev Team
SM removes blockers and facilitates process. Team focuses on delivery. SM coaches the team to become more self-organizing over time.
SM + PO
SM coaches PO on maximizing value and managing the backlog effectively. PO works with SM to improve stakeholder collaboration.
The Bottom Line
These roles exist for a reason. Product Owner ensures you're building the right thing. Scrum Master ensures you're building it the right way. Development Team ensures you actually build it.
When roles are clear, teams move fast. When they're blurred, you get politics, delays, and confusion. Respect the roles. Trust the framework.
Plan like a pro
Product Owners, Scrum Masters, and Dev Teams all use our free planning poker tool to estimate stories and build consensus.
Start Estimation Session