Template description
Iteration planning has one arrow, into Build and test. Build and test has two outgoing arrows. One goes to Daily standup, and Daily standup comes straight back, so the standup is a loop beside the work rather than a gate. The other arrow leaves Build and test for Iteration demo. The demo does not return to the build. It goes to Retrospective, and the retrospective returns to Iteration planning. You can walk two loops. The inner one is standup and build. The outer one closes only after demo and retro. Nothing in the picture lets the standup jump to the demo.
When to use it
Read it when a new team treats the standup as the meeting that approves the demo, or when a retro is being skipped because the build loop feels endless. The arrows separate those rhythms. The demo leaves the build box, and the next planning starts only from the retrospective.
How to adapt it
Rename the ceremonies to the names you use, and say the iteration length on Iteration planning if people still call it a sprint. If the demo can send work back without a retro, add that arrow from Iteration demo to Build and test. If the standup should also be attended by people outside the build, note them on the box rather than inventing a new sequence. Keep the return from Retrospective aimed at planning unless your retro feeds a different backlog meeting.