The Sprint Review: �Origin for Collaboration and Communication

Florian Schmid ( https://www.linkedin.com/in/florian-schmid-64280b1a5/ ) and
Nils Hyoma ( https://www.linkedin.com/in/nils-hyoma-74a79244/ )

Code PaLOUsa 202218th of August 2022

1. The Sprint Review:
Source for Collaboration and
Communication
Florian Schmid and Nils Hyoma
Code PaLOUsa2022
18thof August 2022

2. Florian Schmid
2
§Agile AR + VR Developer
§Master of Digital Reality
§Likes Football and Soccer
§Shouter and Guitar Player of
Hardcore Bands

3. Nils Hyoma
3
§Agile Coach & Trainer
§Worked as a backend developer
§Water polo player and coach
§Farther of a8 year oldboy
§Studied economics and computer
science in Hamburg and Hiroshima
§Hates waste / muda

4. Florian and Nils
4

5. The Product
5

6. The Product
6

7. The Product
7

8. Product Hub
8

9. The Challenge
9
§Empty Backlog
§Product Owner is a Manging
Director
§High risk of delay / costs
§Operational excellence
§Almost no airport experience
§Fear of change
§A lot of failed “IT-Projects”

10. The Challenge –An almost chaotic world!
Requirements
Technologyknown
simple
unknown
unknown
chaotic
complex
complicated
Waterfall
Kanban
Scrum
(Epics, User Stories,
Acceptance Criteria’s)
Design Thinking
(maybe with Scrum?)
Scrum
(Focus on Collaboration)

11. “Business people and developers
must work
together daily throughout the
project.”
11
One of the Principles behind the Agile Manifesto

12. Shorter feedback loops, better ideas…
Product
OwnerStakeholder Developer
Sprint”PO’s
domain”

13. Sprint Review
13

14. “For Product Owners to succeed,
the entire organization must
respect their decisions.”
14
The Scrum Guide –November 2020
Ken Schwaberand Jeff Sutherland

15. Stakeholder Management
15
Influence
Motivationweak
strong
1
2
strong
2
3
4
5
Worker‘s council
Management
Airside Bus Driver
Supervisor
Dispatcher
Has to protect the workers
Want to reduce penalty payments
Want to have a relaxed day,
earning some bonus, lunch breaks
Afraid of conflicts with airlines
and other departments
Counting days until retirement
1
345

16. Stakeholder Management
Target Group / PersoonPossible ChallengeSolutionRegularityResponsibility
SupervisorOverstained by disruptive
change
Testing Session Every SprintScrum Master
Worker‘s councilMust represent the interest
of all employees
Introduction to our Backlog
Refinement process
OnceScrum Master
Breach of trustProaktive questions for
critical requirements
On demandScrum Team
ManagementNo timeSingle appointmentsEvery 2-3 SprintsProduct Owner
Airside Bus DriversExcessive demandTrainingsPrior to each major releaseDevelopers
No time for the review /
Shift work
Group sessions1-2 each SprintDevelopers
DispatcherSee aboveSee aboveSee aboveSee above

17. Collabortion: Design Studio
17

18. Collabortion: Design Studio
18

19. Collabortion: Design Studio
19

20. Collaboration: Job Shadowing
20

21. Collaboration: Coaching
21

22. Why Collaboration?

23. Coneway’s Law
23
Any organization that designs a system
(defined broadly) will produce a design
whose structure is a copy of the
organization's communication structure.
—Melvin E. Conway

24. Product Development with equal talking
Creating a
Vision
Finding
Product Goals
Defining
Requirements
Developing
(Software)
Promoting
Change
Testing
(after the Sprint)
Developers
Product Owner
Project Manager
Agile Coach
User
Stakeholder
SoftwareSustainable Software
Valuable and sustainable SoftwareValuable and sustainable Software,
Optimized Processes,
Acceptance

25. When to include users and stakeholders?
25
Late Majority34%
Scrum Team,
StakeholderMultiplicatorsSponsors
Stubborn usersOpen minded users
Requirement Engineering
Release-+ Sprint Planning
Stakeholder
Management,
Scrum Events
Sprint Review
Training, Coaching
Successful Rollouts
Benefits
Communication and Trainings
Early Adopters13,5%Early Majority34% 16%
SkeptikerInnovators2,5%
Basiert auf Jurgen Appelo: The Innovation Adoption Curve, “How To Change The World”
Product Owner

26. (Cultural) Change Management
26
Sprint ReviewCheck
Sprint PlanningPlan
DoDevelopment
Adapt
Scrum
Team
Product
Development
(Cultural)
Change
Management
“During the event, the Scrum Team and stakeholders review what was
accomplished in the Sprint and what has changed in their environment.”

27. Happy End
27
§Disruptive Product established
§Successful Agile Transformation
§A lot culture changed
§Everything with an empowered
young and motivated Scrum Team
§The Sprint Review was the most
important event
§(The Backlog Refinement the most
important process)

28. Back to the roots!
28
“Encouraging engineers to go out into
the field and listen to what customers
and dealers have to say.”
(The New New Product Development Game
byHirotaka Takeuchi and Ikujiro Nonaka from
the Havard Business Magazine (January
1986))

29. Additional Ressources
29
Backlog RefinementDesign Studio

30. Change is a team
sport…
Thank you!