{"id":48,"date":"2026-10-08T09:20:00","date_gmt":"2026-10-08T09:20:00","guid":{"rendered":"https:\/\/weeks-from-today.com\/blog\/?p=48"},"modified":"2026-10-04T16:43:18","modified_gmt":"2026-10-04T16:43:18","slug":"work-sprint-planning-in-weekly-increments","status":"publish","type":"post","link":"https:\/\/weeks-from-today.com\/blog\/work-sprint-planning-in-weekly-increments\/","title":{"rendered":"Work Sprint Planning in Weekly Increments"},"content":{"rendered":"

TL;DR:<\/strong> A sprint has a length the team already agreed, usually two weeks, and a start datetime that is a real calendar day. Stack later sprints by adding that length again, and keep demo day and release day as separate labels if they are not the same date. When kickoff slips, recompute on the weeks from today calculator<\/a>; do not quietly shorten the sprint to \u201ccatch up.\u201d<\/p>\n

Length is a number in the working agreement<\/h2>\n

If the team agreed that a sprint is two weeks, the end is 14 days after the start, landing on the same weekday. You do not get to call a nine-day rush \u201csprint 14\u201d and also claim the velocity chart is comparable. You can run a shorter cycle. You then name it as shorter and keep it out of the two-week series, or you accept that the chart will kink. The calculator\u2019s role is modest: turn \u201ctwo weeks from the kickoff day\u201d into a date everyone can paste into the tracker. The social role \u2014 whether the team respects that date \u2014 is not something a date tool can repair.<\/p>\n

Write the length where the dates are, not only in a charter nobody opens. \u201cSprint length: 2 weeks\u201d at the top of the board prevents a well-meaning manager from treating the end date as a suggestion that moves whenever a demo room is free.<\/p>\n

Two weeks from a Wednesday kickoff<\/h2>\n

Kickoff is Wednesday, 15 April 2026. Two weeks later is Wednesday, 29 April 2026. If your convention is that the sprint ends at the start of that Wednesday\u2019s planning, say so: work days are 15 April through 28 April, and the 29th is the next kickoff. If your convention is that the 29th is still inside the sprint until close of business, the end is still the 29th but the next kickoff cannot also be the morning of the 29th. The week math does not choose the convention. It gives you the Wednesday. The team writes whether that Wednesday is a fence or a day of work.<\/p>\n

A kickoff on Wednesday is slightly awkward for people who assume sprints start on Monday. Do not \u201cfix\u201d it by sliding the start back to Monday, 13 April unless the team actually started then. A Monday start plus two weeks is Monday, 27 April, which is a different end. Sliding the anchors to Mondays for neatness rewrites history and makes the demo invite wrong. Keep Wednesday if Wednesday is when you planned.<\/p>\n

Three sprints in a row on one calendar<\/h2>\n

Using the fence convention \u201cnext kickoff equals this end,\u201d the series from Wednesday, 15 April 2026 is:<\/p>\n