What is Scrum? How to implement Scrum? - This presentation describes the basic elements of the Scrum Framework. - My goal is to provide an organized view that will help a novice understand and implement the Scrum foundation quickly.

1. Management Fundamentals:
Scrum 101
Project Management Consulting
Yossi Barezer
Aug 2016

2. Introduction
• This presentation describes the basic elements of
the Scrum Framework
• My goal is to provide an organized view that will
help a novice understand and implement the
Scrum foundation quickly
• For enhanced details, you should read the Guide,
receive official training and consult a coach
• How would I describe Scrum?
– The Scrum methodology provides a way to
continuously, consistently, and constantly improve
product value using reality checks

3. AGENDA Certifications
 Definition of Scrum
 Scrum Theory
 The Scrum Framework
 The 3 Pillars/Principles
 The Scrum Team
 The Scrum Team and Event
 Scrum Artifacts
 Product Backlog
 Sprint Planning and Backlog
 The Scrum Process - Increment
 Scrum Event/Ceremony
 Events Goals and Deliverables
 The Sprint Framework
 Time Box
 Sprint Planning
 Daily Scrum
 Scrum Board
 Burn-Down Chart
 Sprint Review
 Sprint Retrospective
 Definition of “Done”
 Scrum Summary

4. Scrum.org Certification
• PSM I, II - Professional Scrum Master Level I&II
(CSM Equivalent)
• PSPO I, II - Professional Scrum Product Owner
Level I&II (CSPO Equivalent)
• PSD I - Professional Scrum Developer Level I (CSD
Equivalent)
• SPS - Scaled Professional Scrum (Scrum of Scrum)
• PSP - Professional Scrum Practitioner
• PSF - Professional Scrum Foundations
• PSE - Professional Scrum Expert
• PST - Professional Scrum Trainer

5. Definition of Scrum
• “Scrum (n): A framework within which people can address complex
adaptive problems, while productively and creatively delivering
products of the highest possible value. “
• “Scrum is a process framework that has been used to manage complex
product development.”
• “The rules of Scrum bind together the events, roles, and artifacts”
• Scrum-Guides
• Scrum-Glossary
• PSD-Glossary

6. Scrum Theory
“Scrum is founded on empirical process control theory, or empiricism”
• The 3 Pillars/Principles
– Three pillars uphold every implementation of empirical process control:
• Transparency
• Inspection
• Adaptation
• The Scrum Team /Roles
– The Scrum Team consists of a:
• Product Owner
• The Development Team
• Scrum Master
– Scrum Teams are self-organizing and cross-functional
• Scrum Artifacts
– Scrum artifacts represent the work or value to provide transparency and opportunities for
inspection and adaptation
• Product Backlog
• Sprint Backlog
• Increment
• Scrum Events
– Scrum prescribes five formal events for inspection and adaptation, as described in the Scrum Events
section of this document:
• The Sprint
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective

7. The Principles/Pillars
The Scrum Framework
Roles/Team
• Product Owner
• Scrum Master
• Developer
Artifact
• Product Backlog
• Sprint Backlog
• Sprint Increment
• Burn-Down/Up Chart
Events/Ceremonies
• The Sprint
• Sprint Planning Meeting
• Daily Meeting
• The Sprint Review
• Sprint Retrospective
• Product Refining
•Transparency • Inspection • Adaptation
DONE

8. Transparency
Inspection
Adaptation Transparency
Inspection
Adaptation Transparency
Inspection
Adaptation Transparency
Inspection
Adaptation
The 3 Pillars/Principles

9. The 3 Pillars/Principles
• Transparency
– “Significant aspects of the process must be visible to
those responsible for the outcome”
• Inspection
– “Scrum users must frequently inspect Scrum artifacts and
progress toward a Sprint Goal to detect undesirable
variances”
• Adaptation
– “If an inspector determines that one or more aspects of a
process deviate outside acceptable limits, and that the
resulting product will be unacceptable, the process or the
material being processed must be adjusted”

10. The 3 Pillars/Principles
Transparency Inspected Adapted Artifact
The Sprint Product Backlog Product Backlog Yes
Sprint Planning Product Backlog Sprint Backlog Yes
Daily Meeting Sprint Review Sprint Backlog Yes
Sprint Review Sprint Increment Product Backlog Yes
Sprint Retrospective
The Team &
Process
The Team &
Process
No
Product Refining Product Backlog
Product Backlog
& Sprint Backlog
Yes
1 Sprint Backlog Sub-task Sprint Backlog Sprint Backlog Yes

11. The Scrum Team
The
Scrum
Team
Scrum
Master

12. The Scrum Team
• The Product Owner
– “The Product Owner is responsible for maximizing the value of the
product and the work of the Development Team”
– “The Product Owner is the sole person responsible for managing the
Product Backlog. Product Backlog management includes”
• The Development Team
– “The Development Team consists of professionals who do the work
of delivering a potentially releasable Increment of “Done” product
at the end of each Sprint”
– “Only members of the Development Team create the Increment”
• The Scrum Master
– “The Scrum Master is responsible for ensuring Scrum is understood
and enacted”
– “Scrum Masters do this by ensuring that the Scrum Team adheres to
Scrum theory, practices, and rules”

