When developing a product, it’s natural to focus on delivering value as efficiently as possible. But have you ever wondered what additional value you could be achieving but haven’t yet? How do you uncover those hidden opportunities to take your product to the next level? That’s where Evidence-Based Management (EBM) comes into play.
Organizations often struggle to address the root causes of inefficiencies, particularly when adopting Agile practices. Instead of tackling the core issues within their systems, they focus on surface-level problems. This blog post will explore these systemic issues and provide insights on how to make meaningful changes that lead to greater effectiveness and agility.
In today’s fast-paced world, organizations must understand their value to make informed decisions and drive continuous improvement. But how do you know the value that’s currently being delivered in your organization? 🤔 This is where Evidence-Based Management (EBM) comes into play, offering a clear path to evaluate and enhance your organizational outcomes. In this blog post, we’ll explore how EBM can help you gauge your organization’s value, optimize performance, and make data-driven decisions.
In the ever-evolving world of business, staying ahead means adapting faster than your competitors. Being agile is not about following a set of rules but rather embracing a mindset of constant questioning and improvement. As Steve Denning wisely said:
In today’s fast-paced, ever-evolving business world, it’s not enough to simply make changes and hope for the best. We need to understand the true impact of our actions—whether they’re improving or hindering our overall success. This is where evidence-based management comes into play. If you’re working in an Agile environment, it’s essential to have the right tools in place to measure success and progress effectively.
There’s a quote from Ken Schwaber, one of the co-creators of Scrum, that goes:
Agile transformations are often heralded as the magical solution to organizational dysfunction, promising faster delivery, happier teams, and better outcomes. However, there’s a quote that resonates deeply with many Agile professionals: “There’s no such thing as an Agile transformation, it’s a cultural transformation.”
As Lao Tzu wisely said, “If you do not change direction, you may end up where you are heading.” This quote resonates deeply with me, both as a professional Scrum trainer and a practitioner. Whether you’re a developer writing code or an organization strategizing for the future, it’s vital to continuously ask yourself: Are we heading in the right direction? 🛤️
In today’s fast-paced world, both individuals and businesses must constantly adapt to their surroundings. Whether it’s a shift in the market, unforeseen circumstances, or technological advancements, those who thrive are the ones who can effectively readjust to the changes around them.
#shorts #shortsvideo #shortvideo Martin Hinshelwood walks us through the 5 #agile bandits. This video features a toxic #productowner
In Agile, there’s a common misconception that leads to what I like to call “Agile Banditry.” Product Owners, when misguided, can fall into the trap of treating their role as a project manager, dictating every step of the team’s progress like an overbearing taskmaster. This often leads to disengagement, frustration, and ultimately, a failed product. In this blog, we’ll explore the dangers of Agile Banditry and how Product Owners can avoid this trap, enabling their teams to thrive.
Agile teams often use burndown charts to track progress throughout a sprint. It seems like a solid approach—after all, it’s a visual indicator of how much work remains. But let me be clear: burndowns are Agile banditry! In fact, relying too heavily on burndowns could lead your team down a treacherous path of excessive upfront planning and false security. Let’s explore why burndowns aren’t the hero of Agile, and how embracing a continuous flow mindset can lead to real value.
The Agile Illusion: Unmasking the Burndown Trap in Sprint Planning - Discover why traditional burndown charts might be misleading your Agile process. Join us as we explore more effective ways to plan and execute sprints.
#shorts #shortvideo #shortsvideo Martin Hinshelwood walks us through the 5 agile bandits. This video features #storypoints
Introduction to Agile Metrics: The Pitfall of Story Points and Velocity
#shorts #shortvideo #shortsvideo Martin Hinshelwood walks us through the 5 #agile bandits. This video features ‘say-do’ metrics.
In Agile environments, there’s often a temptation to rely on metrics that seem to offer clarity and control over a project’s progress. One such metric is the “say-do” metric, which measures what a team says they will do versus what they actually accomplish. While this may appear useful on the surface, it’s often a slippery slope that leads to vanity metrics, reduced psychological safety, and, ultimately, a focus on outputs rather than outcomes.
#shorts #shortvideo #shortsvideo Martin Hinshelwood walks us through the 5 kinds of #agile bandits. This video features #specialsprints
You can’t spend much time in the Agile space without encountering teams doing some kind of special sprints. Whether it’s Sprint Zero, refactoring sprints, bug-fix sprints, or hardening sprints, these so-called “special sprints” are quite common. However, let’s cut to the chase: special sprints are agile banditry, and those practicing them are bandits in disguise. Here’s why they dilute your team’s ability to deliver usable, working products, and how you can avoid falling into the same trap.
In the world of Agile, we often hear about the famous “three questions” used during the daily Scrum or retrospective sessions:
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.
CR2