Weekly Planning Meeting
Use when asked to plan or run a weekly team planning meeting — reviewing last week's progress and committing to this week's priorities — as the short-cycle execution counterpart to yearly-planning-meeting's annual strategy setting, and distinct from a daily standup's much shorter, status-focused check-in (see agile-standup).
A weekly planning meeting reviews the past week's progress and commits the team to the coming week's priorities — the short-cycle execution layer that translates Yearly Planning Meeting's annual objectives into concrete, near-term work, at a longer horizon and deeper planning depth than a daily Agile Standup check-in.
What it typically covers
- Review — what actually got done last week against what was planned, and why any gap exists — genuine review, not just a completion tally (see Agile Reflection for the deeper version of this same discipline at a less frequent cadence).
- Priority-setting — the specific, concrete work committed to for the coming week, tracing back to the current quarter's or year's objectives (see Objectives and Key Results) rather than an arbitrary task list.
- Capacity check — realistic assessment of what the team can actually take on given current availability, avoided-conflicts, and known constraints — committing to more than capacity allows sets the next week's review up to repeat the same gap.
- Dependency and blocker surfacing — anything the team needs from outside itself to hit this week's commitments, flagged now rather than discovered mid-week.
Why this cadence, specifically
A week is long enough to plan meaningful, multi-step work (unlike a daily standup's next-24-hours scope) but short enough to catch drift from plan quickly and adjust — a monthly or quarterly-only planning cadence leaves too much room for a team to head in the wrong direction before anyone notices.
Relationship to other planning cadences
Sits between Yearly Planning Meeting (annual strategy, budget, top-level objectives) and Agile Standup (daily, brief status/blocker check-in) — the weekly cycle is where annual/quarterly objectives actually get broken into work a team commits to and executes against week by week.
Common pitfalls
- Planning without reviewing — committing to a new week's work without first honestly checking what happened to last week's commitments repeats the same estimation mistakes indefinitely.
- No connection to higher-level objectives — a weekly plan that's just a task list, untethered from the quarter/year's actual goals, can keep a team busy without making real progress on what matters.
- Chronic over-commitment — planning more work each week than the team's actual track record supports, rather than adjusting the plan to match demonstrated capacity.
- Treating it as a status meeting rather than a planning one — if the meeting only reports what happened with no forward commitment, it's duplicating what a Agile Standup or async update already covers, without adding real planning value.
Learn more
- Yearly Planning Meeting for the longer-horizon strategic planning this meeting executes against.
- Agile Standup for the much shorter, daily counterpart.
- Objectives and Key Results for connecting weekly commitments to actual strategic objectives.