TL; DR: Overcoming Common Product Backlog Management Traps w/ David Pereira
How teams manage their Product Backlog often makes or breaks their value creation chances. Poor backlog management leads to a feature factory trap, while a mindful strategy enables the team to drive value steadily. During the 54th Hands-on Agile meetup, David Pereira shared tried and tested practices to avoid the feature factory fate.
Ideally, a metric is a leading indicator for a pattern change, allowing your Scrum team to analyze the cause in time and take countermeasures. However, what if you picked the wrong metrics? What if these useless agile metrics lead you in the wrong direction while providing you with the illusion that you know where your team is heading?
Learn more about useless agile metrics, from individual velocity to estimation accuracy to utilization rates.
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.
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.
Learn how individual incentives and outdated organizational structures — fostering personal agendas and local optimization efforts — manifest themselves in Scrum stakeholder anti-patterns that easily impede any agile transformation to a product-led organization.
TL; DR: How to Sabotage A Product Owner — 53 Anti-Patterns from the Trenches to Avoid
One of my favorite exercises from my Professional Scrum Product Owner classes is how to best sabotage a Product Owner as a member of the middle management. The exercise rules are simple: You’re not allowed to use any form of illegal activity. So, outsourcing the task to a bunch of outlaws is out of the question. Instead, you are only allowed to use practices that are culturally acceptable within your organization.
Read on and learn more on how to best sabotage a Product Owner from the exercise results of more than twenty PSPO classes. (I edited the suggestions for better readability.)
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
3rd Party Cookies
This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, and the most popular pages.
Keeping this cookie enabled helps us to improve our website.
Please enable Strictly Necessary Cookies first so that we can save your preferences!
