Our First Ramadan in Dubai Cost Us 4 Weeks of Roadmap: the 7 Steps I Run Every Year Now

A small team planning around a table with sticky notes and a laptop, illustrating the sprint and capacity replanning a Dubai engineering team does before reduced Ramadan working hours begin
Bryan

Bryan

Delivery & Offshore Teams Expert ยท November 20, 2026 ยท 11 min read

TL;DR

  • โ€ขThe rule: the Ministry of Human Resources and Emiratisation announces a two-hour daily reduction in normal working hours for private sector employees during Ramadan, with no corresponding salary reduction.
  • โ€ขCheck your entity first: onshore, reporting describes the reduction as applying to private sector employees regardless of faith. In the DIFC and ADGM, published commentary indicates a narrower scope. A mixed engineering team needs this answered before anything else.
  • โ€ขThe arithmetic nobody does: two hours a day across eight engineers for a month is roughly eight engineer weeks. Teams that do not subtract it read the result as an execution failure.
  • โ€ขThe 7 steps: confirm the rule, convert it to capacity, publish the hours, re-cut the sprint, rebuild the on-call rota, freeze risky releases only, then plan Eid and the return week as one block.

The first Ramadan I managed an engineering team in Dubai, I did something that looks obviously stupid written down: I left the sprint commitments exactly where they were. I knew the working day was two hours shorter. I had read the circular. I simply never converted that into a number and subtracted it from anything. We came out of the month roughly four weeks behind on a roadmap that had looked comfortable in February, and I spent the first week after Eid explaining a delivery miss that was arithmetic rather than performance.

This is the method I have run every year since. It is deliberately boring, it takes about two weeks of preparation, and most of the work happens before the month starts. The steps are in order because the order matters: step one changes who the rest of the plan applies to, and getting it wrong invalidates everything after it.

What the Rule Actually Says

Each year the Ministry of Human Resources and Emiratisation publishes a notice reducing normal working hours for private sector employees across the UAE by two hours per day during Ramadan. Its February 2026 notice is the current reference point, and commentary ties the underlying obligation to Federal Decree-Law No. 33 of 2021 and Cabinet Resolution No. 1 of 2022.

Three consequences matter for an engineering budget. The reduction comes with no corresponding reduction in salary. Hours worked beyond the reduced schedule are generally treated as overtime. And the scope depends on where your entity sits, which is the part that trips up technology companies specifically, because so many of them are in free zones.

On the onshore federal rule, reporting describes the reduction as applying to private sector employees generally, regardless of faith. Inside the free zones the published position is narrower: commentary from employment practitioners indicates that in the DIFC reduced hours apply to Muslim employees, and in the ADGM to Muslim employees who observe the fast. Rules are amended and summaries age, so treat the paragraph you are reading as the reason to ask the question rather than as the answer to it. Confirm the current position for your own entity before you publish a schedule to your team.

๐Ÿ’ก Our Expert Take

The free zone distinction is the most expensive detail in this whole article, and not for payroll reasons. A fifteen-person engineering team in a DIFC company where the reduction applies to some engineers and not others has a visible two-tier working day inside one standup. Handled with a written policy published in advance, it is a non-event. Handled by letting each engineer work it out with their lead individually, it becomes the thing people discuss in private channels for a month, and it surfaces in exit interviews a year later as something else entirely.

Step 1. Confirm Which Rule Applies to Your Entity

Before any planning, answer one question in writing: does the reduction apply to every member of this engineering team, or to some of them?

Ask whoever owns payroll and employment compliance, name the entity, and get the answer in a message you can forward rather than in a corridor conversation. If you operate more than one entity, which is common when part of the team sits in a free zone and part sits onshore, you need the answer per entity. Write down the date you asked, because the question is worth re-asking annually rather than assuming last year holds.

Two follow-up questions save trouble later. First, what counts as the normal working day you are reducing from, since a company on a nine-hour day with a one-hour unpaid break is starting from a different place than one on eight. Second, how does your overtime policy interact with the reduced schedule, because engineers who stay late to finish a deploy are generating a payroll obligation whether or not anyone is tracking it.

Step 2. Convert the Reduction into a Capacity Number

This is the step I skipped in my first year, and it takes twenty minutes.

Two hours off a standard eight-hour day is a quarter of the day. For a team of eight engineers across roughly twenty working days, that is in the region of 320 hours, or close to eight engineer weeks, before you subtract any annual leave. Do the calculation with your real team size, your real working pattern and your real holiday calendar, and produce a single number.

Then do the thing that actually matters: hand that number to whoever owns the roadmap, in writing, before commitments are made for the quarter. Not as a warning, as a subtraction. The sentence that works is some version of this: the team has this many engineer weeks available in this period instead of the usual figure, so here is what fits and here is what moves.

