I am a big fan of the annual State of Agile  report from Digital.ai . Each year, the report looks at things like: Why organizations adopt Agile What frameworks they use What challenges they’re facing But this year was different. For the first time in its 18-year history, Digital.ai didn’t ask about frameworks. They didn’t ask why teams choose Agile. They didn’t even discuss (much) about scaling approaches. Instead, the entire report turned its spotlight on something else en

I once worked in an organization where needed to grow from one Scrum team, staffing up into (eventually) many teams supporting one cross-functional product. I suggested that as new staffing joined us, we should let them self-organize into their own Scrum teams.

What should you do with the Sprint schedule for the holidays? Ask the Scrum team!

Take 10 minutes to think about your day.

Interview questions for the Scrum Master

The Sprint Review is the Product Owner's most valuable event. It’s an opportunity for the Scrum Team and its stakeholders to discuss what was done, and to brainstorm where to go next. When the Sprint Review goes well, it feels like a collaborative workshop. When it doesn’t, it’s a one-way communication that nobody hears. Useless.

Why you should be using flow metrics instead of points to forecast delivery dates in Scrum.

When people first step into the Scrum Master accountability, they often focus entirely on the Scrum Team. That’s understandable—after all, the Scrum Guide defines the Scrum Master as accountable for the Scrum Team’s effectiveness.

Rebel Scrum is the host of the annual Scrum Day Madison conference as well as the upcoming Scrum Day Houston Agile conference. This year's event brought together hundreds of Scrum practitioners, Agile leaders, and innovators for a day of learning, collaboration, and fun. The day kicked off with a flash mob performance by the University of Wisconsin Band , setting the tone for an engaging and high-energy event. With three keynote speakers  and multiple breakout sessions cov

Communication is more important than efficiency for complex, creative work.

One of my favorite Agile books is actually 'Kanban' by David Anderson. In it he talks about the value of Slack time, or time when a Developer has finished all of their work.

If we keep our eyes fixed on velocity, we’ll drift into the rocks. But if we look downstream—toward the real value we’re trying to deliver—we’ll find ourselves moving in the right direction.

In this fast-paced world, we need Scrum more than ever. From the transparency created by artifacts to incremental delivery that keeps us on track, Scrum gives organizations a way to adapt and thrive. AI is a powerful tool, but instead of replacing Scrum, it makes the framework even more essential. Here are five reasons why Scrum is more relevant than ever.

Is your Scrum team just going through the motions of Scrum without using it to focus on continuous improvement? Then coach the "fluffy" Scrum values to help turn them into a team focused on value.

If your team is struggling, pause and ask yourself: Are we really using Scrum the way it was designed? Here are 10 signs you might be holding your Scrum team back - and what you can do about it.

Here are ten practical ideas that your team may consider adopting to help improve your ability to get to Done.

Digital AI releases an annual "State of Agile" report which I am eagerly anticipating. While I wait for the 18th report to be released, I want to take a moment to look at how we have talked about Agile has changed over time.

Working in parallel creates walls to progress.

One practice from Kanban that I think is often overlooked is related to the flow of work. Work on the Scrum board should flow from left to right - but it shouldn't flow backwards.

Looking back, it boggles the mind that companies used to operate without the Product Owner accountability. Projects came and went, budgets were spent, and timelines were met—yet customer needs and business goals were often missed.