DO THIS EXERCISE
Create a “Scrum Event Brief” Prompt
Objective
Design a prompt that:
-
Accepts structured inputs
-
Produces a facilitation plan
-
Is usable across Sprint Planning, Review, Retro, or Refinement
-
Produces consistent output every time
Step 1: Define the Required Inputs
Your prompt should require:
-
Event Type (Planning, Review, Retro, etc.)
-
Sprint Context (Goal, capacity, risks, team state)
-
Agenda Constraints (timebox, participants, remote/in-person)
-
Desired Outcomes (decisions, artifacts, alignment level)
This prevents vague outputs.
Step 2: Define the Required Output Structure
Force structure.
Your output should include:
-
Event Objective
-
Timeboxed Agenda
-
Facilitation Tactics
-
Questions to Ask
-
Risk Signals to Watch
-
Decision Points
-
Artifacts to Capture
-
Follow-Up Actions
Structure is what makes it trustworthy.
Step 3: Your Reusable “Scrum Event Brief” Prompt Template
Copy and adapt this:
PROMPT TEMPLATE
You are an experienced Scrum Master facilitating a Scrum event.
INPUT
Event Type: {event type}
Sprint Context: {goal, capacity, constraints, risks, team maturity}
Agenda Constraints: {timebox, participants, format}
Desired Outcomes: {decisions, alignment, artifacts}
TASK
Create a structured facilitation plan.
OUTPUT FORMAT
-
Event Objective (1–2 sentences)
-
Recommended Agenda with time allocations
-
Facilitation approach (techniques and flow)
-
Key questions to ask
-
Risks or dysfunction signals to monitor
-
Decision checkpoints
-
Artifacts to capture
-
Follow-up actions
Ensure the plan is practical, concise, and suitable for a working Scrum team.
Step 4: Test It Immediately
Use this sample input:
Event Type: Sprint Planning
Sprint Context: New team, unclear backlog refinement, 2-week sprint
Agenda Constraints: 2 hours, remote
Desired Outcomes: Sprint Goal + committed backlog
Run the prompt.
Refine it until:
Why This Matters
You are not automating thinking.
You are standardizing:
-
Preparation discipline
-
Facilitation clarity
-
Decision hygiene
That is leverage.