| 7 - 1st Tuesday | **Midpoint**<br><br>Any issues that are at risk of slipping from the iteration must be raised by the assignee | - |
| 10 - 2nd Friday | **The last day to submit MRs for review**<br><br>MRs must include documentation and testing to be ready to merge <br><br>MRs tend not to be merged on Fridays, or on Thursday in the case of Family and Friends Day (unless there is urgency, i.e. P1-Ops related MRs or in cases with tight timelines). | **Iteration is roughly final**<br><br>Iteration Planner verifies issue priority and team capacity for next iteration. |
| 10 - 2nd Friday | **The last day to submit MRs for review**<br><br>MRs must include documentation and testing to be ready to merge <br><br>MRs are preferably not to be merged on Fridays, or on Thursday in the case of Family and Friends Day, (unless there is urgency, i.e. P1-Ops related MRs or in cases with tight timelines) to minimise impact on days where there is limited team member availability. | **Iteration is roughly final**<br><br>Iteration Planner verifies issue priority and team capacity for next iteration. |
| 13 - 2nd Monday | **Last day of Iteration**<br><br>Ready MRs can be merged | - |
| 14 - 2nd Tuesday | **Meeting Day**<br><br> All unfinished issues either need to be removed from iterations or rolled to the next | **Iteration Planning**<br><br> Sync-meeting to perform retro perspective on the current iteration and align/start on the next iteration according to the created iteration planning. All unfinished issues either need to be removed from iterations or will be automatically rolled to the next |
