Intro SWE Chapter 5 (B) Part Two
Scrum definintion
Scrum is an agile development methodology used in the development of Software based on an iterative and
incremental processes.
Scrum is a management framework that teams use to self-organize and work towards a common goal.
Why is it called Scrum?
It is inspired by a scrum in the sport of rugby.
In rugby, the team comes together in what they call a scrum to work together to move the ball forward.
In this context, Scrum is where the team comes together to move the product forward.
They used the term to describe all members of a team working closely together to incrementally move a project
forward.
18
Scrum - Scrum Roles
Product Owner
Scrum master
Scrum Team
Scrum Product Owner
The product owner represents the customer’s best interest. The Product Owner focuses on ensuring the
development team delivers the most value to the business. They understand and prioritize the changing needs of
end users and customers.
Scrum master
This person is a facilitator, responsible for arranging the daily meetings, improving team interactions, and
maximizing productivity. The Scrum Master oversees keeping Scrum up to date, providing coaching,
mentoring and training to the teams in case it needs it.
Scrum Team
They are a group of professionals with the necessary technical knowledge who develop the project.
Scrum - Scrum Artifacts definition
Artifacts defined by Scrum are specifically designed to maximize transparency of key information so that
everybody has the same understanding of the artifact.
Scrum - Scrum Artifacts list
1. Product Backlog
2. Sprint Backlog
3. Burn-Down Chart
4. Increment
1. Product Backlog
An ordered list of all the remaining requirements or user stories for a product.
2. Sprint Backlog
It is the list of tasks that need to be done for the current sprint.
3. Burndown chart
A frequently updated publicly displayed chart showing the remaining log in the current sprint backlog.
4. Increment
The sum of all requirements implemented in this sprint and all previous sprints.
Scrum Events definition
Scrum Process Framework can be viewed by means of a sequence of events and the corresponding artifacts.
The Scrum events are time-boxed events. That means, in a project, every scrum event has a predefined
maximum duration. These events enable transparency on the project progress to all who are involved in the
project.
Scrum Events List
❑ Sprint Planning
❑ Daily Scrum Meetings
❑ The Sprint Review
❑ The Sprint Retrospective
Sprint
A sprint (also called an iteration) is the basic unit of development in Scrum. The sprint is a time-
boxed effort; that is, it is restricted to a specific duration. The duration is fixed in advance for each sprint and is
normally between one week and one month, with two weeks being the most common. A new Sprint starts
immediately after the conclusion of the previous Sprint.
Sprint Planning
The work to be performed in the Sprint is planned in the Sprint Planning Meeting. During sprint planning, the
product owner and the team decide on what will be implemented during that sprint.
Daily Scrum
The development team meets for 15 minutes (or less) every day of the sprint to inspect progress toward the
sprint goal. They describe for each other how their own work is going, ask for help when needed, and consider
whether they are still on track to meet the sprint goal. This is a short meeting in which team members synchronize,
make sure they are on-track, and ask for help if needed.
Sprint Review
The Sprint Review takes place after a Sprint ends. The Sprint Team meets with stakeholders to show what they
have accomplished and get feedback. During Review, the Product Owner explains what planned work either was
or was not completed during the Sprint. The team then presents completed work and talks through what went
well and how problems were solved.
Sprint Retrospective
The final event in the Sprint is the Sprint Retrospective. This is when the Scrum Team reviews what could be
improved for future Sprints and how they should do it The Sprint Retrospective is held after the sprint review at the
end of each sprint. It offers the team an opportunity to inspect itself and create a plan for improvements to
be enacted during the next Sprint.