Let's learn scrum

1. Let’s Learn
Scrum

2. Reference from Scrum Guide & best practices

3. Topics to cover Starting with.. Q&A Done!
Key concepts
Scrum Framework -
Roles, events, artifacts,
metric
Learning board

4. Topics to cover Starting with.. Q&A Done!
Key concepts
Scrum Framework -
Roles, events, artifacts,
metric
Learning board

5. ● It’s a framework
● primarily meant for complex projects with evolving
requirements, frequent client changes and cope up
with changing business dynamics
● It is not an acronym
About Scrum

6. ● Helps in shortening the feedback loop through
concept of sprint
● Intent is -
○ Get multiple opportunities of feedback
○ Incorporate changes suggested
○ Incremental valuable & potentially shippable outcome
○ Continuous improvement
About Scrum

7. ● Research
● Develop - products, enhancements & reengineering
● Frequent releases
● Managing operations
● Almost any segment from daily life chores till
organizational deliverables..
Kind of projects it could be used?

8. Topics to cover Starting with.. Q&A Done!
Key concepts
Scrum Framework -
Roles, events, artifacts,
metric
Learning board

9. PAM
Product
Owner
SAM
Scrum
Master
DAM
Development
Team
Form the Scrum Team first!

10. ● Sole responsible for What, Why & When aspect
● Defines & expresses the Product Backlog Items (PBI) & timely consult with
development team
● Prioritising the work in the order of priority
● Identify & optimise the value of the work
● Ensures backlog transparency, always, for all
● Ensures the understanding of the backlog items
● Only PO can make a change in the PBI’s priority
● No one should bypass the PO’s decision & ask Development team to do
different work
Product Owner

11. ● Responsible to deliver the potentially shippable increment (DONE items) at the
end of each sprint
● Self-organizing: structure & organise their work to create increment
themselves
● Cross-functional - has all skill as a team
● No titles & No sub-teams
● May individuals have specialised skill but accountability is with all
● 3-9 development team members
Development Team

12. ● Servant leader
● Problem solver
● Protects team from outside distractions
● Value-focused coaching
● Serves PO - in creating awareness, effective backlog mgmt, clarity of PBIs,
empiricism in product planning, prioritising backlog, facilitating events as
requested or needed
● Serves DT - in being self-organizing, create high value products, removes
blockers/ impediments, facilitating scrum events, coaching individuals
● Serves organization - in scrum implementation, productivity focused, partner with
other scrum-masters
Scrum Master

13. ● Time-boxed event
● At the start of it we do just enough planning & at the end we are supposed to deliver a
potentially shippable increment
● 1-4 weeks
● Has following - the sprint planning, daily scrums, the development work, backlog refinement,
the review & the retrospective
● No changes in sprint dynamics & if changed then it will hamper the sprint goals
● Quality goals are not compromised
● Scope may get re-negotiated between PO & Dev Team
● Each sprint may be considered as a project
● A sprint can be cancelled if it no longer makes sense
Sprint

14. Sprint Timeboxing - suggested
Events 1 Wk sprint 2 Wks Sprint 3 Wks Sprint 4 Wks Sprint
Sprint Planning 2 hours 4 hours 6 hours 8 hours
Daily Scrum 15 min 15 min 15 min 15 min
Review 1 hour 2 hours 3 hours 4 hours
Retrospective 45 min 1.5 hours 2.25 hours 3 hours

15. Sprint Timeline - ACTION PLAN (an instance of housekeeping as Inspiration)

16. ● 2 primary elements
○ What could be delivered as in increment by the sprint ends?
○ How are we going to achieve the work needed to deliver?
● 4 key inputs to sprint planning
○ The latest increment, team’s sprint capacity, velocity and PBIs
● Bring anyone who can help the development team to decompose the work
● 3 parts
○ Part 1 - ‘What?’
■ PO explains the sprint objectives
■ All discusses the PBIs needed to achieve them
■ Entire scrum team collaborates to understand ‘WHAT’
■ Velocity (past performance) guides development team to commit (& ONLY THEY CAN COMMIT)
Sprint Planning

