Many Scrum Teams still use velocity, but often in ways that create false certainty. This post explores how combining velocity with uncertainty can lead to better forecasting, greater transparency, and more meaningful conversations about value and risk.

Velocity is one of the most misunderstood ideas in Agile teams. This post explains what it really is. A result, not a target. Something to notice, not something to hit. We break down how velocity often gets misused, share a travel analogy that makes it real, and show how teams can use it to have better conversations. This is not about speed or precision. It is about mindset. And it is a first step toward more honest, value focused planning.

Agile estimation often feels broken. But maybe it is not the technique, it is the thinking behind it. This blog challenges common misconceptions like “you must use story points” and explores why estimation should support learning and decision-making. Through a simple card experiment and the Cone of Uncertainty, it reframes estimation as a conversation about value, not just effort.

Can AI generate high-quality code that is extensible, maintainable, and scalable? This experiment was a simple test to first evaluate the quality of AI-generated code for a basic kata against technical excellence principles—assessing its structure, modularity, and maintainability. Next, AI was prompted to apply a Test-Driven Development (TDD) approach to see if it could improve the quality with a software craftsmanship mindset and principles. The findings were insightful, revealing interesting patterns in how AI approaches structure, testing, and iterative development.

Negativity doesn’t just dampen morale -it can derail team performance entirely. This blog dives into the Bad Apple Effect, showing how just one negative individual can impact collaboration, productivity, and development in sports, business, and Agile teams. Ready to address negativity and build high-performing, adaptable teams? Explore how to tackle toxic behaviours and foster a culture of continuous improvement. Dive in to learn more!

Agile often fails not because it's flawed, but because organisations focus on quick results instead of embracing the mindset shift it demands. This blog explores how the rush for success leads companies to miss Agile's core values -adaptability and value-driven decision-making - resulting in frustration. Ready to move beyond surface-level Agile practices and unlock true business agility? Discover why embracing the journey of transformation is key to lasting success. Dive in to learn more!

Should I Become a Scrum Master? Explore 10 Insightful Questions to Help Make Your Decision

Explore 8 red flags indicating incomplete Kanban adoption. Enhance your team's agility with Practicing Kanban

Unleash Scrum's Potential: Discover Where to Start for Efficient Value Delivery (Product) and Continuous Improvement via Value Stream Mapping

Explore the challenge of 'Escaping the Product Owner’s Trap' in this insightful blog post. Learn how Product Owners often find themselves entangled in component thinking, losing sight of broader objectives and value delivery. Uncover key principles such as Vision, Value, and Validation, and discover actionable strategies to shift towards a product and value-driven mindset. This guide illuminates the path from mere component management to genuine Product Ownership, offering tools and techniques to align with organizational goals and customer needs.

Dispelling Agile and Scrum myths. Learn how Scrum enables Agile principles. Empower your teams to adapt, innovate, and deliver excellence.

A common question we get asked is how do we get started with creating a Definition of Done? Let's explore how we can obtain transparency of where you are, your destination should be, and what your possible first steps are to get there!

Some may confuse the word “Foundation” in the name of the Professional Scrum Foundation course to mean simple or basic. But in truth this means it is a course for everybody to build a solid base of knowledge,

As the name “Test First” suggests, you write a test first before the actual code and keep them running all the time. Well, maybe not the second part explicitly. Yet what if I said to you that it actually means more than that?