When a team is high performing, it can be all too easy to for the Scrum Master to say whelp, that's it! Mission accomplished.

AI can generate code faster than your team can review it. Especially with the latest iteration of Claude, the code comes packed with lengthy comments, voluminous release notes, and logic in a bunch of different places, all of which needs to be reviewed before it goes to production. The human in the loop remains essential for quality. But with so much work coming at us, we can quickly become a bottleneck, too. The counterintuitive answer is to limit work in progress and focus

Sprint after Sprint, a lot of work remained unfinished at the end of the Sprint. Instead of returning that work to the Product Backlog or discussing next steps at the following Sprint Planning event, the vendor simply left the previous Sprint open. At any given time there might be four or five Sprints open for the same Scrum team. Don’t do this!

One of the recent trends that I am thrilled to hear about is that many organizations are - at last! - starting to take note of the importance of defining their products.

Scrum is a popular framework agile teams use to deliver high-quality software products collaboratively and iteratively. According to the latest State of Agile report from Digital.ai, 90% of agile teams use Scrum. Scrum's laser focus on iteratively producing usable increments of value is part of what makes it stand apart from a traditional project management approach. Managing a tight Product Backlog is integral to delivering that value. Scrum is often used for software pro

It’s a myth that Scrum Teams don’t plan. Scrum Teams plan at the Sprint Planning event and when refining work items. They also create a forecast or a roadmap that shows their plans across multiple Sprints. Scrum Teams plan frequently to navigate complicated environments where new information emerges constantly. The team inspects new knowledge and adapts their approach to take advantage of what they've learned. What happens when the team is confronted with unplanned work mi

Agile is an umbrella term encompassing a variety of frameworks and approaches to value delivery in complex environments. The word agile came into widespread use following the creation of the Agile Manifesto in 2001. That year, a group of 17 software practitioners looking for a better way to deliver software settled on the the term agile to refer to their more rational, human approach to complex work. Agile, in this context, is now a widely used term, and the Agile Manifesto h

​ The 2020 Scrum Guide includes five values that are important to every successful implementation of Scrum. These values are courage, commitment, focus, openness and respect. The 5 Scrum Values These values don’t get much attention, but the longer I practice Scrum and coach teams, the more important I find them. This article will define each Scrum value and provide examples of how they play out in the real world. Focus Focus in the context of Scrum means to focus on the w