NYC Scrum User Group Back to Basics: the Sprint Review

1. Emilie Franchomme
NYC
Scrum User Group

2. Intro: 2 truths, 1 lie
I’ve never been involved in Waterfall projects
I’ve been Product Owner, Scrum Master and Agile Coach
I previously gave this presentation at a few Agile
conferences

3. Intro: 2 truths, 1 lie
I’ve never been involved in Waterfall projects
I’ve been Product Owner, Scrum Master and Agile Coach
I previously gave this presentation at a few Agile
conferences
emilie.franchomme@gmail.com
@EFranchomme

4. Preamble

5. Sprint Review defined
Scrum Guide - Ken Schwaber & Jeff Sutherland (July 2013)
A Sprint Review is held at the end of the Sprint to inspect the
Increment and adapt the Product Backlog if needed.
During the Sprint Review, the Scrum Team and stakeholders
collaborate about what was done in the Sprint.
Based on that and any changes to the Product Backlog during the
Sprint, attendees collaborate on the next things that could be done
to optimize value.
This is an informal meeting, not a status meeting, and the
presentation of the Increment is intended to elicit feedback
and foster collaboration.

6. Oversight…
Or so obvious?

7. Back to definitions
Review: A formal assessment or examination
of something with the possibility or intention
of instituting change if necessary
(from obsolete French revue, from revoir ‘see
again’)
Demonstration: The action or process of
showing the existence or truth of something
by giving proof or evidence

8. Synecdoche
The Sprint Review
is much more
than a Demo

9. An informal definition
« The Demo is a
multi-faceted diamond »
Oana Juncu

10. Preparation
Murphy’s law: « Anything that can go wrong, will go wrong »
There are glitches...
(respondant PO) [...] Demo day: the User Story is
broken. All hands on deck! The User
Story will be fixed within 5 minutes
of the beginning of the
demonstration. (respondant SM)
I forgot to send the invites!!!
(respondant PO)
The demo must be prepared to be efficient (respondant Coach)

11. Storytelling
• Sprint
• User Stories

12. Show
• The team can only
show what is done
• Showing forces the
team to complete

13. Validation?
Approved Rejected

14. Feedback

15. Alignment

16. Celebrate

17. Reflect
(c) Brendan Wixted

18. One does not simply have a Demo!
Thank you for your attention

19. A quick feedback: your ROTI (Return On time Invested)

20. One does not simply have a Demo!
Questions?
Emilie Franchomme
emilie.franchomme@gmail.com
@EFranchomme

22. Picture credits
• One does not simple have a Demo: One does not simply (meme) via https://imgflip.com/
• Intro: 2 truths, 1 lie: video from Agile Tour Bordeaux https://www.youtube.com/watch?v=yuAa_fozTmc
• Preamble: Scrum framework by Kenny Rubin http://www.innolution.com/resources/visual-agilexicon
• Oversight? : http://www.versionone.com/pdf/2013-state-of-agile-survey.pdf
• An informal definition (Attribution Licence CC) : bluediamond_2 by Michelle Tribe Greeencolander
http://www.flickr.com/photos/greencolander/1863112308/in/photostream/
• Storytelling: Once upon a time, by Kenneth Whitley
http://commons.wikimedia.org/wiki/File%3AOnce_upon_a_time%2C_WPA_poster%2C_ca._1938.jpg
• Show: Mädchen mit Teller, painting by Carl von Bergen
http://commons.wikimedia.org/wiki/File%3ACarl_von_Bergen_M%C3%A4dchen_mit_Teller.jpg
• Validation?: via http://www.agent-de-joueur-foot.fr/wp-content/uploads/2013/11/Carton-rouge.jpg
• Feedback : A typical wooden boomerang, by Adrian Barnett
http://en.wikipedia.org/wiki/Image:Boomerang.jpg
• Alignment : Compass on a boat, by Rama
http://commons.wikimedia.org/wiki/File%3ACompass_mg_5961.jpg
• Celebrate: Success kid (meme) via https://imgflip.com/
• Reflect: Photo from a serie about framing composition of landscapes in a mirror, by Brendan Wixted
http://www.flickr.com/photos/brendanwixted/7190127336/in/photostream

