If you’ve spent any time in the world of Agile, you’ve heard of both Scrum and Kanban. They’re often mentioned in the same breath, sometimes used interchangeably, and occasionally confused with each other entirely. They’re not the same thing, but they’re also not opposites. Both are grounded in Agile values, both help teams deliver better … Read more
If you hold a Scrum Alliance certification, you already know the credential doesn’t last forever. Every two years, you’ll need to renew, and that renewal requires more than a fee. It requires proof that you’ve kept learning. That’s where Scrum Education Units (SEUs) come in. This guide explains what SEUs are, why they matter beyond … Read more
Sprint planning gets a bad reputation in a lot of organizations. Teams sit in a room for hours, the Product Owner reads through a list of stories, developers stare at the ceiling, and everyone leaves with a vague sense that they just endured something rather than accomplished something. It doesn’t have to be that way. … Read more
One of the clearest signs of an effective Scrum Master isn’t how well they run ceremonies… it’s how well their team solves problems. If a team keeps making the same mistakes, keeps hitting the same walls, and isn’t visibly improving over time, something isn’t working. This post offers a practical framework for ScrumMasters who want … Read more
If you ask any Agilist how they measure success, you’ll probably hear one common answer: velocity. It’s simple. It’s visible. It produces a clean chart at the end of every sprint. But it’s the wrong metric. Velocity measures how much work a team completes. It does not measure whether that work matters. Agile was never about maximizing output. It was about improving outcomes in uncertain … Read more
On paper, the Product Owner role looks powerful: set priorities, maximize value, say “no.” In practice, many Product Owners end up acting more like air traffic controllers for stakeholder requests, trying to keep everything from crashing while having very little authority to change the flight plan. This isn’t a failure of Scrum. It’s a failure of organizational clarity, decision rights, and … Read more
Sprint retrospectives are meant to be the engine of continuous improvement; the moment your team pauses, reflects, and gets better. And yet, paradoxically, retrospectives are often the least Agile Agile ceremony. Not because teams don’t talk honestly. In fact, retros can be some of the most cathartic, thoughtful meetings a team has all sprint. But too often, they end there: a good … Read more
If you’ve ever stared at a backlog full of vague user stories like “As a user, I want to log in so that I can access the system,” you know the classic pain points: User stories are often uncomplicated, but they’re also easy to misuse. Great user stories don’t just describe features. They connect real human needs to measurable business outcomes. They reduce ambiguity. They empower teams. And yes, they actually deliver value. … Read more
This is part two of our Agile leadership blog series. If you missed part one, “What Even Is Agile Leadership,” check it out here. Corporate strategies rarely fail on paper. They fail in execution when culture and reality collide. Senior leaders read the blogs, know what’s happening in the zeitgeist, study Harvard Business Review, etc. … Read more
It’s almost Thanksgiving, so let’s talk turkey: most ScrumMaster resumes look like they were cloned in a lab. They say, for example: Yes, that’s what a ScrumMaster does. Yes, that’s what the Scrum Guide prescribes. Yes, when we look for a ScrumMaster, we want them to do those things. But what impact did … Read more