As a Scrum trainer, I get the chance to hear from people working in widely different industries - from finance to healthcare to tech. Because of my unique position, I have the opportunity to notice trends that cross industries. Here is what I am hearing a lot about lately.
1. The Shift Toward a Product Model
One of the brightest changes I’ve observed is a growing move toward the product model. And as I mentioned last week, I am thrilled to hear about this one.
When I say that people are adopting a product model, it means that they are coming to the realization that siloing their teams by technology doesn't work. When organizations adopt the product model, it means that they are taking a step back to ask, “What are we trying to deliver?”, and then they are building cross-functional teams to deliver it.
This isn’t an easy transition. Stepping back to define products takes time, thought, and often a cultural shift. But it’s worth it. Teams that embrace a product model find they’re better able to reduce dependencies, focus their efforts, and deliver value faster.
2. The Rise of Kanban-Inspired Practices
Another trend I’m personally delighted to see is the increasing adoption of Kanban practices used within the Scrum framework. In particular, I am thrilled to see that teams are increasingly deciding to limit their work in progress (WIP). What this means that for any step in the process (e.g., Development, Testing, etc.), the team decides upon a maximum number of work items that can be in the active state at any given time. It seems like a small change - but it has a profound impact on focus and actually helps teams deliver value sooner because they aren't multi tasking as much.
When teams work on fewer things at once, they actually get more done—and they do it better. By limiting WIP, teams reduce context switching, improve focus, and create smoother flow through their system. I’ve seen teams go from constant chaos to steady, predictable delivery simply by implementing a WIP limit. It’s one of the most accessible and effective improvements a team can make, and I’m thrilled to see it gaining traction.
And, yes, when you limit work in progress, it's still Scrum. You are simply adding another compllimentary practice to your tool kit. (Sign-up for the Professional Scrum with Kanban to participate in activities that will help you convince your team - and yourself! - of the power and impact that limiting work in progress can have on your team.)
3. Simplify to Accelerate Value Delivery
Finally, many teams are simplifying their Scrum practices. Teams are starting to ask: “What’s truly helping us deliver value, and what’s just overhead?”
One example I hear often is the removal of unnecessary approval gates. While well-intentioned, these gates can slow delivery, create bottlenecks, and undermine the team’s ability to self-organize. By letting go of these constraints, teams can move faster while still maintaining quality and alignment.
Many people don't realize that Scrum is simple for a reason! It's because teams working in complex environments should apply this simple framework in the way that works best for their environment. Scrum doesn't require you to have a certain number of columns on your backlog or to write your Product Backlog items in a certain format. The team decides on what format and which complimentary practices are helpful, and Scrum gives them just enough - but not too much - structure to help them collaborate around value. When teams simplify their Scrum and let go of the extra constraints, it’s a return to the heart of Agile: responding to change and continuously improving. (Join us at Scrum Day Madison for Agile manifesto co-author Alistair Cockburn's keynote talk on Returning to the Heart of Agile.)
Final Thoughts
These trends—adopting the product model, incorporating Kanban practices, and simplifying Scrum—are all signs of a deeper maturity in Agile thinking. Teams aren’t just following a what the latest big box consultant has told them to do; they’re making it their own, grounded in the real-world need to deliver value.
If you’re part of an organization on its Agile journey, I encourage you to reflect on these trends. Are you clear on your products and customers? Are you limiting WIP to improve flow? Are you holding onto rules that no longer serve you? The answers may unlock the next step in your evolution.