BACK

Engineering the Agile Stack: Notion Scrum Master

Run your sprint board from chat. Your Mind handles the reads and writes in Notion.

01. Context: The Scrum Engine

This Skill automates:

  • Task transitions between sprint columns.
  • Weekly sprint rollovers.
  • Status reporting across the backlog.

Prerequisites:

  • A Notion workspace with a Scrum Master database (Tasks, Sprints).
  • The Notion App and Notion Scrum Master Skill equipped on your Mind.
  • OAuth authorized so the Mind can read and write on your behalf.

02. Heartbeat Strategy: Logic Over Logistics

Treat your Scrum Master board as state. Every row is a task the Mind can read, update, or move. Tell it the outcome you want and it runs the database operations. That beats clicking through rows yourself.

03. Project Structure: The Integration Workflow

  1. Initialize. Equip the Notion Scrum Master Skill and finish the OAuth handshake.
  2. Query the backlog. Ask the Mind to pull every task not marked Done.
  3. Update and transition. Ask the Mind to move tasks between columns or into the next sprint.

04. Prompt Templates: Steering the Scrum

Template: Moving Tasks Across the Board

  • Weak: "Move my task to Done in Notion."
  • Strong: "Find the task 'Final Boss Art Assets' in the Scrum Master database. Change its Status to Done. Confirm the update before replying."

Template: Status Reporting

  • Weak: "Tell me what's due today in Notion."
  • Strong: "List every task in the Scrum Master database due today that isn't Done. Return titles with their current sprint as a bulleted list. Reply 'Backlog clear' if nothing matches."

05. Example: Automating the Weekly Sprint Rollover

The Skill earns its keep on recurring routines. Friday rollover runs as one prompt:

  1. Close the sprint. List every task still In Progress or Blocked.
  2. Carry work forward. Roll unfinished tasks into next week's sprint.
  3. Archive what shipped. Move Done tasks out of the active view and stamp a completion date.
  4. Post a recap. Summarize shipped work, carryovers, and persistent blockers for the team channel.

The Mind handles reads, writes, and the summary. You decide what the next sprint focuses on.