Scrum Team

Scrum Team = Scrum Master, Product Owner, and Developers who work towards a Product goal. It is cross-functional and self-managing.
Read more

Scrum Team

Scrum Team consists of Scrum Master, one Product Owner, and Developers who work towards a Product goal. It is cross-functional, self-managing, and usually fewer than 10 people. Each sprint the team creates a valuable and usable product increment.

Scrum Master

Establishing Scrum according to the Scrum Guide. They are leaders, enablers who serve the Scrum Team, Product Owner, and the organization by coaching in Scrum adoption, removing impediments, and facilitating activities.

Product Owner

The main accountability is maximizing the value of the product according to the Product Goal. The Product Owner is one person representing the stakeholder’s needs, adjusting the Product Backlog accordingly. His Product Backlog decisions are respected by all.


The creators of a usable Increment based on the Sprint Backlog. They are responsible for the Sprint plan, its creation, adaptation, and execution to meet the Sprint Goal and the Definition of Done.

Scrum framework overview

Similar posters

RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.