If your planning runs on points rather than hours, convert it once and keep the conversion. If you have historical velocity from previous years, use it in preference to the arithmetic, because real throughput in a shorter month is usually a little worse than the pure hours suggest, for reasons covered in step four. Our method for engineering headcount planning in Dubai uses the same approach of fixing the capacity figure before the commitment rather than after.

THE SUBTRACTION MOST TEAMS SKIP2 hoursper person, per dayร—8 engineersexample team sizeร—20 daysworking days in month=320 h~8 eng weeksIF YOU DO NOT SUBTRACT ITSame commitment, shorter month, predictable miss, read afterwards as a performance problemIF YOU DOScope cut in advance, roadmap owner informed before committing, no retrospective argumentExample figures. Run the calculation with your own team size, working pattern and leave calendar.

Step 3. Publish the Actual Daily Hours in Writing

Decide the specific times and send them to the whole team at least a week before the month begins. Vague guidance produces a month of private negotiation.

Three things belong in that message. The start and finish times, as clock times, not as a number of hours. A core overlap window during which everyone is reachable, which is what protects meetings, pairing and reviews from dissolving. And the position on remote work for the month, because this is when the question arrives whether or not you have answered it.

One practical note on the core window. Reduced hours tend to pull the start of the day later and the finish earlier, and different people shift in different directions. If you do not name an overlap, you can end up with a nominally seven-hour day in which two engineers overlap for three hours. Naming four hours of guaranteed overlap costs nothing and preserves most of the collaboration.

If part of your team sits outside the UAE, say explicitly what changes for them and what does not. A distributed team reads silence as instruction, and the version of this that goes wrong is a colleague in another timezone quietly keeping the old schedule and wondering why reviews take two days.

Step 4. Re-Cut the Sprint Instead of Compressing It

You have a capacity number from step two. Now reduce scope to match it, rather than keeping the commitment and hoping.

Compression is the default failure and it is seductive, because for the first week it appears to work. People skip breaks, shorten standups, defer reviews. What actually happens is that the invisible work goes first: code review depth, test coverage, documentation, the conversation where someone says this design will not hold. That work does not disappear, it relocates to the week after Eid as defects, and the month looks fine right up until it does not.

Two adjustments make the shorter day work better than the arithmetic predicts:

  1. Move deep work to the first half of the day. Fasting changes when people are at their sharpest, generally earlier. Put design discussions, debugging and anything requiring sustained concentration in the morning block, and put status, administration and lighter review work later.
  2. Cut the number of parallel work streams, not the size of each one. A team with four things in flight and twenty five percent less time should run three things, not four smaller things. Context switching is the first thing a shorter day cannot absorb, and reducing stream count is the cheapest capacity you will find all month.

Protect code review explicitly, with a named reviewer per stream and an expected turnaround that accounts for the shorter overlap window. Review is the first thing to slip and the most expensive to recover.

๐Ÿ’ก Our Expert Take

The single highest-return change I have made to this plan over the years was cutting stream count rather than story size. In one team we went from five concurrent initiatives to three for the month and finished more total work than the previous year on a longer calendar. Nothing about the engineers changed. We simply stopped asking people with six hours of focus time to hold five contexts in their head. It is also the change with the least political cost, because you are not telling anyone their project is cancelled, only that it starts after Eid.

Step 5. Rebuild the On-Call Rota for Shorter Days

A shorter working day means a longer uncovered window, and the rota you were running last month assumes coverage you no longer have.

Work through four things. The handover times, which have moved and need to be restated. The acknowledgement expectation outside working hours, which should be explicit rather than assumed. The escalation path, including who is second in line when the first responder is unreachable at iftar. And compensation or time back for out-of-hours work, agreed in advance, since this is exactly the month when goodwill gets quietly spent.

If you run a dedicated or partly offshore team, this is also the moment to re-read the escalation matrix rather than discover its gaps during an incident. We keep a worked example in the on-call escalation matrix for a dedicated team in Dubai, and the structure transfers to any stack.

One concrete suggestion that has saved us twice: for the duration of the month, put two names on every on-call shift rather than one, with the second person explicitly described as backup rather than as a second responder. It costs almost nothing in practice, because the backup is rarely called, and it removes the failure mode where a single unreachable phone becomes a thirty-minute delay on a production incident.

Step 6. Freeze Risky Releases and Name the Exceptions

Most teams do one of two unhelpful things here. They freeze everything, or they freeze nothing and rely on judgement that is harder to exercise on a shorter day with thinner review coverage.

The workable version is a short written policy with three parts. What continues: routine low-risk changes, behind flags where possible, shipped early in the day rather than late. What waits: anything touching payments, authentication, data migration or a third-party integration you do not control. How to get an exception: a named approver, a written reason, and a rollback plan, so that genuine urgency is not blocked by an informal freeze nobody ever wrote down.

The timing detail that matters most is to stop shipping anything meaningful in the last working hour of the day. On a shortened schedule that hour is much closer to the moment when the people who could help you debug it have gone, and a deploy at that hour is a bet on nothing going wrong.