23. References
About the Sprint Review (English):
• Scrum Guide by Ken Schwaber & Jeff Sutherland (July 2013):
https://www.scrum.org/Portals/0/Documents/Scrum%20Guides/2013/Scrum-Guide.pdf
• Scrum from the trenches de Henrik Kniberg (2007):
http://www.crisp.se/henrik.kniberg/ScrumAndXpFromTheTrenches.pdf
• Richard Lawrence’s blog: http://www.richardlawrence.info/2009/04/24/how-to-give-a-great-sprint-demo/
• Hing Chan’s blog: http://hingchanscrum.blogspot.com/2012/01/mes-deux-cents-importance-de-la.html
• Agile DZone, article by Patroklos Papapetrou: http://agile.dzone.com/announcements/agile-dummies-continuous
• Martin Harris’s blog: http://martinaharris.com/2010/01/dancing-to-the-tune-of-the-scrum-demo/
• Agile Software Development, article by Peter Stevens: http://agilesoftwaredevelopment.com/blog/peterstev/simple-scrum-
sprint-review
• Scrum Alliance, articles by Bob Schatz:
o http://www.scrumalliance.org/articles/48-successful-sprint-reviews
o http://www.scrumalliance.org/articles/124-the-sprint-review-mastering-the-art-of-feedback
• Toolbox, article by Bryan Campbell: http://it.toolbox.com/blogs/agile-pm/whats-in-a-demo-29494
• Ilan Goldstein’s blog: http://www.scrumshortcuts.com/blog/retrospectives-reviews/to-dos-for-your-sprint-reviews/
• Sandy Mamoli’s blog:http://www.nomad8.com/files/sprint_review_show_and_tell.php
• Charles Bradley’s blog:
o http://www.scrumcrazy.com/Tips+for+a+Good+Sprint+Review
o http://www.scrumcrazy.com/Executive+Summary+-+The+Sprint+Review
o http://www.scrumcrazy.com/Worst+Practice+-+The+Sprint+Review+as+a+Signoff+Meeting
• InformIT, article by Kenneth S. Rubin: http://www.informit.com/articles/article.aspx?p=1928232&seqNum=4
• InfoQueue, article by Robert Galen: http://www.infoq.com/articles/agile-project-manager-viola
• Stephanie Stewart’s blog: http://iamagile.com/2012/06/13/our-evolution-of-sprint-reviews/
• Roman Pichler’s blog: http://www.romanpichler.com/blog/agile-product-innovation/the-scrum-cycle/

24. References
About feedback:
• Keep your cool when getting feedback: http://hbr.org/tip?date=041812
• How to get feedback where you’re the boss: http://blogs.hbr.org/hmu/2012/05/how-to-get-feedback-when-youre.
html
• Agile Feedback loops: http://www.infoq.com/news/2011/03/agile-feedback-loops
• Presentation “Tightening the feedback loop” by Patrick Kua (Agile 2011):
http://www.slideshare.net/thekua/tightening-the-feedback-loop-agile-2011
• Presentation “Feedback loops in agile development” by Jamie Allsop:
http://www.slideshare.net/AgileOnTheBeach/feedback-loops-in-agile-development
• Bob Marshall’s blog: http://flowchainsensei.wordpress.com/2012/09/26/how-to-give-feedback/
• Yves Hanoulle’s blog : http://www.hanoulle.be/2010/07/perfection-game/
About Definition of Ready:
• Ken Power’s blog: http://systemagility.com/2011/05/17/definition-of-ready/
• D. André Dhont’s blog: http://dhondtsayitsagile.blogspot.fr/2012/09/definition-of-ready.html
About Scrum/Kanban:
• Stories about practising Scrum and Kanban for 50 months: http://www.targetprocess.com/articles/agile50months/
• David J. Bland’s blog (velocity): http://www.scrumology.net/2011/04/20/no-points-for-you-come-back-1-sprint/
• Alan Dayley’s blog (velocity): http://www.dayleyagile.com/2012/01/velocity-moves-forward/

25. References
In French:
• Scrum Guide de Ken Schwaber & Jeff Sutherland (juillet 2011 - revue de sprint page 13):
http://www.scrum.org/storage/scrumguides/Scrum%20Guide%20-%20FR.pdf#view=fit
• Scrum from the trenches de Henrik Kniberg (2007 - démos page 77):
http://www.infoq.com/resource/news/2007/06/scrum-xp-book/
en/resources/ScrumAndXpFromTheTrenches_French.pdf
• Kanban et Scrum, tirer le meilleur des deux de Henrik Kniberg et Mattias Skarin (2010 - fin de sprint page 15):
http://www.infoq.com/resource/news/2010/01/kanban-scrum-minibook/en/resources/KanbanAndScrum-French.pdf
• Livre de Claude Aubry : “Scrum, le guide pratique de la méthode agile la plus populaire” (éditions Dunod, 2ème
édition septembre 2011) - Chapitre 9 “La revue de sprint”: http://www.aubryconseil.com/pages/Livre-Scrum
• Blog de Claude Aubry:
o Généralités: http://www.aubryconseil.com/post/2007/11/25/336-la-revue-de-sprint
o Observations en tant que PO: http://www.aubryconseil.com/post/2007/01/27/166-la-demonstration-lors-de-la-revue-
de-sprint
• Blog de Fabrice Aimetti: http://www.fabrice-aimetti.fr/dotclear/index.php?post/2010/09/01/Arretez-d-appeler-demonstration-
votre-revue-de-sprint
• Blog de Cyrille Deruel: http://www.bouzin-agile.fr/?post/2010/05/10/La-d%C3%A9monstration-%3A-le-tour-de-magie-
de-l-Agilit%C3%A9
http://www.bouzin-agile.fr/?post/2012/08/26/Evitez-l-effet-gruyere-dans-vos-projets-Agiles
• Blog d’Alexandre Boutin: http://www.agilex.fr/2009/08/un-piege-de-la-demo/
• Blog d’Octo:
o Article d’Eric Gentilini: http://blog.octo.com/ne-craignez-plus-leffet-demo/
o Check list: http://blog.octo.com/wp-content/uploads/2011/05/Checklist-avant-demo.pdf
• Présentation “Scrum master Academy” de Gilles Mantel et Jean-Laurent Fabre de Motlhon au ScrumDay 27/03/2012
(règle 30 slide 15 et règle 41 slide 18): http://www.scrumday.fr/?presentation=scrum-master-academy
• Blog de Christophe Addinquy: http://freethinker.addinq.uy/post/58542893843/en-finir-avec-la-demo
• Blog de Jean-claude Grosjean:
o http://www.qualitystreet.fr/2010/06/26/alerte-agile-n%C2%B08-pour-le-feedback-on-a-la-demo
o http://www.qualitystreet.fr/2010/08/06/truc-de-coach-un-plan-de-bataille-pour-une-demo-efficace/
o http://www.qualitystreet.fr/2014/09/08/truc-de-coach-1-2-3-demo-notre-protocole-demo /

