Creating and Managing Sprints

Overview

Sprints are time-boxed periods for completing work. They help you plan and focus on specific goals.

Sprint Statuses

• Planning: Sprint is being set up, issues being added
• Active: Sprint is in progress (only one can be active)
• Completed: Sprint is finished

Creating a Sprint

From MCP:

panelTodo_createSprint({
  name: "Sprint 1",
  startDate: "2024-01-15",
  endDate: "2024-01-29"
})

Adding Issues to a Sprint

// When creating an issue
panelTodo_addIssue({
  title: "Implement login",
  sprintId: "sprint-uuid"
})

// Move existing issue to sprint
panelTodo_moveIssueToSprint({
  issueId: "issue-uuid",
  sprintId: "sprint-uuid"
})

Starting a Sprint

When you're ready to begin work:

panelTodo_startSprint({ sprintId: "sprint-uuid" })

This changes the sprint status from "planning" to "active".

Completing a Sprint

panelTodo_completeSprint({
  sprintId: "sprint-uuid",
  moveIncomplete: true  // Moves unfinished issues to backlog
})

Listing Sprints

// All sprints
panelTodo_listSprints()

// Filter by status
panelTodo_listSprints({ status: "active" })

Sprint Workflow

1. Plan: Create sprint, add issues
2. Start: Begin the sprint
3. Work: Complete issues during the sprint
4. Review: At sprint end, review completed work
5. Complete: Close sprint, move incomplete issues

Best Practices

• Fixed duration: 1-2 weeks works well
• Scope carefully: Don't overcommit
• One active sprint: Focus on current work
• Review velocity: Track how much you complete