Write the policy once, date it, and reuse it next year. The annual version of this conversation is otherwise held from scratch every time, usually in the week it is needed.

Step 7. Plan Eid and the Week After as One Block

The failure I see most often is a plan that stops at the end of the month. The Eid holiday and the return week are where an otherwise well-managed month gets undone.

Three things to settle in advance. First, who is covering across the holiday, agreed and staffed well ahead rather than negotiated the week before, since holiday dates are confirmed close to the time and everybody wants the same days. Second, a written catch-up order for the backlog, agreed before the month ends, so that the queue on return is not reordered by whoever is loudest on the first morning. Third, a deliberately light first week back: no major releases, no new initiative kickoffs, and the postponed work from step four starting in week two rather than on day one.

Then do one thing that takes half an hour and pays for itself annually. Hold a short retrospective specifically on the month, separate from your normal sprint retrospectives, and record what the real capacity turned out to be against your step two estimate. That number is the single most valuable input to next year, and it is the one nobody writes down. The structure we use for this is in our guide to the engineering retrospective, and the same discipline of recording the actual figure applies.

Short on capacity rather than on planning?

Sometimes the honest answer after step two is that the team is a person or two short of the commitment, and no amount of re-cutting fixes it. HireDeveloper.ae sources pre-vetted engineers for UAE employers, including engineers who have worked UAE schedules before and need no explanation of what the month involves. We will also tell you plainly when the better move is to cut scope rather than add a person mid-quarter.

Get started

The Two-Week Preparation Calendar

The steps above map onto a simple countdown. Everything in it is deliberately front-loaded, because none of it works as an in-month improvisation.

WHEN EACH STEP HAS TO HAPPEN14 days outSteps 1 and 2confirm the rule,fix the capacity number7 days outSteps 3 and 4publish hours,re-cut the sprint3 days outSteps 5 and 6rota rebuilt,release policy writtenbefore month endStep 7Eid cover andcatch-up order agreedTHE ONE STEP THAT CANNOT MOVEStep 1. Confirm scope per entity first. Every later step inherits that answer.Nothing here is an in-month improvisation. The month itself should contain no planning work.Record actual capacity against your estimate at the end. That figure is next year starting point.

๐Ÿ’ก Our Expert Take

After running this for several years, the part I would defend hardest is not the capacity arithmetic, it is publishing the hours in writing a week early. The arithmetic protects the roadmap. The written schedule protects the team from a month of small private negotiations, each of which is reasonable on its own and which collectively produce a team where nobody is quite sure when anyone else is working. Engineers are generally relaxed about a shorter month and considerably less relaxed about ambiguity, and the written note costs ten minutes.

FAQ: Ramadan Working Hours and Engineering Teams in Dubai

Are working hours reduced during Ramadan in the UAE private sector?

Yes. The Ministry of Human Resources and Emiratisation announces a reduction of normal working hours for private sector employees of two hours per day during Ramadan, and commentary ties the obligation to Federal Decree-Law No. 33 of 2021 and Cabinet Resolution No. 1 of 2022. The reduction does not come with a corresponding salary reduction, and work beyond the reduced schedule is generally treated as overtime. Free zone positions differ, so confirm the current rule for your own entity rather than assuming the onshore position applies to you.

Does the reduction apply to non-Muslim engineers on my team?

Onshore, reporting on the federal rule describes the reduction as applying to private sector employees generally, regardless of faith. Inside some free zones the scope is narrower: published commentary indicates that in the DIFC reduced hours apply to Muslim employees, and in the ADGM to Muslim employees who observe the fast. For a mixed engineering team this is the first thing to confirm and the first thing to put in writing, because an unexplained two-tier working day inside one standup causes more damage than the hours themselves.

How much engineering capacity does the month actually cost?

Two hours per person per working day is about a quarter of a standard eight hour day. For eight engineers over roughly twenty working days that is in the order of 320 hours, close to eight engineer weeks, before any leave. Run it with your own numbers. The error that costs money is not the arithmetic, it is failing to subtract the figure from the commitment and then reading the resulting shortfall as an execution problem in the retrospective.

Should we freeze deployments for the whole month?

Freeze risky releases, not all of them. A blanket freeze pushes a month of accumulated change into the week after Eid, which is the worst moment to ship a large batch into a team that is still returning. Write a three-part policy instead: routine low-risk changes continue and ship early in the day, anything touching payments, authentication, data migration or an integration you do not control waits, and there is a named approver with a written exception route for real urgency.

Run the plan, then hire against what is left

Work through steps one and two and you will know within an afternoon whether you have a planning problem or a staffing one. If it turns out to be staffing, we can help: we source pre-vetted engineers for UAE employers and we are straightforward about what is available and what is not. If you also need a hand with product scope, our guide to building an ecommerce app in Dubai covers the seasonal load planning that tends to collide with this month.

Lets get started