Scrum is founded on empirical process control and asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk. At the end of every Sprint, an increment of 'done' work must be available in order to inspect and adapt accordingly.

Scrum addresses complex problems in complex environments and asserts that knowledge comes from experience and making decisions based on what is known. What is known can only be discovered in hindsight.

A Scrum Master is not a management position in the traditional sense of the word. A Scrum Master does not have authority over the team members, the product, or the project. A Scrum Master is a servant leader who helps the team self-organize, collaborate, and deliver value. A Scrum Master is accountable for managing the Scrum process, ensuring that the team follows the Scrum values and principles, and facilitating the team's interactions with stakeholders and the organization. A Scrum Master is also accountable for removing organizational impediments that limit the team's progress and productivity, such as bureaucracy, silos, or conflicts. A Scrum Master is not accountable for reporting on the performance of a team, managing the project plan and the project deliverables, or managing the capacity and utilization of the Developers. These are responsibilities of the Product Owner, the Developers, or other roles in the organization.

Conflicts are a natural occurrence and the Scrum Master coaches the Development Team on the value of resolving conflicts. Leaving conflicts unresolved can impact the Scrum values of openness and respect diminishing trust. Lower trust levels will impact the Scrum Team's effectiveness and can cause impediments in the future. It is the responsibility of the Scrum Master to remove impediments that hinder the team through conflict resolution and facilitation.