Product owners handed the team finished tickets, the team built exactly what was written, and every sprint review showed it was not what anyone had meant.
Hard Work, Steady Rework
A reporting team at a global research and advisory firm pulled data from a large internal database and turned it into dashboards colleagues across the business relied on. Its requests came from internal customers in another country, through two product owners who collected them and passed them to the team.
The team worked extraordinarily hard and shipped a significant volume of work every sprint. It also produced a steady stream of rework, because the work it was handed was never fully understood before anyone started on it. Its Scrum Master was sharp and organized, and had been functioning more like a program manager than anyone had formally acknowledged. She kept the work moving and knew where everything was. She had also been quietly compensating for a broken handoff for months.
Refinement That Was Really Order-Taking
We watched refinement sessions before drawing any conclusions. What we saw was not refinement. It was order-taking. The product owners arrived with tickets they had already written. They described what they wanted: a button in a particular place, a dashboard that read a certain way, a report that showed a specific number. The team listened. Nobody asked questions. The session ended, and the team went off to build what it thought had been described.
Days or weeks later, the sprint review arrived. The product owners looked at what had been built and found it was not what they had imagined. The button was in the wrong place. The dashboard was missing a dimension nobody had mentioned. The report showed the number, but not in the format anyone wanted, because nobody had specified a format. The product owners asked why the team had not built it their way. The team asked why the product owners had not said so in refinement.
Both questions were fair, and that was the problem. The team was not failing to deliver. It was delivering exactly what the tickets said, which was a smaller and less precise thing than the requesters had in mind. The product owners lacked the technical context to scope the work completely, and the team had been conditioned not to ask the questions that would have closed the gap. Nobody owned the conversation in between.
-
Customer makes a request
-
Half the picture Ticket written alone No technical questions asked.
-
Where it broke Team listens in silence Order-taking, not refinement.
-
Team builds the ticket Exactly what was written.
-
Where it shows Review: not what was meant Rework enters the next sprint.
Participants, Not Observers
We raised it with the Scrum Master first, because she had already named it privately. The product owners, she said, saw refinement as something they did before giving the work to the team, not as a conversation with it.
The product owners were less receptive. They had written the tickets. They had done their part. Being asked to work through those tickets again with the team felt to them like doing the same work twice, and somewhat beneath the seniority they believed they held. Their job was to bring the work. The team's job was to do it.
We told the leadership above them that the product owners needed to be in refinement as participants, not observers. The team could not scope the work without them, and they could not scope it without the team. Leadership made their participation mandatory. It was not popular with the product owners. It was the right decision.

The Questions Nobody Had Asked
The first few sessions with everyone in the room were awkward. The product owners were used to speaking and being heard; the team was used to listening. Neither habit served refinement, so we disrupted both. We started directing questions to the developers instead of the product owners. When they say the dashboard should show this data, what do you need to know to build it?
Slowly, the team answered. It needed the expected response time. It needed the acceptable error ratio. It needed to know whether the data should be filtered by region or by account type, because that changed how the query had to be built. And it needed to know what the user would actually do with the insight, because that changed what the insight had to show.
The product owners had never been asked these questions, because the team had never asked them, and the team had never asked because nobody had made asking expected. Once the questions started, the product owners began to see what the team needed from them: not a picture of the output, but the business context that would let the team decide how best to produce it. They had been stakeholders given a product owner's title without anyone explaining what the role required.
- A button in a set place
- A set dashboard layout
- A report showing a number
- Expected response time
- Acceptable error ratio
- Filter by region or account
- What the user will do with it
Giving the Seam an Owner
By the end of the engagement, refinement was genuinely collaborative. The team spoke. The product owners listened as often as they talked. The Scrum Master facilitated instead of compensating. The rework that had been consuming a significant share of every sprint shrank, because the work was understood before it was built rather than after it had been built wrong.
The handoff had never been missing. It happened every sprint. What was missing was ownership of the conversation inside it. Requests crossed from internal customers to product owners to the team, and at each crossing something was dropped, because each side believed its part was finished when it handed the work on.
Making refinement mandatory and two-way gave that seam an owner: the people who held the requirements and the people who would build them, in the same conversation, before the work began.
A handoff works only when both sides of it have to talk before the work starts. Otherwise the conversation happens anyway, at the sprint review, after the work is built.
Share With Your Team
Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.


