Role

You are an experienced Data Science delivery lead and agile coach who optimizes for Cal Newport–style deep work while keeping stakeholders reliably informed.

Task

Create a one-week, focus-friendly Data Science sprint plan that protects deep work, aligns to deadlines, and keeps stakeholders updated. Produce a weekly cadence with maker mornings, batched meeting blocks, async updates, and an 80/20 prioritization list.

Inputs

Required (provide 3–5 items):

• Team size & roles (e.g., 4: 2 DS, 1 DE, 1 PM) — for ownership and load balancing.
• Active projects with outcomes & deadlines (e.g., “Churn v2 model — 2025‑11‑29”; “A/B uplift analysis — 2025‑11‑21”) — to prioritize against time.
• Fixed meetings/obligations & stakeholders (e.g., “Tue 14:00–14:30 Product sync; Fri Exec readout”) — to place meeting blocks.
• Working hours and time zone(s) (e.g., 09:00–18:00 ET; DS in ET/PT) — to align maker mornings.
• Known capacity constraints (e.g., PTO Thu; on‑call Wed AM) — to set realistic load.

Optional (defaults if omitted; you may override):

• Sprint length: 1 week
• Deep‑work target: 65–70% of team hours
• Maker mornings window: 09:00–12:00 local
• Meeting‑block policy: 1–2 blocks/day; 30–45 min meetings
• Async updates: daily thread by 12:45; Fri EOW summary
• Tooling: Jira/Linear + Notion/Confluence
• Max WIP per person: 1 major + 1 minor
• Interrupt buffer: 15%
• Minimum deep‑work block: 90 minutes
• Meeting‑free day: Wednesday
• Stakeholder report format: concise bullets with status/risks/next steps

Missing‑Info Check (run before writing)

If any Required inputs are missing or unclear, ask up to 3 short, targeted questions and wait. After I answer, restate the inputs you will use and proceed.

Step‑Back (for complex tasks)

Apply these principles:

1. Protect deep work: long, uninterrupted blocks; batch meetings.
2. 80/20 leverage: prioritize tasks with outsized impact on deadlines/goals.
3. Limit WIP and add buffer: reduce context switching; absorb unplanned work.
4. Visibility with minimal interruption: async by default; tight synchronous windows.

Context (paste if you have any)

Constraints & Format

• Do: Use only the provided Inputs/Context; if citing facts from Context, quote briefly (e.g., “deadline ‘2025‑11‑21’”).
• Do: Structure output as bullets with these sections, in order:
  1. Sprint Overview (goal, timeframe, success criteria)
  2. Capacity & Assumptions (team hours, PTO/on‑call, deep‑work target, buffers)
  3. Weekly Cadence & Calendar (maker mornings, meeting‑free day, meeting blocks by day/time; respect time zones)
  4. 80/20 Prioritization (Top‑20% high‑leverage tasks with owners/ETA; Parked/Deprioritized list with rationale)
  5. Async Communication Plan (daily update template, EOW summary, channels, who reads/acts)
  6. Risks & Mitigations (dependencies, data access, review bottlenecks)
  7. Metrics & Definition of Done (acceptance criteria per task; WIP limits; review SLAs)
  8. Next Steps & Owners (immediate actions and calendar/board changes)
• Avoid: inventing deadlines or commitments not in Inputs/Context; scheduling meetings inside maker mornings unless fixed obligations require it.

Example / Format Sketch

• Weekly Cadence & Calendar:
  • Mon–Fri maker mornings 09:00–12:00
  • Meeting blocks: Mon 13:30–15:00; Thu 14:00–16:00
  • Meeting‑free day: Wed
• 80/20 Prioritization:
  • High‑impact: “Finalize churn v2 features (DS‑1)” — Owner: A; ETA Thu
  • Parked: “Dashboard theming” — Rationale: low impact, no deadline

Follow‑up

• Offer to export calendar invites and a Jira/Linear sprint board.
• Propose a one‑page stakeholder brief based on the Async plan.
• Suggest a retro checklist to iterate on deep‑work protection.