Scrum starts with Done. The Future Present of Scrum is to start enacting Scrum.
At the Agile Tour Dublin 2016 Gunther Verheyen, seasoned Scrum practitioner, discussed the past and current challenge of Scrum of creating Done Increments, and the future challenge to start enacting Scrum.
Russian Call Girls in Karol Bagh Aasnvi ➡️ 8264348440 💋📞 Independent Escort S...
The Future Present of Scrum (Agile Tour Dublin 2016)
1. by Gunther Verheyen
Scrum. Connector, writer, speaker,
humanizer.
The Future Present of Scrum
Are we Done yet?
Agile Tour Dublin
Chartered Accountants House
6 October 2016
2. 2Gunther Verheyen – Ullizee-Inc, 2016 - @Ullizee
• Lean (software development)
• Kanban
• DevOps
• SAFe
• The Spotify model
• DAD
• eXtreme Programming
• Scrum
What definition of ‘Agile’ do you employ?
3. 3Gunther Verheyen – Ullizee-Inc, 2016 - @Ullizee
Scrum turns 21.
Two+ decades of Scrum (1995-2016):
• 70+ % of Agile teams employ Scrum
• 500.000+ people trained/certified
• 1.000+ books on Scrum
• Scrum is free for anyone to use
4. 4Gunther Verheyen – Ullizee-Inc, 2016 - @Ullizee
Is that a Gorilla I see over there?
Source: https://versionone.com/pdf/VersionOne-10th-Annual-State-of-Agile-Report.pdf
7. 7Gunther Verheyen – Ullizee-Inc, 2016 - @Ullizee
How would you rate your skills in Scrum?
None (or theory only)
Unchallenged (0-1 years experience)
Well-versed (1-5 years experience)
Mastery (5+ years experience)
9. 9Gunther 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 road ahead
10. 10Gunther 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
Humanising the workplace
(It starts and ends with people)
12. “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”
13. 13Gunther Verheyen – Ullizee-Inc, 2016 - @Ullizee
A system called ‘Scrum’.
Product
Backlog
Increment
14. 14Gunther Verheyen – Ullizee-Inc, 2016 - @Ullizee
One team delivering product.
1. A team pulls
work from one
Product
Backlog.
2. Each Sprint
delivers a
releasable
Increment of
product.
The Customer’s Experience
15. 15Gunther Verheyen – Ullizee-Inc, 2016 - @Ullizee
Multiple teams delivering product.
1. A product has
one Product
Backlog.
2. Multiple
Teams create
integrated
Increments, that
can wrap into
releases.
The Customer’s Experience
16. 16Gunther 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?
17. 17Gunther 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”?
18. 20Gunther 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?
19. 21Gunther 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
Releasable Valuable
20. “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”
21. 23Gunther 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
22. Done is where Scrum starts.
Let’s shape the future to be
about enacting Scrum.
Source: Gunther Verheyen, “The Future Present of Scrum”
23. 25Gunther Verheyen – Ullizee-Inc, 2016 - @Ullizee
Scrum provides a bounded environment for action
24. 26Gunther Verheyen – Ullizee-Inc, 2016 - @Ullizee
Your compass to truly enact Scrum.
More at “There is value in the Scrum Values” (Gunther Verheyen)
25. 27Gunther Verheyen – Ullizee-Inc, 2016 - @Ullizee
A Scrum (Software) Studio. A bounded environment.
A Scrum (Software) 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 for innovative and creative
software and people development.
26. “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
27. 29Gunther Verheyen – Ullizee-Inc, 2016 - @Ullizee
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” and “Scrum
Wegwijzer”
Mail gunther.verheyen@mac.com
Twitter @Ullizee
Blog http://guntherverheyen.com
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/
Scrum in itself is meaningless, unless employed.
The success of Scrum consists of its daily practitioners.
Combined scrum alliance and Scrum.org numbers
Amazon search on Scrum (not including rugby books)
VersionOne, the state of Agile survey.
If only 58% were combining Scrum and XP…
Let’s postpone the celebration a while.
Let’s postpone the celebration a while.
A traveller looking to get his feet back on the ground.
Start with people. Give people a purpose to self-organize against. Give people a professionally fulfilling purpose, a purpose that creates pride. Wirh Scrum that purpose is the creation of a Done version of product, in a Sprint.
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/
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.
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
Many definitions of Done focus only on development activities, where such activities in themselves hold no guarantee on high quality.
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/