Days to Weeks

Ten Working Days Is Fourteen on the Wall Calendar

Somebody in refinement says a piece of work is about eight days. The delivery manager writes it into a plan. A stakeholder reads that plan and hears "next week and a bit". Three people, three different units, and none of them said which one they meant. Engineering estimates almost always come in working days, because that is what a person can picture doing; schedules and release dates live on a seven-day calendar, because that is what everyone outside the team looks at.

The gap is not subtle. Eight working days is nearly two whole calendar weeks, and the error compounds every time an estimate is passed along without being converted.

Conversion factor: 1 wk = 7 d, so divide days by 7. A 45-day run is 6.42857143 wk. But if those 45 are working days, the calendar span is 63 d, which is 9 wk — one estimate, two answers, and only one of them belongs on a roadmap.

Where the Two Counts Diverge in Delivery Planning

Estimates arrive in working days

Nobody sizes a ticket by imagining a weekend in the middle of it. Whatever unit the board displays, the number an engineer had in mind was days at a desk, and it needs stretching before it can meet a date.

Calendars run on seven-day weeks

An iteration boundary, a release window and a demo invitation are all pinned to a seven-day grid. Divide by 7 and you get the span people will actually live through, weekends included.

Ceremonies come out of the same budget

Planning, review, retrospective and the daily standup are real hours inside the iteration. Counting them separately from "the work" is how a cadence ends up quietly over-committed every time.

Stakeholders hear weeks, not days

Outside the team, weeks are the currency of a commitment. Handing over a day figure invites the listener to convert it themselves, usually generously, and to remember the optimistic version.

Converting a Backlog Estimate Into Calendar Time

The routine takes seconds and saves an argument later: establish which kind of day you were handed, get it onto the calendar, then round in the direction that will not embarrass you.

Start from the estimate you were handed

Drop the raw number into the left field and the week figure follows on the same keystroke. Spaces inside a pasted value are ignored, so a figure lifted out of a tracker export needs no tidying first.

Add the non-working days back in

If the estimate counted desk days only, multiply by seven fifths before converting: 15 becomes 21, a clean 3 wk. Skipping this is the single commonest reason a plan reads a third shorter than it runs.

Flip the direction for a stakeholder date

Hit swap (↔) when the conversation starts from a target instead: six weeks comes back as 42 d. The right-hand box also takes input directly, so a week count typed there resolves the day total for you.

Move the figure into the plan

Copy hands over the digits alone, which a spreadsheet column or a roadmap field accepts without complaint. Ctrl + C over a selection inside the field strips the grouping the same way.

Dividing by 7 gives calendar weeks, never working weeks. Forty-five working days is nine weeks on a wall calendar, not the 6.43 the arithmetic prints, because the tool has no idea which of your days anybody is at work.

Cadences Side by Side, in Both Kinds of Day

Common iteration patterns with the working days they contain, the calendar span they occupy and a typical ceremony load. Ceremony figures assume the usual proportional timeboxes — close to a full day of planning, review and retrospective for a month-long iteration, scaled down for shorter ones — plus a quarter-hour standup on each working day.

Cadence	Working days	Calendar days	Calendar weeks	Typical ceremony hours
One-week iteration	5	7	1 wk	about 5 h
Two-week iteration	10	14	2 wk	about 10 h
Three-week iteration	15	21	3 wk	about 14 h
Month-long iteration	20	28	4 wk	up to 20 h
Two weeks with one public holiday	9	14	2 wk	about 10 h
Two weeks across a two-day shutdown	8	14	2 wk	about 10 h
Five two-week iterations in one increment	50	70	10 wk	about 50 h
Six-week cycle plus two-week cooldown	40	56	8 wk	varies by cycle

The two holiday rows are the ones worth staring at. Neither shortens the calendar span by a single hour, yet one costs a tenth of the team's capacity and the other a fifth, while the ceremony load sits exactly where it was. That is the arithmetic behind an iteration that "felt busier than usual" without anyone being able to say why, and it is the argument for setting a commitment from available working days rather than from the week count printed on the board.

How the Converter Earns Its Place in Planning

A day figure and a week figure in view together

Nothing has to be submitted; the second box tracks the first as it is typed, which is what makes it usable in the middle of a refinement session rather than after one.

Type the week count and get the days back

Both fields take input, so a target expressed in weeks resolves to a day total without touching the swap control or restarting the sum from the other end.

Fractions of a week are not rounded away

Up to eight decimals are kept, so 0.42857143 stays visible instead of becoming a friendly half, which matters when several such fragments are about to be added together.

Paste the number into a planning sheet

What lands on the clipboard is a bare numeral with no unit and no grouping, so a formula cell treats it as a number rather than as text it refuses to sum.

Questions Teams Ask During Sprint Planning

Why is a ten-day sprint two weeks long?

Because the ten refers to days the team is at a desk, and the calendar has to supply four more to accommodate two weekends. Ten working days at five per week is exactly 14 d of wall-clock span, which divides cleanly into 2 wk. Say "ten days" outside the team and a listener will divide by seven, land near a week and a half, and write down a date that is three days early. The habit worth adopting is naming the unit every time: ten working days, two calendar weeks, both numbers sitting in the plan side by side.

Should we run a two-week or a three-week cadence?

Look at the ceremony share before anything else. A fortnight gives roughly 10 h of scheduled events across 10 working days; three weeks gives around 14 h across 15, so the proportion of the box spent in a meeting drops noticeably as it gets longer. Against that, feedback arrives a third less often and a mid-iteration surprise has more room to hide. Teams with a stable backlog and heavy coordination costs tend to prefer three weeks; teams still learning their domain usually get more out of the shorter loop, even though it costs them more meeting time per delivered day.

What does velocity per calendar week tell me that velocity per sprint does not?

It makes two cadences comparable. Thirty points a fortnight and 42 per three-week box look unrelated until each is divided by its calendar weeks, at which point they are 15 and 14 — near enough identical throughput. That is the figure to reach for when a team changes its iteration length and everybody panics at the falling total, and it is also what a forecast needs, since anyone asking about a date is asking in weeks. Keep the per-iteration number for the team's own commitment conversation and the per-week number for anything that leaves the room.

A public holiday lands inside the next sprint — do we shorten the sprint?

Almost never. The calendar span is unchanged at 14 d, the ceremonies still have to happen, and moving the boundary breaks a rhythm that every downstream dependency has learned to expect. What changes is capacity: nine working days instead of ten is a tenth less, so the commitment should drop by about a tenth, and two holidays in one box take it to a fifth. Adjust what goes in, leave the dates alone, and record the reduced day count somewhere visible so the trend line does not look like a regression three months later.

How do I turn an estimate given in working days into a delivery date?

Three steps, in order. Scale the working days to calendar days by multiplying by seven fifths, so 30 becomes 42. Convert that span to weeks, giving 6 wk. Then add the days nobody counted: known holidays, leave already booked, and the share of each iteration that ceremonies consume, which on a fortnightly cadence is close to a day and a quarter per person. A 30-working-day piece of work realistically occupies seven to eight calendar weeks for one person, and that is before anybody gets pulled onto something urgent.