Scrum is a framework for project management developed by Ken Schwaber and Jeff Sutherland. It is lightweight, simple, and difficult to master. Scrum uses self-organizing cross-functional teams, sprints, daily stand-ups, and artifacts like product backlogs and sprint backlogs. The goals are transparency, inspection, and adaptation. Scrum aims to deliver working software frequently through short development cycles and continuous improvement.

1. SCRUM – PROJECT MANAGEMENT
FRAMEWORK
DEVELOPED BY KEN SCHWABER AND JEFF
SUTHERLAND
By: ing. Anjana Saxena

2. Agenda
 Introduction
 Agile and Lean
 What's Scrum
 How does Scrum helps to deliver useful products
 Videos and Game

3. Agile and Lean
Agile Manifesto values
 Individuals and interactions over
processes and tools
 Working software over
comprehensive documentation
 Customer collaboration over contract
negotiation
 Responding to change over following
a plan
Lean Values
 Eliminate Waste
 Build Quality In
 Create Knowledge
 Defer Commitment
 Deliver Fast
 Respect People
 Optimize the Whole

4. A project without Scrum
Requirements Design Code Test

5. What is Scrum?
A framework within which people can
address complex adaptive problems, while
productively and creatively delivering products
of the highest possible value.
 Lightweight
 Simple to understand
 Difficult to master

6. Scrum Framework
 Scrum Teams and their associated roles
 Events
 Artifacts
Rules – binds all above

7. Three pillars of Scrum
 Transparency
 Inspection
 Adaptation

8. Transparency for Customers

9. Transparency for Scrum Team

10. Inspection & Adaptation

11. Sprint Teams and Communication
 Product Owner
 Scrum Team –
Scrum Master and
team
Scrum
Team
Produ
ct
Owner
Scrum
Master
Business Owner
Stakeholder
s

12. Scrum Events
 Sprint Planning meeting
 Daily Scrum meeting
 Sprint Review meeting
 Sprint Retrospective meeting

13. Velocity or Story Points

14. Sprint Planning Meeting
 Product owner and
Scrum team
 Prioritized Product
Backlog
 Estimated Sprint
backlog and Sprint
goal
 Work in the right
order based on
dependency
Product/Sprint backlog

15. Customer story Amsterdam

16. Sprint Review & Retrospective
 Inspect the iteration
 Collaboration team
and Stakeholders
 Inspect how the last
Sprint went
 Identify potential
improvements
 Create a plan for
implementing
improvements

17. Scrum Artifacts
 Product Backlog
 Sprint Backlog

18. Scrum

19. How does Scrum help?

20. Mini Projects/Quality Software

21. Scrum Planning Goal
Example sprint goals for an e-commerce
application:
 Implement basic shopping cart functionality
including add, remove, and update
quantities.
 Develop the checkout process: pay for an
order, pick shipping, order gift wrapping, etc.

22. Product –Sprint - Task

23. Example Product Backlog

24. Example Sprint Backlog

25. Ball point Game Rules
 You play in one or several Teams
 Starting point equals endpoint
 No passing of the ball to your direct neighbour
 The ball must have air-time
 Two minutes per iteration
 One minute for continuous improvement & new
estimate
 You play five iterations

26. Ball point Game Chart
Ball point Game chart
Iteration Estimate Velocity Results of change Retro outcome

27. Scrum Quotes
Mike Cohn
“
“Scrum has become recognized as one of the best project management frameworks for
handling rapidly changing or evolving projects, especially those with technology or
requirements… “
Mary Poppendieck
“The biggest cause of failure in software-intensive systems is not technical failure; it’s
building the wrong thing.”

28. References
 http://www.scrumguides.org/
 https://www.mountaingoatsoftware.com/company/about-
mike-cohn
 https://www.mitchlacey.com/intro-to-agile/scrum/the-
product-backlog
 Game by Boris Gloger

29. Scrum (Basics)
The End