Back to the Playbook
DefineDE-13
Prepare sprint
Propose a realistic sprint that advances the objectives while respecting capacity and dependencies across teams.
Product statusAvailable now
Context in6 required inputsReady backlog · Priorities and objectives · Estimates
TransformationProduct Manager + Product Agent + Architecture AgentAtlassian · Estimate Feature · Code Analysis
OutcomeProposed sprint scope with rationale, dependencies and risks.Artifact: Sprint
Owner
Product Manager
Human + Agent
Participants · Agents
EngineerProduct AgentArchitecture Agent
Trigger
Before sprint planning.
Required context
JiraReady backlogProduct BrainPriorities and objectivesJiraEstimatesFilesTeam capacityCodeDependencies from Jira and codeJiraCurrent sprint status
Optional context
JiraCarry-over riskJiraIncidentsFilesCalendar constraints
Skills
AtlassianEstimate FeatureCode Analysis
Activity steps
- 1Filter Ready items and rank against the objectives.
- 2Account for capacity and cross-team dependencies.
- 3Propose the sprint scope and epic assignments.
- 4Flag trade-offs and risks.
Output
Proposed sprint scope with rationale, dependencies and risks.
Artifacts
Creates: Sprint
Updates: Jira story
What good looks like
- Capacity-aware.
- Linked to the objectives.
- Dependencies from the code are respected.
- Trade-offs are explicit.
Quality gate
The team commits during sprint planning.
Destination
Jira
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Deep dives from the AI PM Lab
Articles that explain the thinking behind this Activity.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.