17. ● Part 2 - How?
○ Development team decides how could they deliver the increment to meet
goals
○ Decomposes the work into smaller pieces of effort - one day or less
○ If capacity is full then it needs to trade-off or renegotiate on other work items
which are more important
● Part 3 - Explain
○ Finally, the Development team explains how could they work as a self-
organizing team to achieve the sprint goal & aspired increment
Sprint Planning

18. In Sprint Review, cleaning the board by removing DONE
stories
18

19. In Sprint planning, Check the UNDONE stories from
previous sprint & new stories from current sprint
19

20. Prioritise backlog, splitted down to tasks, finish estimation
20

21. Step 5 - And everything should have a meaning like...
Team name, Sprint#, Start date &
End date of sprint
Color codes like post-it color
signifies its a story or task or
kind of task and also
distinguishes different goals.
Each post it also has estimates
like stories have story points and
tasks have hours
We keep our primary focus towards
achieving the sprint goals over
finishing only specific tasks
Definition of Done helps us in knowing all the
necessities that confirms the quality and
shared understanding towards work
COMPLETION
21

22. ● For the development team
● Happens every day at the same time & place to reduce complexity
● Purpose is to inspect the progress towards sprint goal & forecast the next work to achieve the
sprint goal
● Format is set by the development team & can be conducted in different ways - purpose is to
focus on progress towards the sprint goal..
● Usually 3 questions helps:
○ What did I do yesterday?
○ What will I do today?
○ Do I see any impediments & blockers from meeting the sprint goals?
● After scrum, team often meets for detailed discussion or replan sprint work..
Daily Scrum

23. ● Scrum Master teaches Development team effective ways
● Its an internal meeting for the development team
● Scrum Master avoids disrupts from others who are present
Daily Scrum

24. Happy Standup :)

25. ● Happens at the end of the sprint
● Scrum & stakeholders collaborates to check the sprint goals delivered, Increment
maturity and changes the backlog to create value in future increment
● SM ensures the purpose of the meeting is known to attendees
● PO explains what is DONE & NOT-DONE
● Dev Team explains their experience while achieving sprint goals
● PO discusses timeline, delivery date, state of Product backlog & maturity of
increment
● Review of marketplace experience & next valuable thing to deliver
● At offset, we have a revised backlog based on feedbacks
Sprint Review

26. ● Scrum team inspects itself & identifies action plan for improvement during the
next sprint
● Last meeting of the sprint
● It should be positive & productive
● Check the improvements that we were supposed to make during the sprint..
● Identify what went well & what needs to be improved & how can we make those
improvements
● Qualitative & DONE outcomes are always considered
Sprint Retrospective

27. Potentially Shippable
Product
Increment
Review
No Changes
in Duration or Goal
Retrospective
Team
Daily Scrum
Meeting
Product Owner
Input from End-Users,
Customers, Team and
Other Stakeholders
Product
Backlog
Refinement
Scrum Master
SCRUM FRAMEWORK
Product Backlog
Sprint
Backlog
Sprint
1-4 Weeks
8
9
10
11
12
7
1
2
3
4
5
6
The Scrum Team
Sprint Planning
Meeting
Team Selects
How Much To
Commit To
By Sprint’s End
7
1
2
3
4
5
6

28. Levels of planning

29. ● Specific to scrum team
● Team must have a shared understanding
● It is used to assess when the work is complete
● It guides the development team in making the commitments
● The Sprint Increment should be potentially shippable hence DOD is important
● Means - qualitative, usable, no risk, thoroughly tested, just enough documentation
● It should be considered as STANDARD of any work
Definition of DONE

30. Topics to cover Starting with.. Q&A Done!
Key concepts
Scrum Framework -
Roles, events, artifacts,
metric
Learning board

31. Topics to cover Starting with.. Q&A Done!
Key concepts
Scrum Framework -
Roles, events, artifacts,
metric
Learning board

32. THANK YOU
www.Benzne.com
Anuj M Ojha