This document provides an overview of Scrum, an agile framework for managing product development. It defines key Scrum concepts like values, roles, events, and artifacts. The Scrum Team includes developers, a product owner, and a Scrum master. Events like sprint planning, daily scrums, sprint reviews and retrospectives help the team set goals, track progress, and improve. The product backlog, sprint backlog and definition of done are important artifacts. Scrum aims to deliver value through short development cycles called sprints, collaboration, self-organization and accountability.

1. Scrum Basics

2. What is Agile?
#webeforeme

3. Agile Manifesto
#webeforeme
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

4. Scrum Values
● Commitment
● Focus
● Openness
● Respect
● Courage
What is Scrum?
#webeforeme
Scrum is an iterative and incremental agile software development framework for
managing product development.
Scrum is a lightweight framework that helps people, teams and organizations generate
value through adaptive solutions for complex problems.
Scrum is a framework for managing software development.

5. Scrum Team
#webeforeme
What is Team?
What is Scrum Team?
Scrum Team Structure?
Size of Scrum Team
Cross Functional Team
Self managing Team

6. Developers
#webeforeme
Developers are the people in the Scrum Team that are committed to creating
any aspect of a usable Increment each Sprint.
Accountable for:
● Creating a plan for the Sprint, the Sprint Backlog;
● Instilling quality by adhering to a Definition of Done;
● Adapting their plan each day toward the Sprint Goal; and,
● Holding each other accountable as professionals.

7. Product Owner
#webeforeme
The Product Owner is accountable for maximizing the value of the product
resulting from the work of the Scrum Team. How this is done may vary widely
across organizations, Scrum Teams, and individuals.
Accountable for:
● Developing and explicitly communicating the Product Goal;
● Creating and clearly communicating Product Backlog items;
● Ordering Product Backlog items; and,
● Ensuring that the Product Backlog is transparent, visible and understood

8. Scrum Master
#webeforeme
Scrum Masters are true leaders who serve the scrum team and the large
organization
Serve scrum team in several ways:
● Coaching the team members in self-management and cross-functionality
● Helping the Scrum Team focus on creating high-value Increments that meet the
Definition of Done;
● Causing the removal of impediments to the Scrum Team’s progress; and,
● Ensuring that all Scrum events take place and are positive, productive, and kept
within the timebox.

9. Serve Product Owner in several ways:
● Helping find techniques for effective Product Goal definition and
Product Backlog management;
● Helping the Scrum Team understand the need for clear and
concise Product Backlog items;
● Helping establish empirical product planning for a complex
environment; and,
● Facilitating stakeholder collaboration as requested or needed.
Scrum Master
#webeforeme

10. Serve Organization in several ways:
● Leading, training, and coaching the organization in its Scrum
adoption;
● Planning and advising Scrum implementations within the
organization;
● Helping employees and stakeholders understand and enact an
empirical approach for complex work; and,
● Removing barriers between stakeholders and Scrum Teams.
Scrum Master
#webeforeme

11. What is Events?
What is Scrum Events?
All scrum events are Timeboxed
Scrum Events
#webeforeme

12. The Sprint
#webeforeme
Sprints are the heartbeat of Scrum, where ideas are turned into values.
Time Length: One month or less.
All other scrum events happen within Sprint.
During The Sprint:
● No changes are made that would endanger the Sprint Goal;
● Quality does not decrease;
● The Product Backlog is refined as needed; and,
● Scope may be clarified and renegotiated with the Product Owner as
more is learned.

13. Cancel Sprint?
● When?
● Who?
The Sprint
#webeforeme
Forecast Sprint Progress
● Burn-downs
● Burn-ups
● cumulative flows

14. Sprint Planning
#webeforeme
Timebox: Eight hours for a four-week sprint, proportionately shorter for shorter
sprints
Attendees: The complete Scrum team, including all roles
Most important: Team capacity and DoD

15. Purpose of Sprint Planning Meeting
#webeforeme
A Sprint Goal
A Sprint Backlog

