Boris Hinzer provides an overview of Agile and Scrum concepts and practices. He discusses the four values and twelve principles of Agile, as well as the roles, artifacts, and events that are part of Scrum such as the Product Owner, Development Team, product backlog, sprints, sprint planning, daily scrums, sprint reviews, and retrospectives. Hinzer also provides tips, hints and things to avoid when implementing Scrum. The presentation aims to help people understand the basics of Agile and Scrum as well as ways to improve their implementation.

1. Hacking Agile
not a tech talk

2. Boris Hinzer
TYPO3 Fanboy
TYPO3 Association Board
Education Committee
CertiFUNcation Firestarter
web-vision // FGTCLB
CEO, Founder, Scrum PSPO
Nerd, Gamer

3. Agile is DEAD

4. But it might need
some SOLID
punches on the heaD
Agile is DEADNOT

5. The values of Scrum

6. 4
The values of Scrum
The four Values of the agile Manfesto
1.Individuals and Interactions Over Processes and Tools
2.Working Software Over Comprehensive Documentation
3.Customer Collaboration Over Contract Negotiation
4.Responding to Change Over Following a Plan

7. The 6 CORE princiPLES
1. Customer satisfaction through early and continuous
software delivery
2. Accommodate changing requirements throughout
the development process
3. Frequent delivery of working software
4. Collaboration between the business stakeholders and
developers throughout the project
5. Support, trust, and motivate the people involved
6. Enable face-to-face interactions

8. The other 6
7. Working software is the primary measure of
progress
8. Agile processes to support a consistent
development pace
9. Attention to technical detail and design enhances
agility
10.Simplicity
11.Self-organizing teams encourage great
architectures, requirements, and designs
12.Regular reflections on how to become more
effective

9. 12
7. Working software is the primary measure of
progress
8. Agile processes to support a consistent
development pace
9. Attention to technical detail and design enhances
agility
10.Simplicity
11.Self-organizing teams encourage great
architectures, requirements, and designs
12.Regular reflections on how to become more
effective
The other 6

10. The Basics of Scrum

11. The Scrum TEAM
1 Product Owner
1 Scrum Master
9 Developer

12. The product backlog
Owned by the product owner
slice on from large to small
• Large
= Topics (eg. Interfaces ERP/PIM systems)
• Medium
= Epics (eg. search)
• Small
= User Stories or Tasks (eg. search form)
Should contain only what is needed in
next 2-3 sprints

13. The product backlog
• Introduce Epics for:
Impediments,
Kaizen and Scrum Events
• Color encode them
• Put your estimations at the Epics
HINTS

14. The product backlog
• Think ahead: „What could be a good Sprint
Goal for the upcoming sprint?“
• Tag Tasks, Stories, Epics already with
versions - You might need them later
• Try a Sprint Preparation Backlog (DoR)
BONUS

15. The product backlog
Sprint PREP

16. The product backlog
Sprint PREP
MVP = Minimum Viable Product
SLC = Simple, Lovable, Complete

17. The product backlog
Sprint PREP
SLC = Simple, Lovable, Complete

18. The Sprint PLANNING
Time for estimations based on comparisons
„an apple weighs twice as much as a mandarin“
often done with Story Points as Planning Poker
• Planning 1:
• The complete Scrum Team
• Answer to „What can be achieved in next
sprint?“
• Planning 2:
• Development Team
• Slicing of the stories in (sub)-tasks

19. The Sprint PLANNING
HINTS
• Planning 1:
• Find reference tasks and adjust them if
needed
• Prepare the planning by reading concepts,
asking questions ahead, checking
requirements and impediments ahead
• Planning 2:
• Prepare only as much as needed to start
• Slicing and backlog refinement can also be
done within Sprint
• keep or even lower the time box

20. The Sprint PLANNING
BONUS
Development team is responsible
what to put into the sprint backlog
Set a common Sprint Goal
Time for „Promise made…“
PROMISE MADE

21. Basics
The Sprint
Sprint = development cycle
always between one to four weeks
At the the end there should be a potentially
shippable increment oft software

