Nine in ten tickets I see come with conversations attached.
Could you have them before the ticket’s marked Ready?
It’s Thursday afternoon. A developer posts in the team channel: “I’m stuck on part of this ticket.”
It feels like a surprise. Really, it was decided on Monday, when the ticket went into the sprint without anyone checking what it would take to finish.
When I start working with a team, one of the first things I look for is waste. Time spent waiting, redoing work, or working something out for the second time. A fair bit of it comes from how we treat tickets, and the fix usually starts with how the team writes its definition of ready.
What a clear ticket looks like
A clear ticket needs little or no discussion. Anyone on the team with the right experience can pick it up, build it, test it, deploy it and show it to the client, without someone having to explain it first.
That’s rare. Possible, but rare.
Small tickets need fewer conversations
There’s an old checklist for good tickets called INVEST, from Bill Wake. A good ticket is independent, negotiable, valuable, estimable, small and testable.
Small does the most work. The smaller the ticket, the fewer conversations it needs and the easier it is to make clear. A big ticket usually struggles with the rest too. It’s harder to estimate, harder to test, and tangled up with other work.
If a ticket needs a long conversation, it often wants splitting.
What a ticket really is
Most tickets still aren’t clear, and that’s fine. Writing a properly clear ticket takes time, and when there’s pressure on, we write a placeholder instead. A title, a line or two, maybe a link to a design. Really, it’s a promise to have a conversation later.
So here’s how I think about it. Every ticket is a promise that some work will get done. A placeholder carries a second promise: that some conversations will happen first.
Take a ticket that says “Add filters to the search results”. Which filters? Can you combine them? What happens when nothing matches? Does it need to work on mobile? Leaving those out when the ticket was written was reasonable. Each one is still a conversation someone will need to have before the work is done.
Those conversations happen anyway
There’s often a feeling in a team that talking about the work is expensive. Long meetings feel like waste. Doing gets praised, and visible progress is how people show they’re being productive. So placeholders go in, and everyone gets started.
But the conversations still have to happen. So they happen late, in small pieces, and often without the people who needed to be there. They start like this:
“I’m stuck on part of this ticket.”
“This isn’t what we were expecting.”
“I’m not sure how to test this part.”
By then the dev has built half of it, the client has seen something different from what they pictured, or QA is holding a ticket they can’t sign off. Each one starts a feedback loop at the worst possible moment. Someone has to stop and wait for an answer, and by the time it comes they’ve moved on to something else and have to find their way back in. The longer the wait, the more it costs.
Bring them forward
So I don’t push teams to write perfect tickets. I push them to have the conversations earlier, while they’re cheap.
In practice that means:
- When a ticket’s being refined, ask what conversations it still needs, and who with.
- Have them before the ticket’s marked Ready, rather than halfway through the build.
- Put what you learn back into the ticket, so the next person doesn’t need the same chat.
- If a ticket slips through without them, have them before anyone starts building.
A definition of ready that fits
This is where a definition of ready helps. Most teams write one that says a ticket must be clear before work can start. That’s a high bar, and under pressure, teams skip it.
There’s another way to write it. A ticket is ready when it’s clear, or when the conversations it needs have happened and what came out of them is in the ticket. It doesn’t need a perfect write-up. It needs the right people to have talked.
That’s a bar most teams can meet. And it moves those Thursday afternoon “I’m stuck” messages to Monday morning, when they cost a lot less.
Try adding one line to yours: “The conversations this ticket needs have happened, and what we agreed is in the ticket.” Then see what turns up on Thursday.
I’m Harry Bailey. I work with delivery teams that are tired of finding out on Thursday what they should have known on Monday. See how a team reset works.
Photo by mediha ekici on Unsplash