13. The Scrum Team and Events
Event
Event
Owner
Product
Owner
Scrum
Master
Developer Other
Sprint Planning
Part I
Product
Owner
Y Y Y N
Sprint Planning
Part II
Dev Optional Y Y N
Daily Meeting Dev N Optional Y N
Sprint Review
Product
Owner
Y Y Y Y
Sprint
Retrospective
Scrum
Master
Y Y Y N
Product Refining
Product
Owner
Y Y Y N
1 Sprint Backlog
Sub-task
Dev N Optional Y N

14. Scrum Artifacts
Product
Backlog
Sprint
Backlog
Increment

15. Scrum Artifacts
• Product Backlog
– “The Product Backlog is an ordered list of everything that might be needed
in the product and is the single source of requirements for any changes to
be made to the product”
– “The Product Owner is responsible for the Product Backlog, including its
content, availability, and ordering”
• Sprint Backlog
– “The Sprint Backlog is the set of Product Backlog items selected for the
Sprint, plus a plan for delivering the product Increment and realizing the
Sprint Goal”
– “The Sprint Backlog is a forecast by the Development Team about what
functionality will be in the next Increment and the work needed to deliver
that functionality into a “Done” Increment”
• Increment
– “The Increment is the sum of all the Product Backlog items completed
during a Sprint and the value of the increments of all previous Sprints.”

16. Product Backlog
The product attributes are:
- Description: will answer the question “What should I do?”
(detailed enough to understand)
- Order: The Product Backlog is ordered by the Product Owner
- Estimate workload effort: Small, Medium, Large, Extra Large
- Value: to marketplace
scrumreferencecard.com

17. Sprint Planning and Backlog
The Development Team selects items to develop.
This will be the Product Increment.
Each selected Item will have the following details:
- Description: will answer the question “How will we make this change?”
- Duration 1-2 days
- Assign Owner
scrumreferencecard.com

18. The Scrum Process - Increment
By Lakeworks - Own work, GFDL, https://commons.wikimedia.org/w/index.php?curid=3526338
“At the end of a Sprint, the new Increment must be “Done,” which means it must
be in useable condition and meet the Scrum Team’s definition of “Done.” It must
be in useable condition regardless of whether the Product Owner decides to
actually release it”

19. Scrum Events

20. Scrum Events
• The Sprint
– The heart of Scrum is a Sprint, a time-box of one month or less during which a
“Done”, useable, and potentially releasable product Increment is created
• Sprint Planning
– The work to be performed in the Sprint plans at the Sprint Planning. This plan is
created by the collaborative work of the entire Scrum Team
• Daily Scrum
– The Daily Scrum is a 15-minute time-boxed event for the Development Team to
synchronize activities and create a plan for the next 24 hours. This is done by
inspecting the work since the last Daily Scrum and forecasting the work that could
be done before the next one”
• Sprint Review
– A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt
the Product Backlog if needed. During the Sprint Review, the Scrum Team and
stakeholders collaborate about what was done in the Sprint
• Sprint Retrospective
– The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and
create a plan for improvements to be enacted during the next Sprint.

21. Events Goals and Deliverables
Event Goal Deliverables
The Sprint A time-box duration which a
“Done”, usable, and Increment is
created potentially releasable
product
A working Increment
Sprint Planning Part I: What can be done this
sprint?
Part II: How will the chosen work
get done?
Product Backlog, Sprint
Goal, list of selected
Product Backlog
Define “Done”, Check List,
Sprint Backlog (Sprint Plan:
Tasks & Owner)
Daily Meeting Inspect and adapt the progress
toward the Sprint Goal
• What did I do
yesterday?
• What will I do today?
• Do I see any
impediment?
Updated Scrum Board,
Updated Sprint Backlog
Burn-Down/Up

22. Events Goals and Deliverables
Event Goal Deliverables
Sprint Review Inspect the Increment and Adapt
the Product Backlog
1. P.O. explain what is
“done” and what is not
“Done”
2. Dev. Team explain
overall achievements
3. Demonstrate the
Increment
4. Refine Product Backlog
Sprint Retrospective Inspect itself and provide a plan
to adjust in the next Sprint
A plan with improvements
for the next Sprint
Product Refining Refine the Product Backlog Refined Product Backlog,
Updated Product Backlog
Burn-Down/Up
1 Sprint Backlog
Sub-Task
Provide daily task to execute Working task, Updated
Sprint Backlog Burn-
Down/Up

23. The Sprint Framework
“The heart of Scrum is a Sprint, a time-box of one month or less
during which a "Done", useable, and potentially releasable
product Increment is created. This applies to every Sprint”

