What are we building this sprint?
Start with clarity. What work are we committing to? Be specific enough that everyone—human teammates and AI collaborators—understands the scope.
💡 Multi-Mind Insight:
When we align on what we're building at the start, we're not just setting expectations for the team—we're creating shared context that helps everyone (including AI teammates) understand priorities, make decisions, and stay focused throughout the sprint.
What do we call this iteration?
What features, fixes, improvements, or initiatives are we taking on?
Example: "We're launching the new user dashboard with real-time metrics, fixing the top 3 bugs from last sprint, and completing the API documentation for external partners."
Why does this matter?
Purpose drives commitment. When we understand why this work matters, we make better decisions about tradeoffs and stay motivated when things get tough.
What customer pain are we solving? What business goal are we advancing? Why now?
Example: "Customer feedback shows they're struggling to understand their usage patterns. The dashboard gives them visibility they've been asking for. The bug fixes are blocking three enterprise customers. The API docs unlock our partner ecosystem."
What does success look like?
Define "done" before we start. What outcomes tell us we succeeded? How will we measure impact?
💡 Multi-Mind Insight:
Clear success criteria help everyone—human team members and AI collaborators—know what to optimize for. When we define success up front, we make better decisions about scope, quality, and tradeoffs throughout the sprint.
What specific outcomes or metrics tell us we succeeded?
Example: "Dashboard launches to 100% of users with <500ms load time. All three critical bugs are fixed and verified. API docs are published and 3 partners can integrate independently without support."
Who's involved?
Context about the team helps everyone understand roles, capacity, and collaboration patterns.
Who's leading? Who's building? Who needs to be consulted? Any AI teammates in the mix?
Example: "Sarah (PM) leading, Marcus and Jen (Engineering), Lisa (Design), AI assisting with documentation. Need sign-off from Alex (Product Lead) before launch."
Any constraints or concerns?
Surface blockers early. What might slow us down? What dependencies exist? What keeps us up at night?
Time limitations? Technical blockers? External dependencies? Team capacity concerns?
Example: "Marcus is out Thu-Fri for conference. Dashboard depends on metrics API finishing first (Dev Ops team owns). Holiday week means lighter support capacity."
Sprint Kickoff Summary
Here's our shared understanding for this sprint. Download this to share with the team, paste into your project wiki, or reference throughout the sprint.
Sprint/Cycle
What We're Building
Why This Matters
Success Looks Like
Team & Roles
Constraints & Concerns