TL; DR: Jira Anti-Patterns
If you ask people to come up with popular attributes for “Agile” or “agility,” Scrum and Jira will likely be among the top ten featured. Moreover, in any discussion about the topic, someone will mention that using Scrum running on top of Jira does not make an organization agile. However, more importantly, this notion is often only a tiny step from identifying Jira as a potential impediment to outright vilifying it. So in March 2023, I embarked on a non-representative research exercise to learn how organizations misuse Jira from a team perspective as I wanted to understand Jira anti-patterns.
Read on and learn more about how a project management tool that is reasonably usable when you use it out of the box without any modifications turns into a bureaucratic nightmare, what the reasons for this might be, and what we can do about it.
TL; DR: Red or Blue?
I need your support, dear community. For months, I have been working on turning the popular Scrum Anti-Patterns Guide PDF into a new book from Scrum-org’s Professional Scrum Series, published by Pearson. We will soon start the editing process, and I am hopeful we may see a release date in Q2/2023.
Creating the graphics has been challenging at times; there will be more than 50 cartoons and sketches in the book. However, it has also been gratifying to rethink some of the old cartoons and, generally, improve their quality.
There is one challenge, though, I like to ask for your support: which cover shall it be — red or blue?
TL; DR: Agile Micromanagement
There are plenty of failure possibilities with Scrum. Indeed, given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. For example, the Scrum Guide clearly states the importance of self-management at the Scrum team level. Nevertheless, the prevailing cause of many messed-up attempts to use Scrum result from what I call agile micromanagement, a pseudo-commitment to agile principles only to be overridden whenever it seems beneficial from a stakeholder’s or manager’s perspective.
Join me and delve into the importance of self-managing Scrum teams in less than two minutes.
TL; DR: No Sprint Goal
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. For example, what if there is no Sprint Goal — Sprint after Sprint? What if the Scrum team is always only working on a random assortment of work items that seem to be the most pressing at the moment of the Sprint Planning?
Join me and delve into the importance of the Sprint Goal for meaningful work as a Scrum team in less than two minutes.
TL; DR: Prisoners of Retrospectives
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. What if, for example, not all of your Scrum team’s members feel enthusiastic about the Sprint Retrospective, the critical event when the Scrum team inspects itself? How can you help them become dedicated supporters instead? Join me and delve into how to avoid teammates feeling like prisoners of Retrospectives in less than two minutes.
TL; DR: Scrum Developer Anti-Patterns
After covering the anti-patterns of the Scrum Master, the Product Owner, and the stakeholders, this article addresses Scrum Developer anti-patterns, covering all Scrum Events and the Product Backlog artifact. Continue reading and learn more about what to look out for if you want to support your teammates who build the Increment.