1. Product Backlog
2. Scrum Events
2.1. The Sprint
2.1.1. No changes are made that would endanger the Sprint Goal
2.1.2. Quality does not decrease
2.1.3. The Product Backlog is refined as needed
2.1.4. Scope may be clarified and renegotiated with the Product Owner as more is learned
2.2. Sprint Planning
2.3. Daily Scrum
2.4. Sprint Review
2.5. Sprint Retrospective
3. Sprint Backlog
4. Scrum Artifacts
4.1. For the Product Backlog it is the Product Goal
4.2. For the Sprint Backlog it is the Sprint Goal
4.3. For the Increment it is the Definition of Done
5. Scrum Team
5.1. Developers
5.1.1. Creating a plan for the Sprint, the Sprint Backlog
5.1.2. Instilling quality by adhering to a Definition of Done
5.1.3. Adapting their plan each day toward the Sprint Goal
5.1.4. Holding each other accountable as professionals
5.2. Product Owner
5.2.1. Developing and explicitly communicating the Product Goal
5.2.2. Creating and clearly communicating Product Backlog items
5.2.3. Ordering Product Backlog items
5.2.4. Ensuring that the Product Backlog is transparent, visible and understood
5.3. Scrum Master
5.3.1. The Scrum Master serves the Scrum Team
5.3.1.1. Coaching the team members in self-management and cross-functionality
5.3.1.2. Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done
5.3.1.3. Causing the removal of impediments to the Scrum Team’s progress
5.3.1.4. Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox
5.3.2. The Scrum Master serves the Product Owner
5.3.2.1. Helping find techniques for effective Product Goal definition and Product Backlog management
5.3.2.2. Helping the Scrum Team understand the need for clear and concise Product Backlog items
5.3.2.3. Helping establish empirical product planning for a complex environment
5.3.2.4. Facilitating stakeholder collaboration as requested or needed
5.3.3. The Scrum Master serves the organization
5.3.3.1. Leading, training, and coaching the organization in its Scrum adoption
5.3.3.2. Planning and advising Scrum implementations within the organization
5.3.3.3. Helping employees and stakeholders understand and enact an empirical approach for complex work
5.3.3.4. Removing barriers between stakeholders and Scrum Teams