A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible

The three pillars of Scrum are:

  • Transparency
  • Inspection
  • Adaptation

The five values of Scrum are:

  • Courage
  • Commitment
  • Focus
  • Openness
  • Respect

Blending methods

Mixing several agile frameworks.


SCRUM is a self organizing team

The Scrum Master

One key responsibility of the Scrum Master is to help the team understand and follow Scrum theory. More specifically, according to the Scrum Guide, "The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the Organization. The Scrum Master is accountable for the Scrum Team's effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework." The Scrum Master makes sure that important meetings occur, like the Daily Scrum. In the same way that a coach would be aware of the game clock, the Scrum Master is tasked with making sure that the meeting is kept within the appropriate timebox. A timebox is a Scrum concept that refers to the estimated duration for an event.

The Scrum Master acts as a coach to the Scrum Team—they encourage the team to build the product in the time frame. They also support the team by creating a collaborative environment so the project's goals are achieved. The Scrum Master's duties include:

  • Coaching the team members in self-management and cross-functionality
  • Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done (an agreed upon set of items that must be completed before a project or user story can be considered complete)
  • Causing the removal of impediments to the Scrum Team's progress
  • Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox (a Scrum concept that refers to the estimated duration for an event)

Scrum Master vs. project manager

The role of the Scrum Master is sometimes confused with the role of the project manager. While the two roles share related skills and qualities, they are very different roles.

A Scrum Master is responsible for helping the team understand Scrum theory and practice. They ensure Scrum events take place and help the team focus on delivering value by removing impediments. But unlike a traditional project manager, they do not take on the management of changes in scope or priorities. Additionally, Scrum Masters do not maintain traditional project artifacts like Gantt charts.

The Product Owner

Youtube: Agile Product Ownership in a Nutshell

According to the Scrum Guide, "The Product Owner is responsible for maximizing the value of the product resulting from work of the Scrum Team. How this is done may vary widely across organizations, Scrum Teams, and individuals." Product Owners maximize the value of the product by representing and expressing the voice of the customer throughout the project duration. A product isn't useful to its customers if that product doesn't fulfill their expectations and meet their needs. The Product Owner's duties include:

  • Developing and explicitly communicating the Product Goal
  • Creating and clearly communicating Product Backlog items (The Product Backlog contains all of the features, requirements, and activities associated with deliverables to achieve the goal of the project.)
  • Ensuring that the Product Backlog is transparent, visible, and understood

Product Owner vs. project manager

In traditional project management, scope management is the primary responsibility of the project manager. But in Scrum, the definition and management of product scope falls to the Product Owner. Conversely, the Product Owner isn't responsible for team performance—they aren't considered to be a manager. The project manager leads the project team to meet the project's objectives and oversees tasks and progress.

There are also similarities between the Product Owner and project manager roles. For instance, both roles are tasked with stakeholder management. This means they both must practice and facilitate effective communication among team members and stakeholders.

Additionally, in many companies—including Google—the definition of product or solution scope is the responsibility of a separate role called a product manager. So, it is important when joining any new company to discover how that company approaches the area of product definition, requirements development, and user research to understand what they consider to be the domain of the project manager.

Barry Overeem's

Characteristics of a Great Scrum Team