As they do so teams should continue to validate their work doing user testing, A/B testing, gathering feedback and further refining the prioritization of the backlog. So we’re by no means done, but we’ve got to a point where we can get into a cadence of delivery, and use regular Retrospectives to track our progress and find ways to continually improve. Certainly my experience has been that in large organisations who are still learning how to apply Design Thinking and Agile, getting to this point is the hardest part for a project.
Planning Poker is a great approach because it sizes stories relative to each other, and doesn’t get into the political nightmare of deciding exactly how many man hours a story is. It helps focus the conversation on the work required, not the pressure to execute that work in a particular timeframe.