DocsSprintsSprint Planning

Sprint Planning

Sprint planning is where your team decides what to work on next. Takonaut gives you the tools to create sprints, fill them with the right tasks, and manage the full lifecycle from start to completion.

Creating a Sprint

To create a new sprint, navigate to the Sprints page for your project and click Create Sprint. You’ll need to provide:

  • Name — a label for the sprint (e.g., “Sprint 14” or “Onboarding Revamp”).
  • Start date — when the sprint begins.
  • End date — when the sprint ends. The date picker calculates the duration automatically.
  • Goal — a one-line description of what the team aims to deliver. This keeps the sprint focused and gives stakeholders a quick summary.

The sprint is created in the Planning state. You can take as long as you need to add tasks and refine scope before starting it.

Adding Tasks to a Sprint

There are two ways to populate a sprint with tasks:

  • From the backlog — open a task that isn’t assigned to any sprint and set its sprint field. You can also drag tasks from the backlog into the sprint view.
  • Create new tasks — create tasks directly within the sprint. The sprint field is pre-filled automatically.

Tasks can belong to only one sprint at a time. If a task is already in another sprint, you’ll need to remove it from that sprint first.

Auto-Scheduling

Takonaut includes an AI-powered auto-scheduler that can assign tasks to sprint days based on priority, story points, dependencies, and team member availability.

To use it, open a sprint in the Planning state and click Auto Schedule. The scheduler will:

  • Distribute tasks across the sprint timeline.
  • Respect task dependencies — blocked tasks are scheduled after their blockers.
  • Balance workload across team members based on their capacity.
  • Prioritize higher-priority tasks earlier in the sprint.

You can review and adjust the suggested schedule before accepting it. Auto-scheduling is a suggestion, not a commitment — you remain in control.

Story Point Capacity

During planning, it helps to know how much work the team can handle. The sprint planning view shows:

  • Total capacity — the combined story points your team can deliver, based on historical velocity and team size.
  • Planned points — the sum of story points for all tasks currently in the sprint.
  • Remaining capacity — how many more points you can add before exceeding the team’s bandwidth.

This prevents over-commitment. If planned points exceed capacity, the UI flags it so you can trim scope before starting the sprint.

Moving Tasks Between Sprints

Sometimes priorities shift and tasks need to move. To move a task to a different sprint:

  1. Open the task.
  2. Change the Sprint field to the target sprint.
  3. Save.

You can also move tasks in bulk from the sprint detail view by selecting multiple tasks and choosing Move to Sprint from the actions menu. This is especially useful when completing a sprint and redistributing unfinished work.

Starting a Sprint

When planning is done and the team is aligned, click Start Sprint to activate it. This changes the sprint state from Planning to Active and:

  • Locks the start date to today (if it hasn’t already passed).
  • Filters the project board to show only this sprint’s tasks.
  • Sends a notification to all project members that the sprint has started.

Only one sprint per project can be active at a time. If another sprint is already active, you’ll need to complete it first.

Completing a Sprint

When a sprint reaches its end date — or the team has finished all planned work — click Complete Sprint. You’ll be prompted to decide what happens to incomplete tasks:

  • Move to next sprint — unfinished tasks are automatically assigned to the next sprint in the Planning state. If no next sprint exists, you’ll be prompted to create one.
  • Move to backlog — unfinished tasks are removed from the sprint and returned to the project backlog for re-prioritization.

After completion, the sprint is locked. Its tasks, progress, and velocity data are preserved for historical reference and reporting.

Delivery Manager Assignment

Each sprint can have a Delivery Manager (DM) assigned to it. The DM is responsible for overseeing the sprint’s progress, unblocking the team, and ensuring the sprint goal is met.

To assign a DM, open the sprint and select a team member from the Delivery Manager dropdown. The DM will:

  • Receive additional notifications about sprint progress and blockers.
  • Be highlighted on the sprint detail page so the team knows who to go to.
  • Have access to DM-specific tools like nudging team members and reviewing sprint health.

Sprint Standup

During an active sprint, team members submit daily standups to report progress on their sprint tasks. Each standup captures:

  • What I did yesterday — tasks worked on.
  • What I’m doing today — planned work.
  • Blockers — anything preventing progress.

Standups are tied to the active sprint, giving the DM and team leads a daily pulse on how the sprint is tracking. See the Standups page for more details on the standup workflow.