[ToC] ## Why are we doing this? We want to ensure we are reserving capacity from escalation handling to pursue strategic product goals that will drive stability and vision. ## How are we doing this? The team will be split into "squads": 1. **Dev Squad** - fully focused on attaining strategic goals 2. **Reaction Squad**- DRIng escalations and participating in development as time allows For documentation on how reaction rotation should work like please see our [handbook page](https://handbook.gitlab.com/handbook/engineering/development/sec/secure/dynamic-analysis/dynamic-analysis/#reaction-rotation) ## Rotation The two squads will cycle in between Dev and Reaction roles every milestone. ### Changing squads Ask a parallel in a different squad if they're OK with switching. Then switch. ### Special cases Talk to @tkopel ## Schedule | Milestone | Reaction | Dev | |---|---|---| | 17.6 | David, Arpit | Mike | | 17.7 | Mike, Arpit | David, Hannah | | 17.8 | Mike, David | Arpit, Hannah | | 17.9 | Hannah, David | Arpit, Mike | | 17.10 | Hannah, Arpit | David, Mike | | 17.11 | Mike, Arpit | David, Hannah | | 18.0 | Mike, David | Arpit, Hannah | | 18.1 | Hannah, David | Arpit, Mike | | 18.2 | Hannah, Arpit | David, Mike | | 18.3 | Hannah, Arpit | David, Mike | | 18.4 | Arpit, David | Hannah, Mike | | 18.5 | Mike, David | Arpit, Hannah | | 18.6 | Hannah, David | Arpit, Mike | | 18.7 | Hannah, Arpit | David, Mike | | 18.8 | Mike, Arpit | David, Hannah | | 18.9 | Mike, David | Arpit, Hannah | | 18.10 | Hannah, David | Arpit, Mike | | 18.11 | Hannah, Arpit | David, Mike | | 19.0 | Mike, Arpit | David, Hannah |