Scrum is a way to organize your work teams to accomplish more and keep morale high.
If you'd like to be able to explain Scrum in easy to understand language, keep reading this tutorial.
Level up your agile and get professional training.
Key Scrum Resource
You can't really understand Scrum until you're ready The Scrum Guide so please head over to there first.
In a nutshell
Scrum is a way to organize the people, plans, and products of your teams to produce the most value in the lowest amount of time.
This is accomplished by having three roles on your teams
- Scrum Master
- Product Owner
These three roles describe how people serve there teams.
Scrum Master Role
The scrum master is the leader who servers their team. They are responsible for removing impediments and speeding up their team's cadence meaning that the team accomplishes more and more during a given week as time goes on.
The scrum master also coaches the members of the team to use Scrum more effectively.
The Product Owner Role
The product owner organizes and prioritizes the team's work in a backlog. The backlog is a to-do list that is both prioritized and available to the entire team. The team should only operate off of one backlog.
The product owner is responsible for the value the team creates.
The Developer Role
The developers are the ones who produce the work of the team. They are responsible for the quality of the work and for work completion. The Scrum Master and Product Owner serve the developers in such a way that the developers create the right thing, with high quality, and on time.
The result of this supportive, agile relationship is high value, low cost products made by happy teams.
This is done on a day-to-day basis with the Scrum Events.
Scrum Event 1, Daily Scrum
The Daily Scrum is the event where the team meets to discuss what they accomplished yesterday and what they plan to accomplish today in support of the team goal. This allows the team to effectively work together while avoiding duplication of effort or wasted work.
Scrum Event 2, Sprint Planning
Spring Planning is where the team gathers and determines what work they will accomplish int the sprint. This should be fast and easy since the product owner should have the potential work well defined and prioritized before spring planning starts.
Scrum Event 3, Sprint Review
The Sprint Review is where the team shows and demonstrates their product to their customers and stakeholders. This allows the customers and stakeholders to provide incremental feedback to support incremental development. It should be frank and specific feedback and the team should use that feedback to adjust their plans.
Scrum Event 4, Sprint Retrospective
The Sprint Retrospective allows the team to discuss how to make their team better. This can be done a variety of ways, but my favorite way is by measuring everyone's happiness and choosing one thing that the team could do to improve a team member's happiness.
Scrum Event 5, Sprint
The Sprint is the 5th and final event of the Scrum Framework. It's the wrapper in which everything occurs. Nothing should occur outside the Sprint. Sprints remain the same duration for the life of a team.
How to become a Scrum Master
It can be hard to get your first Scrum Master position, but it's almost impossible to do unless you're a professionally credential holding Scrum Master. If you are still waiting for your chance to get your Scrum Master credential may we suggest the cheapest Scrum Master credential?
In this tutorial you learned what the Scrum Framework is. This included
- The roles of Scrum
- Scrum Master
- Product Owner
- The events of Scrum
- Daily Standup
- Sprint Planning
- Sprint Review
- Sprint Retrospective
- The Sprint
- The artifacts of Scrum
- Sprint Backlog
- Product Increment