Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Scrum Day Europe 2016 - The Future Present of Scrum


Published on

Scrum is the most applied method for Agile software development. Depending on the source, 70-90% of all Agile teams worldwide say they use Scrum. The primary reason for the success is in the people using Scrum to help them manage and create software products, better.

Can we say we’re Done with Scrum? Or do we have many challenges in implementing Scrum?

The key to employing Scrum professionally is creating Done Increments of product, where “Done” actually means “releasable in production.” It might take another two decades to actually get there.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Scrum Day Europe 2016 - The Future Present of Scrum

  1. 1. by Gunther Verheyen Scrum. Connector, writer, speaker, humanizer. The Future Present of Scrum Are we Done yet? Scrum Day Europe V Amsterdam, Netherlands 7 July 2016
  2. 2. Houston?SDE turns 5. Scrum turns 21. Thank YOU
  3. 3. 3Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee Is that a Gorilla I see over there? Source:
  4. 4. Is the journey over? Are we Done yet?
  5. 5. 5Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee What is the #1 challenge of your team, department or organization moving forward with Scrum? What is stopping you? Does your Scrum Master know? Does management know? Looking at the journey ahead
  6. 6. 6Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee The future is unwritten. Our journey faces many challenges. Enacting Scrum People Ceremonies Principles and Values Technical Excellence Done Increments The power of the possible product Maximize Scrum Scaled Scrum Scrum Studio Upstream adoption Professional Scrum Creating releasable software (every Sprint) Increasing effectiveness (not dysfunctions) Scrum in the enterprise Growing Product Ownership Humanizing the workplace (It starts and ends with people)
  7. 7. Houston?
  8. 8. “If Scrum was to be reduced to one purpose, and one purpose only, that is the creation of a Done Increment in a Sprint.” Source: Gunther Verheyen, “Done is a crucial part of Scrum, actually”
  9. 9. 9Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee A system called ‘Scrum’, the path we travel. Product Backlog Valuable Increment
  10. 10. 10Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee One team delivering product (the basics) 1. A team pulls work from one Product Backlog. 2. Each Sprint delivers a releasable Increment of product. The Customer’s Experience
  11. 11. 11Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee Multiple teams delivering product (sticking with the basics) 1. A product has one Product Backlog. 2. Multiple Teams create integrated Increments, that can wrap into releases. The Customer’s Experience
  12. 12. 12Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee On your current or latest project: • Did you deliver an Increment? –Every Sprint? • Was it releasable? –Every Sprint? What is stopping you? Does your Scrum Master know? Does management know? How Done are you?
  13. 13. 13Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee The definition of Done provides transparency 1. What is the state of the Increment? 2. Is the Increment releasable, i.e. “ready for release”?
  14. 14. 14Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee Raise your hand: They might have been produced in similar environments, using similar techniques. Their definitions of “Done” likely reflected very different product qualities. Which product had the best definition of Done?
  15. 15. 15Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee Development Standards Product Qualities What are you defining as “Done”? • Pair programming • (A)TDD • Refactoring • User acceptance testing • Continuous Integration – Unit, deployment, build, integration, regression tests • Performance testing • Clean Code base • Valuable functionality only • Architectural conventions respected • According to design/style/usability guide • Documented • Service levels guaranteed
  16. 16. “Done is a crucial part of Scrum, actually.” – Key for empirical product delivery – Foundational for business agility – The purpose for product people Source: Gunther Verheyen, “Done is a crucial part of Scrum, actually”
  17. 17. 17Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee What Done requires • Committed, focused, engaged people • Team effectiveness through collaboration, autonomy & self- organization • Skills (training) • Engineering practices & standards • Infrastructure, tooling & automation • Quality standards & guidelines • Removal of Impediments • Elimination of low value
  18. 18. 18Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee A Scrum Studio. Your flight control center. A Scrum Studio is a contained, yet integrated, part of the organization where software development fully employs Scrum • A physical or a virtual area • Value over utilization • Stable product teams • Tooling and infrastructure • Facilities and resources A center of innovative and creative software and people development.
  19. 19. 19Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee Enacting Scrum. Your compass. People Commitment Focus OpennessRespect Courage
  20. 20. 20Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee Scrum provides a bounded environment to get going What is stopping you? • Does your Scrum Master know? • Does management know?
  21. 21. Scrum starts with Done. Let the next 20 years be about enacting Scrum. Source: Gunther Verheyen, “The Future Present of Scrum”
  22. 22. 22Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee About Gunther Verheyen Independent Scrum caretaker • eXtreme Programming and Scrum since 2003 • Professional Scrum Trainer • Shepherded Professional Scrum at • Co-developed Agility Path, Nexus and the Scaled Professional Scrum framework at • Author of “Scrum – A Pocket Guide” and “Scrum Wegwijzer” Mail Twitter @Ullizee Blog
  23. 23. 23Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee S A F E T R A V E L S
  24. 24. 24Gunther Verheyen – Ullizee-Inc, 2016 @Ullizee Scrum Guide Update 2016 “When the values of commitment, courage, focus, openness and respect are embodied and lived by the Scrum Team, the Scrum pillars of transparency, inspection, and adaptation come to life. The Scrum Team members learn and explore those values as they work with the Scrum events, roles and artifacts. Successful use of Scrum depends on people becoming more proficient in living these five values. People personally commit to achieving the goals of the Scrum Team. The Scrum Team members have courage to do the right thing and work on tough problems. Everyone focuses on the work of the Sprint and the goals of the Scrum Team. The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work. Scrum Team members respect each other to be capable, independent people.” More at “There is value in the Scrum Values” (Gunther Verheyen)