TL; DR: Scrum Team Failure
This post on Scrum team failure addresses three categories from the Scrum anti-patterns taxonomy that are closely aligned: Planning and process breakdown, conflict avoidance and miscommunication, and inattention to quality and commitment, often resulting in a Scrum team performing significantly below its potential.
Learn how these Scrum anti-patterns categories manifest themselves and how they affect value creation for customers and the organization’s long-term sustainability.
This is the third of three articles analyzing the 183 anti-patterns from the upcoming Scrum Anti-Patterns Guide book. The other two articles, see below, address adhering to legacy systems, processes, practices, and communication and collaboration issues.
TL; DR: Product Discovery for Scrum Teams
While Scrum excels at building and releasing Increments, it does not guarantee that those are valuable—garbage in, garbage out. Scrum teams can equally make things no one is interested in using at all. The critical artifact to create value is the Product Backlog, “an emergent, ordered list of what is needed to improve the product.” (Source.) However, Scrum does not elaborate on how the Product Owner identifies Product Backlog-worthy work items. That would be the job of the process that feeds into the Product Backlog: product discovery.
Learn more about which frameworks have proven useful to augment Scrum with product discovery practices.
TL; DR: Health Checks for Agile Teams
Agile teams thrive on continuous improvement and adaptability. Self-assessment isn’t just a health check measuring tool but a compass guiding teams toward their potential. It enables teams to understand their strengths, identify areas of improvement, and delve deeper into work dynamics beyond mere output.
The true essence of self-assessment in Agile is fostering transparency, collaboration, and relentless improvement. It’s not an audit; it’s a mirror reflecting a better version of your Agile team.
This article comprises a few well-known self-assessment tools; use them or have them inspire you to create your own assessment.
TL; DR: Creating a Personal Readme for Scrum Masters with ChatGPT
Providing a personal readme to your new teammates and stakeholders as a Scrum Master is a great way to build trust and rapport while managing expectations at the same time. I do so regularly and having a template for that purpose comes in handy.
Therefore, I thought it also might be an excellent exercise to test ChatGPT on more practical aspects of a Scrum Master’s work. So please follow the complete path to having ChatGPT create a decent personal readme template for Scrum Masters—which took me less than 20 minutes.
TL; DR: Maximizing Utilization as a Relic from the Industrial Management Past
There are plenty of failure possibilities with Scrum. Since Scrum is an intentionally incomplete framework with a reasonable yet short “manual,” this effect should not surprise anyone. For example, what if the focus of the organization is on the maximizing utilization of the “workers” of the Scrum teams? What if the organization is still stuck deeply in industrial paradigm thinking, ignoring the benefits of slack time for the creation of value in the field of knowledge work?
Join me and delve into the effects of this outdated management principle in 60 seconds.
TL; DR: Unsmart Improvements
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. One area that typically flies under the radar is improvements. While the Scrum Guide encourages addressing the most impactful ones as soon as possible, it is up to the Scrum team to figure out how to improve. One manifestation of this core team task we often encounter is picking unsmart improvements, though.
Join me and delve into the consequences of picking unsmart improvements as a Scrum Team in less than 90 seconds.