The weekly ritual that decides if the squad works or not

Daily isn’t enough. Monthly retro isn’t enough. What separates a squad that ships from a squad that improvises is a 45-minute weekly ritual with 5 specific questions. Revin runs this ritual across all clients. Here is how it works.

Por Victhor Araújo

Victhor Araújo

A 15-minute daily is mechanical. Sprint review is ceremony. Monthly retro arrives late. What actually separates a squad that ships from a squad that improvises is a less famous and much more decisive ritual: the weekly review.

Revin runs a 45-minute weekly review with every client from day 1. It's not an update meeting — it's a structured checkpoint of 5 questions that unblocks sprints before they catch fire on Friday. Squads without this ritual are always reacting; squads with it are always anticipating.

For PMs, tech leads, and founders who feel engineering is always firefighting on Friday — and want to see how the right weekly ritual eliminates 70% of that.

5 questions in 45 minutes: the checkpoint that unblocks sprints before they catch fire

🗓️ The 5 questions of the weekly review

Every Wednesday, 45 minutes, fixed calendar, tech lead facilitates. Five questions in order:

1. "What was supposed to be done by Wednesday and still isn't?"

Defines the gap between plan and reality mid-sprint — not on Friday. Senior squads still have 2 days to correct; squads without ritual find out too late.

2. "Which ticket has been stalled for more than 36h?"

A stalled ticket signals invisible blocker: waiting on review, decision, environment. The ritual surfaces it — and the tech lead unblocks right there.

3. "What new technical decision was made and not documented?"

Almost every week some dev decided something alone that becomes critical context for the team. Without the ritual, it becomes tribal knowledge; with it, it becomes a written ADR.

4. "What will catch fire next week if we do nothing today?"

Forecast question. Identifies emerging risk: late dependency, forgotten feature flag, unstable external integration. Senior squads anticipate; reactive squads find out when it blows up.

5. "What question will the external stakeholder probably ask on Friday?"

Mirrors the client's angle. The squad rehearses the answer before the question lands. Result: sprint review with no surprise, stakeholder satisfied.

A squad without a weekly ritual is a reactive squad — every Friday is a surprise

🚧 What happens in squads WITHOUT this ritual

• Daily becomes "ticket status" with no action — everyone says "I'm working on X" and nothing unblocks.
• Sprint review is the first moment the client sees what was NOT delivered — 2 days before the deadline.
• Monthly retro catalogs what went wrong, but the specific sprint already passed.
• Tech debt and implicit decisions stack up invisibly for 4-8 weeks until they become a forced refactor.

🎯 Why 45 minutes (not more, not less)

Less than that becomes an extended daily — no depth to answer the 5 questions. More than that becomes a meeting nobody wants — and disappears from the calendar in 3 weeks. 45 minutes with a locked agenda fits the week and respects the squad's focus.

Tech lead facilitates, 2-3 seniors present, client PM invited (not required). Output: a list of 5-8 specific actions with owner and deadline by Friday. No minutes; the document is the updated tickets.

📢 Want to implement this ritual in your current squad? Book a Diagnostic Sprint — Revin delivers the template + facilitates the first month of weekly reviews until it becomes habit.

🎯 Conclusion: the weekly ritual is the difference that matters

Daily, sprint review, and retro are commodities — every squad does them. The weekly review is the ritual few operate, and the one that most separates serious managed squads from generic agencies. Revin ships this ritual encapsulated across all contracts; not a favor, just process.

📢 Revin runs this weekly review with every client since 2023. See the cases to see how this shifts delivery predictability.