<aside> 🌖 Rituals bond your team Every team has a common language and customs. Decide how you'll plan, build, test, build, and most importantly learn together, then make sure the dates are on the calendar.

</aside>

• [ ] Set sprint length
• [ ] Set ticket acceptance criteria (discuss with PMs, devs, and QA)
• [ ] Set definition of done
• [ ] Set stand-up times

maybe a few one hour plannings at the start... lock in on initial problem framing (commander versus agent)

• [ ] Set planning cadence chris and jacob
• [ ] Set retro times chris and jacob
• [ ] Set demo and decide times chris and jacob

Note: This part should be fun! Reference what we did with ROCK SOLID ROUTING to see how much we can learn as we go.

chris and jacob