24/07/2026
📌 I’m starting a new series where I’ll share small changes I made as a Project Manager that created a bigger impact than I expected!!
Here’s the first one.
When I joined Inspectrum, we were running sprint retrospectives because that’s what Scrum says you should do. Every sprint looked the same:
“Communication could be better.”
“We need to estimate more accurately.”
People talked. We wrote notes. Then we moved on. The next sprint? The same conversation. I realized the problem wasn’t the retrospective. It was that nothing actually came out of it.
So I introduced one simple rule:
💡 Every retrospective ends with one action item. 💡
Not five, not a long wish list. Just one improvement, assigned to one owner, with one deadline before the next sprint planning.
We tracked it on a visible board, so everyone could see:
what we agreed to, who owned it, and whether it was completed.
The first month wasn’t perfect. A few actions slipped. But because everyone could see them, accountability became part of the process instead of something managers had to chase.
After a few months, something changed.
The team stopped bringing up generic problems and started talking about the real blockers because they knew their feedback would actually lead to change.
✅ Design-to-development handoffs became smoother.
✅ Our estimations became more predictable.
And over the following months, the team’s productivity improved by around 15%, simply because we kept removing small sources of friction instead of letting them repeat every sprint.
One thing I’ve learned over the years is this:
Teams don’t trust processes because they’re Agile, Scrum, or written in a handbook. They trust them when they consistently solve real problems.
That’s when a process stops feeling like a ceremony and starts becoming a tool.
I’m curious: what’s one small process change you’ve made that created a surprisingly big impact?
