News — Scrum

1. Read The Scrum Guide
2. Study until you can describe the tasks and functions of the:
1. Scrum Master role
2. Product Owner role
3. Developer role
3. Study until you can describe the usage and standards for the:
1. Sprint Backlog
2. Product Backlog
3. Product Increment
4. Study until you can explain the length and purpose of
1. A Sprint
2. The Daily Scrum
3. Sprint Planning
4. Sprint Retrospective
5. Sprint Review
5. Work on a Scrum Team for at least a year to gain experience
6. Learn how to lead small teams by
1. Reading at least 20 leadership books
2. Get to know five people you consider influential leaders
3. Learn to listen to your teammates
4. Gain the respect of your team through problem-solving

Rationale for Scrum Teams: to improve the speed, quality, and value of work in order to make work fun and fast.

As a true leader the scrum master serves their team in 5 key ways.

1. Keeping the team on task 
2. Keeping the team on time
3. Keeping the team focused on their goal
4. Resolving problems before they hurt productivity
5. Protects the team from distractions

Quality is the responsibility of everyone on a Scrum team. The developers need to produce high quality work for every product backlog item.

The Scrum Master must ensure the team understands and complies with the acceptance criteria and definition of done.

The Product Owner must ensure the customer is pleased with the product and it meets the product owner's vision before releasing the product.

As you can see, this issue is a bit more complicated than just saying, "the product owner is responsible for quality".

While everyone on the team is responsible for quality, they are responsible in different ways.

The rationale for scrum teams implementing short sprints is to get more feedback and limit schedule risk.

Shorter sprints mean your teams get Sprint Reviews more often, which, is valuable because Sprint Reviews are when customers give you feedback on your product.