SCRUM is an agile, lightweight process for managing and controlling projects, events, tasks, departments and activities.

1. Scrum

2. 2
What is Scrum?
Definition from rugby football:
a scrum is a way to restart the game after an interruption,
where the forwards of each side come together in a tight
formation and struggle to gain possession of the ball when
it is tossed in among them

3. Five Values of Great Teams!
Accountability

4. JASS 2006 Agile Project Management - Scrum 4
Scrum - an agile process
• SCRUM is an agile, lightweight process for managing and controlling
projects, events, tasks, departments and activities.
– Iterative, incremental process
– Team-based approach
– developing events & activities with rapidly changing requirements
– Controls the chaos of conflicting interest and needs
– Improve communication and maximize cooperation
– Protecting the team form disruptions and impediments
– A way to maximize effectiveness

5. 5
The way Scrum works

6. 30
days
24
hours
To Do
Tasks
Sprint Backlog
Fast projects
Sprint
Daily Scrum
Status
Progress
Solutions
Achieved
Scrum process

8. 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter
Goals
New Goals 2017
Cost reduction
PlanningMediaActivities
Moving into new building
This is a sample
text. Replace it
by your own
text.
This is a sample text. Replace it by your
own text. This is a sample text. Replace
it by your own text. This is a sample
text. Replace it by your own text.
This is a sample text.
Replace it by your own text.
This is a sample text.
Replace it by your own text.
This is a sample
text. Replace it
by your own
text.
This is a sample
text. Replace it
by your own
text.
This is a sample
text. Replace it
by your own
text.
This is a sample text. Replace it
by your own text. This is a
sample text. Replace it by your
own text.
This is a sample text.
Replace it by your own
text. This is a sample
text. Replace it by your
own text.
This is a sample
text. Replace it
by your own
text.
Year planning

9. Scrum Task Board Template
Accomplished Sprint (1 Month) To Do In Progress Done
This is a sample
text. Replace it
with your own
text.
This is a sample
text. Replace it
with your own
text.
This is a sample
text. Replace it
with your own
text.
This is a sample
text. Replace it
with your own
text.
This is a sample
text. Replace it
with your own
text.
This is a sample
text. Replace it
with your own
text.
This is a
sample text.
This is a
sample text.
This is a
sample text.
This is a
sample text.
This is a
sample text.
This is a
sample text.
This is a
sample text.
This is a
sample text.
This is a
sample text.
This is a
sample text.
This is a
sample text.
This is a sample
text. Replace it
with your own.
This is a
sample text.
This is a
sample text.
This is a sample
text. Replace it
with your own
text.
This is a sample
text. Replace it
with your own
text.
This is a sample
text. Replace it
with your own
text.

10. Scrum board

11. Scrum Roles
Scrum Roles
There are three roles in a Scrum project; no less, and no more. We are
not allowed to define any other roles, because it is harmful to the
unity of the team.
A Scrum Team consists of the following three roles:
The term “Scrum Team” refers to all the project team members:
everyone internal to the project.
Scrum Team members usually have only one of the three standard
roles of Scrum:
Project Owner, Scrum Master, or Staff Team member.
It is possible for a single person to be assigned to more than one of the
standard roles, but it is not recommended.
The Scrum Team is a part of the performing organization (which
executes the project either for itself or as an external project).

12. 12
Scrum Master
• Represents management to the project
• Typically filled by the project owner
• Responsible for enacting scrum values and
practices
• Main job is to remove impediments
• Scrum Master can be everybody of the team

13. 13
The Scrum Team
• Typically 5-10 people
• Cross-functional
• Members should be part of the leadership
• Team is self-organizing
• Membership can change only between sprints

14. Project owner Owner
• Acts like one voice (in any case)
• Knows what needs to be done and in what
sequence this should be done
• One of the staff members

15. The Process
• Sprint Planning Meeting
• Sprint
• Daily Scrum
• Sprint Review Meeting

16. 16
Sprint Planning Meeting
• A collaborative meeting in the beginning of
each Sprint between the Project Owner, the
Scrum Master and the Team

17. 17
Sprint Planning Meeting
• 1st Part:
– Determining the Sprint Goal.
– Participants: Project Owner, Scrum Master, Scrum
Team
• 2nd Part:
– Participants: Scrum Master, Scrum Team
– Creating Sprint Backlog

18. 18
Pre-Project/Kickoff Meeting
• A special form of Sprint Planning Meeting
• Meeting before the begin of the Project

19. 19
Sprint
• A month-long iteration, during which is
incremented a product functionality
• NO outside influence can interference with
the Scrum team during the Sprint
• Each Sprint begins with the Daily Scrum
Meeting

20. 20
Daily Scrum
• Is a short (15 minutes long) meeting, which is
held every day before the Team starts working
• Participants: Scrum Master (which is the
chairman), Scrum Team
• “Chickens” and “Pigs”
• Every Team member should answer on 3
questions

21. 21
Questions
• What did you do since the last Scrum?
• What are you doing until the next Scrum?
• What is stopping you getting on with the
work?

22. 22
Daily Scrum
• Is NOT a problem solving session
• Is NOT a way to collect information about
WHO is behind the schedule
• Is a meeting in which team members make
commitments to each other and to the Scrum
Master
• Is a good way for a Scrum Master to track the
progress of the Team

23. 23
Sprint Review Meeting
• Is held at the end month
• Review of the status and results by the team
• Informal, should not distract Team members
of doing their work
• Each member values the status and progress
of the projects the team member is self not
involved.

24. 24
Rating a project

25. 25
Rating a project or department
• 5 levels
• Each month the status of projects is discussed
• The team members give a rating by a symbol

26. 26
Project Backlog
• Requirements for a system, expressed as a prioritized list
of Backlog Items
• Is managed and owned by a project Owner
• Spreadsheet (typically)
• Usually is created during the Sprint Planning Meeting
• Can be changed and re-prioritized before each PM

27. 27
Sprint Backlog
• Is a FORECAST!
• Is a good warning monitor

28. 28
Information Radiator
• "Two characteristics are key to a
good information radiator. The first
is that the information changes
over time. This makes it worth a
person's while to look at the
display... The other characteristic is
that it takes very little energy to
view the display."