Remove no-merge Friday (286bd24a) · Commits · GitLab.com / Content Sites / handbook

content/handbook/enterprise-data/how-we-work/planning/index.md

+2 −2

Changes for content/handbook/enterprise-data/how-we-work/planning/index.md: 2 added lines, 2 removed lines.
Original line number	Diff line number	Diff line
		@@ -133,7 +133,7 @@ Work Breakdowns consider the following inputs:

		### Twice-Weekly Iteration Planning

		The data team works in two-week intervals, called iterations. Iterations start on Wednesdays and end on Tuesdays. This discourages last-minute merging on Fridays and allows the team to have iteration planning meetings at the top of the iteration.
		The data team works in two-week intervals, called iterations. Iterations start on Wednesdays and end on Tuesdays. This allows the team to have iteration planning meetings at the top of the iteration.

		Iteration planning should take into consideration:

		@@ -153,6 +153,6 @@ The timeline for Iteration planning is as follows:
		\| ----------------- \| ------------------------------------------------------------------------------------------------------------------------------------------------------------ \| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- \|
		\| 0 - 1st Wednesday \| Iteration Start <br><br> \| - \|
		\| 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 are preferably not to be merged on Fridays (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. \|
		\| 10 - 2nd Friday \| The last day to submit MRs for review <br><br>MRs must include documentation and testing to be ready to merge. \| 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 \|