This document summarizes key aspects of Scrum events from a Greek translation of the Scrum Guide. It discusses the Sprint as the heart of Scrum, involving iterative development within timeboxed periods to deliver working software increments. It describes effective practices for Sprint Planning such as focusing on the highest priority work and estimating tasks, and emphasizes the Daily Scrum as a standing meeting for synchronization rather than status reporting. The Sprint Review involves demonstrating the increment to stakeholders to gather feedback and drive further priorities.

1. Welcome
17th Athens Agile/Scrum Meetup
May 2015
http://www.meetup.com/Agile-Greece
sponsored by Agile Actors

2. The Scrum events
Sprint
Planning
Daily
Review
Retrospectives

3. Definition The Sprint
(from Greek Translation of Scrum Guide):
Η καρδιά του Scrum είναι
το Sprint,
ένας χρονο-περιορισμός
ενός μήνα η λιγότερο,
κατά τη διάρκεια του
οποίου δημιουργείται μία "Έτοιμη", χρησιμοποιήσιμη και
δυνητικά παραδοτέα Επαύξηση προϊόντος.

4. Agility & The Sprint
Iterative &
Incremental Delivery
Smaller batches of work
(Click to go)
Short feedback loops and learning/adaptation cycles

5. The container The Sprint
Complexity requires empiricism.
Iterations = Experiments
Sprint is the container of the experiment
“... At the end of the time-box, we open the container and
inspect the results…” Ken Schwaber

6. Benefits The Sprint
Laser focus
on the most important stuff
“I've always said timeboxes
weren't about time, but about forcing hard decisions.”
Jim HighSmith

7. Benefits The Sprint
Sustainable
development
(Click to go)
“...The sponsors, developers, and users should be able to
maintain a constant pace indefinitely.”
Agile Manifesto Principles

8. Benefits The Sprint
Cadence (rhythm)
or corporate heartbeat
“An organization that
delivers at a regular cadence has established its process
capability and can easily measure its capacity.”
Mary Poppendieck

9. Benefits The Sprint
Helps to measure
your team's velocity
"Not knowing the velocity
of production of the teams is the root cause of 100% failure
of release plans.”
Jeff Sutherland

10. How The Sprint
Find out the right Sprint length
Do not forget to set the Sprint Goal
Clear and commonly agreed Definition of Done
Do not full the Sprint (avoid overcommitment)

11. How The Sprint
Establish the right
engineering practices
for having
working software
at the end of the Sprint
Managing Technical Debt,
Automate Testing/Deployments,
Branching/Merging Strategy

12. The Sprint
See it as a container for
your experiment and
approach it like a game
Test Learn Adjust Improve

13. The Sprint Planning

14. Focus & pace
Team needs to be
✓ Awake
✓ Cooperative
✓ Focused

15. ✓ Know what are currently the most important features and why
✓ Prepare beforehand trying to meet DoR (refinements)
✓ You need to know it and believe it so that you can pass it on to your team.
✓ A team that knows what is doing and why, might be more willing and
successful at taking up unknowns and coping with dependencies.
PO and Sprint Planning

16. Inspect and Adapt
✓ Black box
✓ Urgent velocity
✓ PBIs for research, deployments
✓ Try to achieve shippable increment, live demo
✓ Avoid chained PBIs
✓ Shared PBIs in all SCRUM boards
✓ PBI may change during "how”

17. ✓ Time limitation
✓ Average or worst case scenario
✓ Use the extra cards if needed and
agreed
✓ Invite people to attend if needed
Poker Planning

18. ✓ Do they match?
✓ Do they reflect the best ROI for you product at that
current moment?
✓ Is the whole team aligned and committed to the
goal?
✓ Now remember nothing is written in stone!
Sprint Goal & Sprint Backlog

19. The Daily Scrum

20. The Daily Scrum
It is not only about standing up
Time-boxed sync meeting
Planning meeting
Inspect

21. Let’s have a
Daily Scrum!
NO!
It’s unproductive

22. A Not so Effective Daily Scrum
Report to leader
Wait to talk until standup
Not talking at the standup

23. A Not so Effective Daily Scrum
Not a habit

24. A Not so Effective Daily Scrum
Not a habit
Too many
people

25. A Not so Effective Daily Scrum
Not a habit
Too many
people
Not that many

26. A Not so Effective Daily Scrum
Lack of preparation

27. A Not so Effective Daily Scrum
Lack of preparation
Starts the day

28. A Not so Effective Daily Scrum
Lack of preparation
Starts the day
Not reporting impediments

29. A little better Daily Scrum
Clear Sprint Goal

30. A little better Daily Scrum
Clear Sprint Goal
Let team pick the time | Be
on time

31. A little better Daily Scrum
Clear Sprint Goal
Let team pick the time | Be
on time
Hear | Ask | Talk

32. A little better Daily Scrum
Clear Sprint Goal
Let team pick the time | Be
on time
Hear | Ask | Talk
Use a physical wall w/ post-it if
possible

33. A little better Daily Scrum
Signal the problem. Solve
later
Clear Sprint Goal
Let team pick the time | Be
on time
Hear | Ask | Talk
Use a physical wall w/ post-it if
possible

34. A little better Daily Scrum
Get a Token stick |
change order

35. A little better Daily Scrum
Get a Token stick |
change order
Leave w/ plan

36. A little better Daily Scrum
Get a Token stick |
change order
End on time!
Leave w/ plan

38. The Sprint Review
What are we reviewing?

39. The Sprint Review
Presentable artifacts
● Prefer User interface deliverables
● If no UI, find a way to demonstrate progress
● Depending the audience decide the
technical depth of the demo

40. The Sprint Review
Review Preparation
● Make it a rotated task
● The task owner is responsible for the review
flow
● The task owner should consult the team
members if necessary
● Better deploy to a dedicated server

41. The Sprint Review
Review Execution
● Invite people
● Accept feedback from everyone
● Keep notes (record if necessary)
● Focus on happy paths
● Prompt reviewers to play with the application
● Do not make commitments

42. The Sprint Review
Why we do reviews?
● Drive the scope
● Minimize risk
● Deliver working software

43. The Scrum events
Thank you!
Special thanks to:
Yiannis Mavraganis (The Sprint)
Maria Toutountzi/Dimitris Vougas (Planning)
George Psistakis (Daily Scrum)
Nikos Raptis (Review)
John Pagonis (Retrospectives)
www.agilegreece.org @AgileGreeceOrg www.agilegreecesummit2015.
org