22. HINTS
• Do’s…
• …time tracking daily - it is your friend
• …make deals - to meet the sprint goal and the budget
• …make budget spendings visible
The Sprint

23. • Do’s…
• …make slow mover visible - and fight
them actively
The Sprint
Hints

24. Do’s…
…make (over) communication visible
…take short cuts in communication - eg.
constant video calls in distributed teams)
…check old tasks frequently
The Sprint
Hints

25. The Sprint
Basics
Continue to improve the sprint backlog
permanently (refinement) during the sprint
Avoid…
…hidden impediments
No Impediments?
most likely THIS is also an
impediment!

26. The Sprint
Basics
Continue to improve the sprint backlog
permanently (refinement) during the sprint
Avoid…
…hidden agendas
No side notes!
put it in ur issue tracker!

27. The Sprint
Basics
Continue to improve the sprint backlog
permanently (refinement) during the sprint
Avoid…
…over engineering
…anything else besides the sprint goal
Be marie Kondo:
DOes it spark joy?

28. The SPRINT
Review often
…by giving the tasks / stories early to the Product Owner
…by introducing review columns to your agile boards
…gives a nice looking sprint burn downs

29. The SPRINT
Burn Down Flat Lines
…might be caused by late reviews
…might be caused by too much distraction
…might indicate too big stories - slice them smaller
…might indicate tasks which should be stories
…needs to be carefully watched

30. The DAILY SCRUM
Basics
Event for the Development Team
Should be done always at the same time
max 15 minutes time box
Report and check:
„What have I done yesterday?“ … to meet the sprint goal
„What I’m going to do today?“ … to meet the sprint goal
„What are my impediments?“ …which hinder me from
reaching the sprint goal

31. The DAILY SCRUM
Rules & HINTS
• No distraction (smartphones, laptop, …)
• Round robin procedure
• Keep the sprint goal in mind
• Stand Up
• Active Listening - What have others to tell?
• Follow up on details - eg. impediments

32. The DAILY SCRUM
Monitor process daily
…by taking a look at the sprint burn down chart

33. The DAILY SCRUM
If time is left…
…use remaining time for mini Scrum Quizzes
(sources: https://mlapshin.com or https://volkerdon.com/ )
Always…
…„any Deals we can make to today?“ to meet the sprint
goal?
BONUS

34. The SPRINT REVIEW
Basics
Event for the Scrum Team
Time for demo by the Development Team
Product Owner reviews „Sprint Goal fulfilled?“
Product Owner can decide if product increment
shall be released
PROMISE KEPT!

35. PROMISE KEPT!
The SPRINT REVIEW
HINTS
If you introduced Early Reviews during the
sprints…
…it might save time and money with shorter
sprint reviews
…internal reviews times can be booked on
directly on tickets

36. The SPRINT REVIEW
1. Live with it!
2. Bugs should NOT hinder you from a positive review
3. Better DONE than perfect!
YOU DON’T SAY
SOFTWARE. HAS. BUGS.

37. The SPRINT RETRO
Basics
Sprint Retrospective
Usually done immediately after the Sprint Review - with
the whole Scrum Team.
Get feedback of all participants to improve processes.
Should never be obsolete.
• What went well?
• What did not went well?
• What can we improve?
..should lead to continuous improvement actions items…
Kaizen

38. The SPRINT RETRO
more
START
STOP
KEEP
Less

39. The SPRINT RETRO
Kaizen action items
…should be visible during next sprint
…should be checked if they are working
…can also be part of your sprint board

40. Almost forgotten
Versions
Burn Up-Chart aka Version Report
„When are we done?“
„What can we achieve until our CEO demo?“
„How is our performance over the whole project?“

41. The Basics of Scrum

42. BUT there is more
• Scan for old / missed stories in your backlog
• WiP Limit
• Velocity charts
• The godfather … of a story
• From russia with love - MoSCoW
• …
Stay foolish,
stay agile!

43. b.hinzer@web-vision.de
twitter: web_vision_de
https://www.web-vision.de
Boris Hinzer
Thank you!