I am a Product Owner for an IT service firm with developers in the US, India, and Poland. We are struggling with Backlog Refinement because by the time one team has questions, the others are asleep. This is leading to "Sprint stall" where tasks aren't clear enough to start. What are the best practices for asynchronous refinement and ensuring the "Ready" criteria are met for every single user story in a global environment?
3 answers
For distributed teams, you must move away from the idea that all refinement happens in a single meeting. Implement a "Refinement Workflow" in your ALM tool (like Jira) where stories move through a "Draft" to "In-Refinement" to "Ready" state. Encourage developers to leave comments and questions on tickets throughout their workday. As a PO, you should record short "Loom" videos explaining the "Why" and "What" of complex stories so the teams can watch them during their own hours. By the time you do have a brief sync meeting, it should only be to finalize the points and confirm that everyone is aligned on the Acceptance Criteria.
Do you have a "Definition of Ready" that specifically requires a visual mockup or a technical diagram before a story can even be discussed?
We use a "Rolling Refinement" where we stay two Sprints ahead. This gives the global team plenty of time to ask questions before the Sprint Planning session starts.
Rolling refinement is a lifesaver. It completely stopped our "Monday Morning Panic" where we realized halfway through planning that a story was impossible to estimate.
Brandon, we don't have that yet, but it sounds like exactly what we need. Right now, a lot of our stories are just text-heavy, which leads to translation issues and misunderstandings. If I mandate that every complex story needs a wireframe or a flow chart, do you think that will slow down the "Creation" phase too much? I’m already underwater trying to keep up with the current pace of three different teams, and adding a diagram requirement feels like it might become a bottleneck for my own workflow as the Product Owner.