Execution and Delivery

Individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; responding to change over following a plan. The items on the right still have value.

In February 2001, by 17 software practitioners meeting in Snowbird, Utah.

Working software, delivered frequently, rather than documents or percent-complete plans.

Product Owner, Scrum Master, and Developers, forming one team with no sub-teams or hierarchies.

The Scrum Team's effectiveness: coaching the team and organization in Scrum, removing impediments, and ensuring events happen and are productive. The Scrum Master is not a project manager or team boss.

Creating a plan for the Sprint (the Sprint Backlog), instilling quality by adhering to the Definition of Done, adapting their plan daily toward the Sprint Goal, and holding each other accountable.