Hi!
I’m conducting an anonymous survey for my bachelor’s thesis on communication in multicultural project teams. It takes around 8–10 minutes.

I would be very grateful if you could complete the survey or share it with someone who fits the criteria.
https://forms.gle/vRbbCudhSe8rhqDE6

Thank you for your help!

The uncomfortable answer is that updating the tool is probably no one's actual job. It's everyone's implied job, which means it loses to real work every single day, and honestly it should.

What worked for shops I've been in: stop asking everyone to keep everything current. Name one person whose job is a 15-minute weekly pass asking "what on this board is no longer true?" They don't update everything themselves. They just flag what's stale and chase down the truth on the few things that matter.

The team usually stops hating the tool once it stops being a chore everyone shares and starts being one person's short, defined task.

One thing worth checking before you change anything though: is it that they don't update it, or that they update it and nothing ever comes of the updates? Different problems. The first one is the fix above. The second one means the updates go into a void, and people quit updating tools no one reads. That one gets fixed by you, not them.

Back at university I had a course called "Software Processes and Patterns" that introduced me to a tool called AQUSA for finding defects in user stories. Not whether they make sense, but whether they have the right form: no conjunctions, a role present, unique (no duplicates), and so on.

It's based on https://github.com/RELabUU/aqusa-core and the underlying article Improving agile requirements: the Quality User Story framework and tool

The link: https://userstorydoctor.com

It's free, and I don't track anything but the IP (through Cloudflare) to make sure it isn't abused. It's an AQUSA wrapper with both an HTTP endpoint and an MCP server, and it can analyse up to 500 stories at a time, so you can run a semi-large backlog in one go.

The idea was to bring some determinism to my backlog agents. They hallucinate a lot when asked to check the five structural defects AQUSA finds, like "Uniform", where the format "As a [role], I want [goal] so that [reason]" drifts when different people write the stories. Agents are also notoriously bad at cross-referencing across stories.

I'd love feedback if anyone has any.

Our leadership is suddenly into DORA and wants us to improve deployment frequency and lead time. The problem is our process is bogged down with approvals and checks at every stage. We end up batching everything into these massive releases which makes things riskier. I get the theory but in practice I'm not sure what makes a difference without creating more work for us. Anyone been through this and improved their numbers?