How to apply "Scrum Framework" to your project management. It was a 5-6 hours workshop talking about the experiences and best practices about Scrum.

1. A Quick Guide to Scrum
Sharif Accelerator - July 1st 2017

2. Hadi Sinaee
Co-Founder @ Hodhod IM
http://ce.sharif.ir/~sinaee
@HadiSinaee
● B.Sc Software Engineering -
Kashan University
● M.Sc Artificial Intelligence -
Sharif University of Technology
● Currently NodeJS Developer
@HodHod

3. pinimg.com

4. The Scrum Framework

5. Scrum
When / Why
● Fast feedback loop
Requirements change frequently
● All steps is not known in
advance

6. Elements
Building blocks of framework
● Scrum Team
● Scrum Events
● Scrum Artifacts

7. 1. Scrum Artifacts

8. Artifacts
3 main artifacts
● Product Backlog
● Sprint Backlog
● Increment

9. “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. It is never complete!”
Product Backlog

10. Requirement 1
Requirement 2
Requirement 3
Requirement 4
...
Product Backlog(PB)
Product Backlog Item (PBI)
User Story - Sample Format
Title
As <Type of User>
I want to <Some Goal> so that
<A Business Value>
Acceptance Criteria (AC):
☑ Condition 1
☑ Condition 2
Size: 1/2/3/5/8/?
https://www.mountaingoatsoftware.com/agile/user-stories

11. Sprint Backlog
“A forecast by the Dev. Team about what functionality will
be in the next Increment. Actually, it is a set of PBIs. It makes
visible the necessary works to meet the sprint goal.”

12. Requirement 1
Requirement 2
Requirement 3
Requirement 4
...
Product Backlog(PB)
As <Type of User>
I want to <Some Goal> so that
<A Business Value>
Acceptance Criteria (AC):
☑ Condition 1
☑ Condition 2
Requirement 1
Requirement 2
Requirement 3
Sprint Backlog(SB)

13. Increment
“It is the sum of all the PBIs completed during a Sprint. At
the end of a Sprint, the new Increment must be “Done” which
means it must be in useable condition and meet the definition
of “Done” ”

14. 2. Scrum Team

15. Roles
“Everybody’s finding their roles.
It’s like pieces of the puzzle are
coming together for us - Aaron
Cook”
● Product Owner
● Development Team
● Scrum Master

16. Development Team
“ It consists of professionals who do the work of delivering a
potentially releasable Increment of “Done” product at the end
of each Sprint. It is self-organizing and cross-functional”

17. Product Owner
“He/She is responsible for maximizing the value of the
product and the work of the Dev. Team. The sole person
responsible for managing the PB.”

18. Scrum Master
“ He/She is responsible for ensuring Scrum is understood
and enacted. Facilitating Scrum events as requested or
needed. Removing impediments to the Development Team’s
progress.”

19. 3. Scrum Events

20. Events
“We meet the people we’re
supposed to when the time is just
right - Alyson Noel”
● Sprint
● Sprint Planning
● Daily Meetings (Stand-ups)
● Sprint Review
● Sprint Retrospect

21. Sprint
“A time-box of one-month or less. Each Sprint may be
considered a project with no more than a one-month horizon.
Each Sprint has a definition of what is to be built.”

22. Sprint Planning
“The work to be performed in the Sprint is planned at the
Sprint Planning. This plan is created by the collaborative work
of the entire Scrum Team.”

23. Sprint Planning - Point Estimation
1 2 3 5 8
● “User Story Point Estimation” is about
estimating the size (very small to extra
large) of a story.
● You can use Fibonacci numbers as the
base numbers for a size of a story.
● First, find a PBI with size of 2 which all
Dev. Team members agree on.
● For every user story, all Dev. Team
members should individually raise one of
these cards as their estimation of the size
of the given story.
● All members have to agree on a same
number for a story.
● Based on your previous team velocity,
select PBIs.
Sample fib cards. All members have a
copy of these cards

24. Sprint Planning - Velocity
● Team Velocity(TV) simply is the average
of the previous Sprint Velocities.
● Sprint Velocity(SV) for a specific Sprint
is sum of the size of all completed PBIs.
● Example
○ We spent 3 sprints, each with SV of
9, 14, 19 respectively.
○ TV = (9+14+19)/3
● For the first time, there is no velocity.
Just guess a number based on your
knowledge.
○ Remember: Scrum is based on what
is done!
PBI 3
….
S: 1
To Do :(
PBI 1
….
S: 1
PBI 4
….
S: 8
PBI 5
….
S: 8
PBI 2
….
S: 3
In Progress :) Done :D
Scrum Board (Sprint 3): SV = 3 + 8 + 8 = 19

25. Daily Meetings
“It is a 15-minute time-boxed event for the Dev. Team to
synchronize activities and create a plan for the next 24 hours.
What did you do? What was the obstacles? What will you do
today?”

26. Daily Meetings - Burn Down Chart
● It is a Sprint Tracking mechanism.
● It can be computed by the following:
○ X-axis: days from beginning of the
sprint to the end of it
○ Y-axis: measurement unit(story-
point here)
○ For each day on x-axis, compute sum
of number of remaining units ( here
story point number) and then plot the
point on the Y-axis.
● Your plotted line has to be(approximately)
on the straight line(ideal).
● If it is not, there is a problem! Find it out!
Discuss it at Retrospect Meeting if it is
necessary.
http://www.scrum-institute.org/images_scrum/Sprint_Burndown.jpg

27. Sprint Review
“It is held at the end of the Sprint to inspect the Increment
and adapt the PB if needed. Scrum Team and key stakeholders
invited by the Product Owner. The Product Owner explains
what PBIs have been “Done” and what has not been “Done”.”

28. Sprint Retrospect
“It is an opportunity for the Scrum Team to inspect itself
and create a plan for improvements to be enacted during the
next Sprint.”

29. Events Overview
Sprint Planning
Meeting
Daily Meeting
Sprint Review
Meeting
Sprint Retrospective
Meeting

30. Tools

31. Tools
“We change our tools and then
tools change us - Jeff Bezos”
● Trello
● Jira
● Gitlab
● Vivify

32. Refs
● scrumguides.org
● scrumtrainingseries.com
● scrumalliance.org
● mountaingoatsoftware.com