Downloaded 25 times
Uploaded byGunther Verheyen
ScrumDay Germany - The Future Present of Scrum
The document discusses the evolution and challenges of Scrum in software delivery over the past two decades, highlighting its widespread adoption and the importance of defining 'done' increments in agile teams. Gunther Verheyen emphasizes the need for effective implementation of Scrum principles to improve team productivity and product quality. As Scrum continues to evolve, it challenges organizations to fully embrace its methodology for future success.
More Related Content
Similar to ScrumDay Germany - The Future Present of Scrum
ScrumDay Germany - The Future Present of Scrum
- 1. by Scrum.org –Improving the Profession of Software Delivery The Future Present of Scrum Are we Done yet? Gunther Verheyen Scrum.org Antwerp, Belgium ScrumDay Germany Stuttgart 7-8 June 2016
- 2. 2© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved Scrum turns 21. Two decades of Scrum (1995-2015): • The majority of Agile teams use Scrum • 500.000+ people trained/certified • 1.000+ books on Scrum • Scrum is free for anyone to use THANK YOU!
- 3. 3© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved Is that a Gorilla I see over there? Source: https://versionone.com/pdf/VersionOne-10th-Annual-State-of-Agile-Report.pdf
- 4. 4© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved Are we Done yet?
- 5. 5© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved MIN 1 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? How Done are we?
- 6. 6© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved Improving the profession of software delivery
- 7. 7© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved Some challenges Scrum People Ceremonies Principles and Values Technical Excellence Done Increments The power of the possible product Maximizing Scrum Scaling Scrum Studio Upstream adoption Professional Scrum Creating releasable software (every Sprint) Increasing effectiveness (over scaling dysfunctions) Scrum in the enterprise Growing Product Ownership Humanizing the workplace (It starts and ends with people)
- 8. 8© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved Help! (where should I start?)
- 9. 9© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved “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”
- 10. 10© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved Back to basics: a system called ‘Scrum’ Product Backlog Valuable Increment
- 11. 11© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved Back to basics: one team building a product 1. A team pulls work from one Product Backlog. 2. Each Sprint delivers a releasable Increment of product. The Customer’s Experience
- 12. 12© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved Multiple teams building a product: stick 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
- 13. 13© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved MIN 1 On your current or latest project, how Done were you actually: • Did you deliver an Increment? – Every Sprint? • Was it releasable? – Every Sprint? What stopped you? Does your Scrum Master know? Does management know? How Done are you?
- 14. 14© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved The definition of Done provides transparency 1. What is the state of the Increment? 2. Is the Increment releasable, i.e. “ready for release”?
- 15. 15© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved MIN 2 A. The development organization (or the Development Team if none is available from the development organization) B. The Scrum Team, in a collaborative effort where the result is the common denominator of all members’ definitions C. The Product Owner as he/she is responsible for the product’s success D. The Scrum Master as he/she is responsible for the Development Team’s productivity Who creates the definition of Done?
- 16. 16© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved A professional organization defines quality “If the definition of "done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If "done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of “done” appropriate for the product.” http://www.scrumguides.org/scrum-guide.html#artifact-transparency-done
- 17. 17© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved MIN 1 Raise your hand: Let’s hope that their definitions of “Done” reflected their distinct product qualities. Which product had the best definition of Done?
- 18. 18© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved 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
- 19. 19© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved When will your Increments be Done? Seriously. Coded Tested Integrated Deployed Managed Measured Valuable Today? Soon? Some day?
- 20. 20© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved “Done is a crucial part of Scrum, actually.” – A key pillar for empirical development – The foundation for business agility – Where a team’s fulfillment and joy start
- 21. 21© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved Scrum provides a bounded environment for action
- 22. 22© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved A Scrum Studio might be a good place to start 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.
- 23. 23© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved The future present of Scrum encompasses many challenges. What if the next 20 years were about enacting Scrum?
- 24. 24© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved About Gunther Verheyen Independent Scrum caretaker • eXtreme Programming and Scrum since 2003 • Professional Scrum Trainer • Shepherded Professional Scrum at Scrum.org • Co-developed Agility Path, Nexus and the Scaled Professional Scrum framework at Scrum.org • Author of “Scrum – A Pocket Guide (A smart travel companion)” and “Scrum Wegwijzer (Een kompas voor de bewuste reiziger)” Mail gunther.verheyen@mac.com Twitter @Ullizee Blog http://guntherverheyen.com
- 25. 25© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved 90% Agile teams use Scrum Over 53,693 Professional Scrum Masters Over 2,351 Professional Scrum Developers 150 Professional Scrum Trainers Americas, Europe, Africa, Oceania & Asia Over 47,361 Taught Over 6,916 Professional Scrum Product Owners Over 748,912 Assessments As of the end of Jan 2016
- 26. 26© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved Advance through the Professional Scrum program Free Resources Assessments Courses
- 27. 27© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved Scrum.org is a community. Connect. Twitter @scrumdotorg LinkedIn LinkedIn.com /company/Scrum.o rg Facebook Facebook.com /Scrum.org Forums Scrum.org /Community RSS Scrum.org/RSS
- 28. 28© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved “The future state of Scrum will no longer be called ‘Scrum’. What we now call Scrum will have become the norm, and organizations have re-invented themselves around it.” Source: Gunther Verheyen, “Scrum – A Pocket Guide (A Smart Travel Companion)”, 2013
- 29. 29© 1993-2016 GuntherVerheyen, Scrum.org, All Rights Reserved T H A N K Y O U
Editor's Notes
- #2 Abstract Scrum has been around since 1995, for more than two decades. Since the release of the Agile Manifesto in 2001, Scrum gradually become the most applied method for Agile software development. Depending on the source, 70-90% of all Agile teams worldwide say they use Scrum. Scrum has been a key tool for teams and organizations to deal with the increased criticality of software. The primary reason for the success is in the people using Scrum to help them manage and create software products, better. In a world where the dependence of businesses and society on software has increased even more, can we say we’re Done with Scrum? Or do we have many challenges in implementing Scrum? As complexity and unpredictability continue to increase? The key for future success is still Scrum – and we are not yet Done with Scrum. The key to employing Scrum professionally is creating Done Increments of product, where “Done” actually means “releasable in production.” This requires professional development, proper practices and standards, cross-functional collaboration, and inner-Sprint feedback loops. It might take another two decades to actually get there. In his session, Gunther Verheyen explores the system called ‘Scrum’, how it has helped, and how it can continue to help through its core purpose, the creation of Done product in a Sprint, or less. Gunther is a longtime Scrum professional. Having worked with Scrum.org, shepherding the group’s Professional series and leading its European operations, Gunther is now an independent Scrum caretaker. Read https://guntherverheyen.com/2016/05/26/the-future-present-of-scrum/
- #3 Scrum in itself is meaningless, unless employed. The success of Scrum is the daily practitioners. Combined scrum alliance and Scrum.org numbers Amazon search on Scrum (not including rugby books)
- #4 VersionOne, the state of Agile survey. If only 58% were combining Scrum and XP…
- #5 Let’s postpone the celebration a while.
- #10 Read: https://guntherverheyen.com/2012/05/02/the-importance-of-done-in-scrum/ https://guntherverheyen.com/2015/05/14/done-is-a-crucial-part-of-scrum-actually/
- #14 https://guntherverheyen.com/2015/05/05/branching-done/
- #16 The development organization (or Development Team if none is available from the development organization) The Scrum Team, in a collaborative effort where the result is the common denominator of all members’ definitions The Product Owner as he/she is responsible for the product’s success The Scrum Master as he/she is responsible for the Development Team’s productivity Feedback Scrum.org: If the definition of “Done" is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. The Development Team of the Scrum Team can complement it with elements specific for the product or context. If “Done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of "done" appropriate for the product. A professional organization defines quality. ‘Quality’ is ideally seen as product qualities.
- #17 What the Scrum Guide says: “If the definition of "done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If "done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of “done” appropriate for the product.” http://www.scrumguides.org/scrum-guide.html#artifact-transparency-done
- #18 https://guntherverheyen.com/2015/08/04/a-professional-organization-defines-quality/
- #19 Many definitions of Done focus only on development activities, where such activities in themselves hold no guarantee on high quality.
- #20 Done is a great proxy for the state of our craft, for many organizations this is a hope not a reality. And that the state is not as great as we would think it should be…
- #25 About Gunther Verheyen Gunther Verheyen (gunther.verheyen@mac.com) is a longtime Scrum practitioner. After a career as a consultant, in 2013 he started shepherding the Professional series of Scrum.org, while also leading its European operations. Gunther left Scrum.org in 2016 to further his path as an independent Scrum caretaker. Gunther ventured into IT and software development after graduating in 1992. His Agile journey started with eXtreme Programming and Scrum in 2003. Years of dedication followed, of using Scrum in diverse circumstances. As from 2010 Gunther became the inspiring force behind some large-scale enterprise transformations. Gunther left consulting in 2013 to partner with Ken Schwaber, Scrum co-creator, at Scrum.org. He is Professional Scrum Trainer, shepherded the ‘Professional Scrum’ series, worked with Scrum.org’s global network of Professional Scrum Trainers, and is co-creator to Agility Path and the Nexus framework for Scaled Professional Scrum. Gunther left Scrum.org in 2016 to continue his journey of Scrum as an independent Scrum caretaker. In 2013 Gunther published the acclaimed book “Scrum – A Pocket Guide (a smart travel companion)”. Ken Schwaber recommends his book as ‘the best description of Scrum currently available’ and ‘an extraordinarily competent book’. In 2016 the Dutch translation of his book was published as “Scrum Wegwijzer (Een kompas voor de bewuste reiziger)”. When not travelling for Scrum and professionalism, Gunther lives and works in Antwerp (Belgium). You will know how to contact him for a potentially fruitful collaboration. Contact Gunther at Gunther.verheyen@mac.com. Find Gunther on LinkedIn at https://www.linkedin.com/in/ullizee, on Twitter as https://twitter.com/ullizee or read more of his musings on Scrum on his blog, https://guntherverheyen.com/tag/scrum/. More? About: https://guntherverheyen.com/about/ Testimonials: https://guntherverheyen.com/testimonials/ Meet Gunther at an event: https://guntherverheyen.com/events/ Join Gunther in a class: https://guntherverheyen.com/courses/
- #26 DW 90% - Forrester research data https://www.forrester.com/How+Can+You+Scale+Your+Agile+Adoption/fulltext/-/E-res110444#AST962998 2013