26. Online survey results
Words & Sentences about the Demo

27. What does the community say?
Your demos, how are they?
8 %
92 %
8 %
They happen at the end of each sprint
Yes
No

28. What does the community say?
Your demos, how are they?
Feedback is given during the demo
85 %
15 %
Yes
No

29. What does the community say?
44 %
Your demos, how are they?
There are slides
56 %
Yes
No

30. What does the community say?
54 %
44 %
Your demos, how are they?
The sprint burndown/burnup chart is shown
Yes
No

31. What does the community say?
Your demos, how are they?
The product release burndown/burnup chart is shown
71 %
Yes
23 %
No

32. What does the community say?
Who’s attending the demo?
98 %
96 %
48 %
35 %
63 %
Dev team members
Product Owner
Sponsor(s)
Users
Other people

33. What does the community say?
The demo, with 1 word, by the practioners

34. What does the community say?
Who are you?
What’s your role in the project?
15 %
42 %
25 %
2 %
2 %
15 %
Product Owner
Scrum Master
Other Scrum Team
member
Sponsor
User
Other

35. What does the community say?
Who are you?
Your project is developed internally/with an external company?
83 %
17 %
internally
with an external company

36. What does the community say?
The demo, with 1 word, by those who
accompany the teams (coaches)

37. What does the community say?
The demo, with 1 sentence
"The demo allows the team to ensure that the
work delivers value to users; feedback given by
the audience guide future developments to
deliver maximum value at the end of the project."
"The demo done collectively by
the team to the Product Owner
(or customer) is the key
element of the Sprint Review."
"The art of gaining trust
and get rapid feedback."
"An event carefully prepared and immediately debriefed, WITHOUT SLIDE :)"
"In Scrum, there is no demo. There is the presentation of the result
of the Sprint and the Inspect-and-Adapt by the project members."
"Feedback and
self-regulation."
"Win/win sharing time: while guests discover
concretely the progress of the product, the
team’s work is valued and the team gets useful
feedback to continue the development."
"Awesome? It's very nice but you
know, we just did our job :-) ...
(Yay!!)"

38. What does the community say?
The demo, with 1 sentence
"The demo is a multi-faceted diamond; the demonstration is an
opportunity for all stakeholders (Product Owner, Users, Dev
team...) to get and consolidate user experience on the
application being built (+ important aspects of checking, quick
feedback loop, validation)"
"Validation of what has been
done, and not a demo."
"Realistically measure and adjust the
convergence of vision and implementation."
"The demo is the first vector of feedback, it is an
essential tool to ensure that the product meets
the needs and is a quality product!"
"This is the time for the team to get
feedback on the application it builds,
to make sure it understands the
stakes of the application, and finally
to understand the meaning of his
involvement."
"The demo must be
prepared to be efficient."
"Involving users in their product."
"Invite people in a meeting and show them the product, the only real indicator of the progress
of the project."

39. What does the community say?
The demo, with 1 sentence
"The demo is when the pride of the
developer who shows what the team
has done meets the curiosity of the
customer, thus creating the ground of
common knowledge on which the
different possibilities for the future of
this feature or product will be settled."
"This is the time when the reunification of the
team is the strongest (in the sense that if the
PO challenges the team during the sprint or
sprint planning, during the review everyone
form one body with each other). It is also the
place for feedback: openness to others."
"Check that the product under development is still
aligned with the vision of the product, even if it
means adjusting the vision given the volatility of
the situation."
"Be proud of one’s work"
"The team is proud to show its product and is willing to
embrace change, to improve the product."
"Adapt to the audience"
"Having demos is great in Agile, but it's
also a convenient façade not to
question the minimal product and to
advance the release date."