24. Time Box
Event 1 Month 2 Weeks
The Sprint*1 30 days/4 weeks 2 weeks
Sprint Planning 8 hours 4 hours
Daily Meeting 15minutes 15minutes
Sprint Review 4 hours 2 hours
Sprint Retrospective 3 hours 1.5 hours
Product Refining (<10% Dev. Team
time)
<2 days <1 days
1 Sprint Backlog Sub-task*2 1-2 days 1-2 days
Time-boxed events are events that have a maximum duration.
1: Sprint should be short enough to keep the business risk
acceptable to the Product Owner and to be able to synchronize
the development work with other business events
2: The duration of the first tasks should be less than a 1 day

25. Sprint Planning
• The goal is to answer the following:
1. Part I: What can be done this sprint?
2. Part II: How will the chosen work get done?

26. Part I: What can be done this sprint?
• Input: Product Backlog, latest product Increment, project
capacity of the Dev. Team, past performance of the Dev.
Team (Team Velocity)
1. Dev. Team to assess and select from the Product Backlog
what to execute
2. Craft a Sprint Goal
3. An objective set for the sprint that can be met through
the implementation of the Product Backlog
– It provides guidance to the Dev. Team on why it is building the
Increment
– Size the effort for each item
– Generate agreed list of the Product Backlog

27. Part II: How will the chosen work get done?
1. Define what “does “Done” means in practical terms” along
with a Check List (verifiable condition - tests) agreed by the
P.O. and the Dev. Team
2. Generate the Sprint Backlog:
– Detailed Sprint Backlog
– A plan to deliver the selected Product Backlog
• Detailed description
• Assigned owner
3. The plan
– System Design
– Work needed to convert the product backlog into a working product
Increment
– Task duration should be 1-2 days, for the first few days it should be
less than a 1 day
• Output
– The Dev. Team is able to explain how the plan will accomplish the
Sprint Goal

28. • At the first Sprint, the Product Owner collaborates
with the Scrum Master and also select the
Developer Architect to help him to assemble the
team
• This is the initial Scrum’s Team
• The Developer Architect is changeable; Thus, he can
be replaced any time with another Dev. Engineer
• First Sprint may used for Go/No Go Prototype
product
• Multiple Development Teams must have one
Product Backlog and a definition of "done" that
makes their combined work potentially releasable
Part II: How will the chosen work get done?

29. Daily Scrum
• The meeting is used to inspect and adapt the progress toward
the Sprint Goal
1. Traditionally, 3 questions are asked:
1. What did I do yesterday?
2. What will I do today?
3. Do I see any impediment?
2. Updating the Scrum Board
– Update, revise, prioritize the progress and assignment – finished
and new
3. Updating the Sprint Backlog Burn-Down/Up
• If needed, a brainstorm/clarification meeting will occur after
the Daily Scrum meeting

30. Daily Scrum
Round status check with each individual
Update Scrum Boards and Sprint Backlog Burn-Down/Up

31. Scrum Board
Used to Track Status
programmers.stackexchange.com

32. Burn-Down Chart
Describes the remaining workload
- The Work units are the Story Points
- The Time units are 1 Day https://www.axosoft.com/scrum

33. Sprint Review
• Sprint review Inspect the Increment and Adapt the Product
Backlog if needed
• This is an informal meeting, not a status meeting
1. Product Owner explains what have been “Done” and what has not
been “Done”
2. The Dev. Team explain what went well, problem and how they are
solved
3. Demo the work that has “Done” and answers questions about the
Increment; Updating the Product Backlog Burn-Down/Up
4. The Product Owner discusses on the current Product Backlog and
expected completion date (if needed)
5. A short discussion on what to do next. This will be input for the
next Sprint Planning (Product Refining)
6. Recheck if the marketplace has new value and need to refine the
Product Backlog
7. Review the timeline, budget, potential capability, marketplace for
the next release of the product
• The output of the meeting may be a revised Product Backlog

34. Sprint Retrospective
• Sprint review Inspect itself and provide a plan to adjust
the next Sprint
• This is a formal meeting, but NO meeting minutes unless
agreed by all
• The purpose of the meeting is:
1. Inspect how the last sprint went in regards to people,
relationships, process, and tools;
2. Identify and order the major items that went well and potential
improvements; and
3. Create a plan for implementing improvements to the way the
Scrum Team does its work
• The output of the meeting should be a plan with
improvements for the next Sprint

35. Definition of “Done”
“The purpose of each Sprint is to deliver Increments of
potentially releasable functionality that adhere to the Scrum
Team's current definition of "Done"”

36. A picture is worth a thousand words…

37. www.scrumprimer.org

39. Links to Previous Managements
Fundamentals Lectures
Lecture # Topic Description
1 Introduction Describes the difference between Soft Skills and
Hard Skills
2 The Iceberg Model Explain why soft skills are the primary contributor to
project success
3 Communication Manage one of the main causes for project failure;
Get familiar with The C’s of Communication's model
4, part 1 Building A Team Part 1 Learn the 4 stages of team building
4, part 2 Building A Team Part 2 10 steps to develop an effective team
5 Motivation Your best Ally, 3 motivation models