16. Sprint Planning Meeting Best Practices
#webeforeme
Create a recursive calendar invitation include all team members.
Meeting invitation for agile sprint planning should be from the SM
Include agenda in the invitation, add the user stories link which should be
included in the sprint
Make sure the User story you are proposing from the sprint should be
really defined well, all the use cases, functional requirements and
condition of satisfaction are in detailed level and, at least, grooming once
with some senior team members.
Order a tea/Coffee with something sweet, sometimes a coffee bribe does
work or, at least, it keep the developers or QA not to fell a sleep.

17. Sprint Planning Meeting Rules
#webeforeme
Remember the sprint planning meeting is run by scrum master and he has
the highest authority.
PO role in sprint planning meeting is only as a contributor, (s)he make active
contributor in answering the question if the team have and explaining the
user stories to the team.
Scrum master is the timekeeper, leader, facilitator, and coordinator of the
agile sprint planning meeting

18. Sprint Planning Checklist: Product Owner
#webeforeme
Define Sprint Scope
Define each User Story items in detail
Prepare notes or include them in the agenda the thing concern, the question for a
particular user story so the team can come prepare and have those answers before
the before.
Make sure backlog is in priority order
Describe definition of done for each user story and for sprint

19. Sprint Planning Checklist: Scrum Master
#webeforeme
Making sure video, audio conference is reserved and working
Pre-order coffee and light refreshment, “no coffee no code”
Enough post-it notes and markers, whiteboard etc.
Available capacity for the team (team members holidays, public holidays, etc)
Keep tracking the team’s velocity vs the amount of work committed by the team

20. Sprint Planning Checklist: Development Team
#webeforeme
Ask questions to clear any ambiguity or else “speak now or hold your“
Do not commit more than you can not deliver
Remember to think of your personal availability for the coming sprint.
Taking part in technical discussion during estimation or planning poker

21. Sprint Planning Meeting: Summary
#webeforeme
Input
- Product Goal
- Team Capacity
- Groomed Product
Backlog
- Business Conditions
- Current Product
- Definition of Done
- Sprint Planning Meeting
- Tools And Techniques
- Planning Poker
- Expert Judgement
- Brainstorming
- Knowledge Sharing
- Collaborations
Output
- Sprint Goal
- Backlog item
solutions
- Sprint Backlog

22. Daily Scrum
#webeforeme
This is not Reporting Meeting.
Timebox: Fifteen minutes is standard, irrespective of the duration of
the sprint length
Attendees: The complete Scrum team, including all roles
Most important: To speak about any impediments

23. Daily Scrum: Best Practices
#webeforeme
Remain Standing
3 questions agenda
Have your project management tool visible
It’s a collaborative effort
Plan the meeting around the team

24. Daily Scrum: Avoid
#webeforeme
Waiting around your team
Introducing new idea
Letting people ramble

25. Sprint Review
#webeforeme
The purpose of the Sprint Review is to inspect the outcome of the Sprint
and determine future adaptations. The Scrum Team presents the results of
their work to key stakeholders and progress toward the Product Goal is
discussed.
Timebox: Four hours for a four-week sprint, proportionately shorter for
shorter sprints
Attendees: The complete Scrum team, including all roles, plus any other
stakeholders who are interested in the project success
Most important: Demo of working software and assessing the feedback

26. Sprint Retrospective
#webeforeme
The purpose of the Sprint Retrospective is to plan ways to increase quality and
effectiveness.
Timebox: Three hours for a four-week sprint, proportionately shorter for shorter
sprints
Attendees: The complete Scrum team, including all roles; the product owner's
attendance is optional
Most important: To brainstorm and agree on what is working and what is not

27. Sprint Retrospective: Problems
#webeforeme
Boring
Repeat Same Problem

28. Scrum Artifacts
#webeforeme
Product backlog
Commitment: Product Goal
Sprint Backlog
Commitment: Sprint Goal
Increment
Commitment: Definition of Done

29. #webeforeme

30. References
#webeforeme
https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf
https://www.atlassian.com/agile/scrum
https://resources.scrumalliance.org/