Purpose

Produce a clear, scannable sprint brief that every team member — engineer, designer, PM — can read in under three minutes and understand exactly what we're doing and why.

Required Inputs

Sprint name and number
Sprint goal (1-2 sentences)
Ticket list with owners
Known dependencies or blockers
Carry-over items from previous sprint

Process

Read sprint goal and check it's specific and measurable — flag if it's too vague
Group tickets by theme or feature area
Identify the critical path — which tickets must complete for the sprint goal to be met?
Flag risks: tickets with unclear acceptance criteria, missing designs, unresolved dependencies
Note carry-over items and whether they affect this sprint's goal

Output Format

Sprint [Number] Brief — [Dates]

Purpose

Produce a clear, scannable sprint brief that every team member — engineer, designer, PM — can read in under three minutes and understand exactly what we're doing and why.

Required Inputs

Sprint name and number
Sprint goal (1-2 sentences)
Ticket list with owners
Known dependencies or blockers
Carry-over items from previous sprint

Process

Read sprint goal and check it's specific and measurable — flag if it's too vague
Group tickets by theme or feature area
Identify the critical path — which tickets must complete for the sprint goal to be met?
Flag risks: tickets with unclear acceptance criteria, missing designs, unresolved dependencies
Note carry-over items and whether they affect this sprint's goal

Sprint Brief

Purpose

Required Inputs

Process

Output Format

Sprint [Number] Brief — [Dates]

Sprint Brief

Purpose

Required Inputs

Process

Output Format

Sprint [Number] Brief — [Dates]

Things Mac

Trello

Production Scheduling

Jira Integration

Production Scheduling

Cost Aware Llm Pipeline