TL; DR: Gold-Plating Beyond Done
There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. However, creating Product Increments that “over-deliver” in scope or quality — also known as gold-plating — with regard to the previous refinement agreement demonstrates that the Developers need to acquire a more entrepreneurial mindset and embrace their responsibility.
Join me and explore the reasons and the consequences of this Sprint anti-pattern in 109 seconds.
🗞 Shall I notify you about articles like this one? Awesome! You can sign up here for the ‘Food for Agile Thought’ newsletter and join 31,000-plus other subscribers.
🎓 Join Stefan in one of his upcoming Professional Scrum training classes!
Join more than 200 peers from May 27-29, 2021, for the Virtual Agile Camp Berlin 2021, a live virtual Barcamp using open space technology principles and practices.
The Accountability of the Developers According to the Scrum Guide
The Developers bear a mission-critical responsibility: they create the Product Increments designed to provide continuously more value to our customers. Moreover, as the Scrum Team is self-managing, the Developers decide on how they plan to do this:
Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
The specific skills needed by the Developers are often broad and will vary with the domain of work. However, the Developers are always accountable for:
- Creating a plan for the Sprint, the Sprint Backlog;
- Instilling quality by adhering to a Definition of Done;
- Adapting their plan each day toward the Sprint Goal; and,
- Holding each other accountable as professionals.
Source: Scrum Guide 2020.
Why Over-Delivering Is an Indicator for the Developers’ Lack of Professionalism
This Scrum anti-pattern is easy to spot: The Developers increase the Sprint’s scope by adding unnecessary effort to work items of Sprint Backlog, also referred to as scope-stretching or gold-plating beyond Done. Typically, this is done without prior consulting of the Product Owner.
This ignorance of previously made agreements during the refinement process may result in a questionable allocation of resources by neglecting basic business principles like considering opportunity costs.
What can you do about when faced with gold-plating? Try to address the following issues in the next Sprint Retrospective:
- Are Developers and the Product Owner talking often enough with each other, is the Product Backlog refinement process up to the job?
- Are the Developers aware that it is their responsibility to make sound investment decisions when creating Product Increments? Good enough, as in “meets the Definition of Done and the intended purpose,” is a viable approach. It does not always need to be the most elegant, best possible quality solution as long as the Increment delivers the intended value.
Probably, you also want to analyze whether decisions made in the past, for example, the design of extended software architecture, are now driving decisions. So, for example, developers might be doubling down to underline that the previous decision was correct.
Finally, as we are all humans, brace for the occasional over-excitement on the Developers’ side. Sometimes, a third and brand-new JavaScript framework is simply needed in your application. #sigh
Cannot see the form?
Please click here
Gold-Plating Beyond Done — Conclusion
If your Scrum Team strives to be successful, everyone on the team needs to develop an entrepreneurial mindset, not just the Product Owner. The Developers, in particular, are prone to oversee this necessity while at the same time making far-reaching product decisions daily. As Scrum Master and Product Owner, you need to help them fully embrace this level of accountability.
What Sprint anti-patterns have you observed? Please share them with us in the comments.
📖 Gold-Plating Beyond Done — Related Posts
21 Sprint Retrospective Anti-Patterns Impeding Scrum Teams
The Hardening Sprint Fallacy — Making Your Scrum Work #2
Three Wide-Spread Scrum Master Failures in 5:31 Minutes—Making Your Scrum Work #1
Three Wide-Spread Product Owner Failures in 6:09 Minutes—Making Your Scrum Work #5
Download the Scrum Anti-Patterns Guide for free.
📅 Scrum Training Classes, Workshops, and Events
You can secure your seat for Scrum training classes, workshops, and meetups directly by following the corresponding link in the table below:
See all upcoming classes here.
You can book your seat for the training directly by following the corresponding links to the ticket shop. If the procurement process of your organization requires a different purchasing process, please contact Berlin Product People GmbH directly.
✋ Do Not Miss Out and Learn about Sprint Anti-Patterns: Join the 12,000-plus Strong ‘Hands-on Agile’ Slack Team
I invite you to join the “Hands-on Agile” Slack team and enjoy the benefits of a fast-growing, vibrant community of agile practitioners from around the world.
If you like to join now all you have to do now is provide your credentials via this Google form, and I will sign you up. By the way, it’s free.
