Sprints and reports

Without time boundaries, work expands forever. Sprints force a cadence: plan, execute, measure, adjust. They work the same whether humans or agents are doing the work. Each sprint close forces you to evaluate what got done, what is still pending, and what you learned. Without this discipline, projects drift.

A sprint is a time-boxed iteration within a board. It allows you to plan which work items will be completed in a given period, track progress, and generate reports at closing.

Key concepts

• Each board can have only one active sprint at a time.
• A sprint has a start date, end date, and a goal.
• The board's work items are associated with the active sprint.
• When a sprint is closed, a changelog and performance metrics are automatically generated.
• The history of previous sprints is preserved with their reports.

Creating a sprint

1. Access the board where you want to create the sprint.
2. Select New Sprint.
3. Complete the fields:

Field	Description	Required
name	Sprint name (e.g., "Sprint 14 - Auth & Permissions")	Yes
startDate	Start date	Yes
endDate	End date	Yes
goal	Sprint goal: what you want to achieve	No

4. Confirm the creation. The sprint becomes active immediately.

warning

Only one sprint can be active per board. If one is already active, you must close it before creating a new one.

Associating work items

Work items that are on the board when the sprint is active are part of the sprint. There is no explicit action to "associate" items with the sprint: all items present on the board during the sprint are counted.

This means that:

• New items created during the sprint are automatically included.
• Items moved to the board during the sprint are included.
• Items archived during the sprint stop being counted.

Preview of completed items

Before closing a sprint, you can preview which items are considered "done". Almirant identifies items that are in columns with the isDone = true role and presents them as completion candidates.

This lets you verify whether any items still need to be moved to the correct column before closing.

Closing a sprint

There are three closing modes, each for a different scenario:

1. Normal close

Standard close at the end of the planned period.

1. Access the board's active sprint.
2. Select Close Sprint.
3. Review the summary of completed vs. pending items.
4. Decide what to do with uncompleted items (move them to backlog or to the next sprint).
5. Confirm the close.

2. Ad-hoc close

Early close when you decide to end the sprint before the planned date. Useful when work needs to be replanned or objectives have changed.

1. Access the active sprint.
2. Select Close Sprint Ad-hoc.
3. Review and confirm. Pending items are handled the same way as in a normal close.

3. Close by date

Automatic close based on a specific date. Useful for sprints that end on a date different from the one originally planned.

1. Access the active sprint.
2. Select Close by Date.
3. Specify the cutoff date.
4. Items completed before that date are counted as finished.

Unfinished items

When closing a sprint, work items that are not in isDone columns are considered unfinished. You can:

• Move them to backlog -- Items return to the default column for re-prioritization.
• Include them in the next sprint -- Items remain in their current column and are counted in the new sprint.

Automatic changelog

When closing a sprint, Almirant automatically generates a changelog that includes:

• List of completed items, grouped by type.
• Summary of changes made during the sprint.
• Relevant notes extracted from items.

The changelog can be regenerated if needed using the regenerate_sprint_changelog tool.

Reports and metrics

Each closed sprint generates a report with the following metrics:

Metric	Description
Velocity	Number of items completed in the sprint
Distribution by type	Breakdown of completed items by type (epic, feature, story, task)
Distribution by priority	Breakdown by priority level (urgent, high, medium, low)
Distribution by assignee	What work each team member completed
AI cost	Total cost of AI sessions executed during the sprint
Comparison with previous sprints	Velocity and metrics trends compared to previous sprints

Reports include graphical visualizations and the ability to attach screenshots to document the state of the product at sprint close.

Sprint history

All closed sprints are preserved in the board's history. You can access any previous sprint to view:

• The report with metrics.
• The generated changelog.
• The work items that were part of the sprint.
• Attached screenshots.

For developers

For Developers

MCP tools

Tool	Description	Main parameters
list_sprints	Lists all sprints of a board	boardId
get_sprint	Gets the details of a sprint	sprintId
get_active_sprint	Gets the active sprint of a board	boardId
create_sprint	Creates a new sprint	boardId, name, startDate, endDate, goal
close_sprint	Closes the active sprint (normal)	sprintId
close_sprint_adhoc	Closes the sprint early	sprintId
close_sprint_by_date	Closes the sprint with a cutoff date	sprintId, date
get_sprint_work_items	Gets the items associated with the sprint	sprintId
preview_done_items	Previews completed items before closing	sprintId
regenerate_sprint_changelog	Regenerates the changelog of a closed sprint	sprintId

Example: Create a sprint

Tool: create_sprint
Parameters:
  boardId: "board-uuid"
  name: "Sprint 14 - Authentication"
  startDate: "2025-03-01"
  endDate: "2025-03-14"
  goal: "Complete the login system with Google OAuth and user roles"

Example: Preview completed items

Tool: preview_done_items
Parameters:
  sprintId: "sprint-uuid"

Returns the list of items that would be marked as completed when closing the sprint, allowing verification before the close.

Example: Close sprint and generate report

Tool: close_sprint
Parameters:
  sprintId: "sprint-uuid"

When the close is executed, the changelog and sprint metrics are automatically generated.