This document provides an overview of Scrum, a framework for managing product development. It discusses how Scrum addresses issues like lack of progress and the need for new ways of working. Scrum uses short cycles ("sprints") to focus teams on goals, with daily stand-ups to track progress and impediments. Roles include the Product Owner who prioritizes goals, the Scrum Master who facilitates the process, and cross-functional team members. Sprints end with demonstrations and retrospectives to continuously improve. The values of Scrum emphasize inspection, adaptation, clear goals, teamwork and learning to deliver working products.

2. A NEW WAY OF
DOING THINGS
SCRUM

3. WHY PEOPLE HATE WORK?
People don’t get stuff done

4. “Two decades ago I was desperate
I needed a new way of thinking about work”
And through tons of research and experimentation and looking over
past data I realised we all needed a new way of doing things done.
!
-Jeff Sutherland

5. noun
a Rugby play in which, typically, three members of each team line up opposite one another with a group of two and
a group of three players behind them, making an eight-person, three-two-three formation on each side; the ball is
then rolled between the opposing front lines, the players of which stand with arms around a teammate's waist,
meeting the opponent shoulder to shoulder, and attempt to kick the ball backward to a teammate.
[skruhm]
SCRUM

6. INTENSE FOCUS ON THE GOAL
BUILT UP AND ENERGIZED
RADICAL COLLABORATION
ARMS AND BODIES LOCKED TOGETHER
PUSHING FOR THE SAME GOAL
HUNGER TO CRUSH
CRUSH ANYTHING IN THEIR WAY WAS TO BE OBLITERATED
UNIVERSAL EXCITEMENT
WHEN ANY TEAM MEMBER BROKE THROUGH WITH THE BALL
COLLABORATION

7. SCRUM IS BASED ON A SIMPLE IDEA
STOP, LOOK, AND GO
- DAVID STEINDL-RAST

8. PDCA CYCLE
PLAN. Do. CHECK. ACT

9. SCRUM
actors conversations artifacts
THINGS

10. PRODUCT OWNER (PO) SCRUM MASTER (SM) TEAM MEMBER (TM)
THE ACTORS

11. stand up
meeting
DAY 2-8
INSPECT AND
ADAPT
THE CONVERSATIONS
sprint
planning
DAY 1
CLEAR GOAL

12. sprint
retrospective
DAY 10
VOICE AND
IMPROVEMENT
THE CONVERSATIONS
sprint
review
DAY 10
GOOD PRODUCT

13. • User story
• Product backlog
• Burndown chart
THE ARTIFACTS

14. Plan are worthless, PLANNING is everything.
DAY 1 - SPRINT PLANNING
4 HOURS
PO, SM, TM

15. Team need to know what to do
Refine and estimate sprint backlog
Prioritise sprint backlog
READY - READY

16. Independent
Negotiable
Valuable
Estimable
Small
Testable
USER STORY

17. INSPECT and ADAPT. Fail quickly then fix early.
DAY 2 TO 9 - DAILY STAND UP MEETING
ONLY 15 MINUTES
SM, TM

18. What did you do yesterday?
What will you do today?
Are there any impediments in your way?
3 QUICK QUESTIONS

19. MAKE WORK VISIBLE
Team will self organized to do great things without
telling them anything about how to do

20. SPECIAL TIPS
Do one thing at a time

21. DEMO or Die. Actually working software.
DAY 10 - SPRINT REVIEW
4 HOURS
STAKEHOLDER, PO, SM, TM

22. “Kaizen” or IMPROVEMENT.
DAY 10 - SPRINT RETROSPECTIVE
30 MINUTES
PO, SM, TM

23. 1. Silent Writing
2. Post Ideas
3. Group Ideas
4. Prioritize
5. Discuss Highest Priorities
6. Create a Plan
RETROSPECTIVE TIPS

24. What went right?
What could have gone better?
What can be made better in the next sprint?
TEAM AND PROCESS

25. INSPECT
AND
ADAPT
PRIORITIZED
GOOD
PRODUCT
CLEAR
GOAL
VOICE
learn
cross
function
team
work
people
ideas
culture
VALUES
WAY FOR US TO LEARN ABOUT THE PRODUCT
AND HOW WE’RE BUILDING IT
AND HOW TO GET BETTER IN TIME

26. Trust the other folks without watching them all the time but
trusting that they’re gonna come through with their parts
-Steve Job

27. Rip up your business cards
Get rid of all titles, all managers, all structures
Performance is about the team no individual contributions
- Jeff Sutherland

28. TRUE HAPPINESS IS THE JOURNEY, NOT THE DESTINATION
- ALAMANDA SHANTIKA -
THANK YOU