Common Scrum practices offer various instruments for team work visualization: product/sprint backlog, daily standups, burndown/burnup charts. However, this tool set is rarely found sufficient for large project teams which are distributed between different locations and suffering time zones difference.
How to understand whether backlog items prioritized correctly? Do teams understand priorities for next sprint and release? Are user stories refined enough for development? Many of these questions are often found in a "dead zone" which causes a lot of trouble with scaling. On top of that, many distributed teams often suffer from gaps in communication with business stakeholders.
In this presentation I review a couple of practices for backlog structuring and visualization, using product discovery techniques for building shared understanding between all parts of distributed team, bottleneck identification and elimination, definitions of "done" for backlog items refinement process.