TemplateMethodology1 min read
What it is for
Keep design one sprint ahead of development, without a tunnel effect.
The questions it helps settle
Where in the design cycle
Two thirty-minute meetings, alternating from one week to the next, between the Product Owner and the design team. The first one identifies the design topics of the coming sprint, the second one prepares the sprint planning.
The ritual exists to avoid the tunnel effect: design runs one sprint ahead, the Product Owner knows the state of the mockups, and tickets reach refinement with deliverables that can already be seen.
This process describes two kinds of synchronisation meetings, held in alternation between the Product Owner and the design team. The goal is a smooth collaboration and an efficient preparation of the design deliverables for the sprints.
Each meeting lasts thirty minutes. The two kinds follow each other: one week the identification of topics, the next week the preparation of the sprint planning.
A topic that is not ready at the second meeting does not enter the sprint. It comes back to the next identification meeting, with what it lacks named explicitly.
