Sprints

The Sprints panel brings agile sprint management into your code editor. Browse your sprint backlog, view sprint-specific boards, analyze progress with burndown and burnup charts, and manage sprint details — all within the same window as your code.

The Problem This Solves

Sprint ceremonies require switching to a browser to check sprint status, review burndown charts, or reassign tasks. This context switching during stand-ups, planning, or mid-sprint check-ins wastes everyone's time and breaks the team's rhythm.

With the Sprints panel, developers and managers can review sprint health, move tasks, and analyze velocity directly in the editor — the tool they use most throughout the day.

What You Are Looking At

The Sprints panel opens as an editor tab with two main views: the Sprint List and Sprint Detail.

Sprint List: Shows all sprints in the current project with search, filter, and sort capabilities. Each sprint card displays its name, date range, task count, and progress indicator.

Sprint Detail: Opens when you click a sprint, showing four tabs — Board, Team, Analytics, and Details.

Opening the Sprints Panel

Access the Sprints panel through:

• Click Sprints under the Plan section in the GitScrum sidebar
• Open the Command Palette and run GitScrum: Open Sprints

Sprint List

The Sprint List view displays all project sprints with powerful discovery tools.

Search

Use the search bar at the top to find sprints by name. Results filter as you type.

Filters

Filter sprints by status to focus on what matters:

• Active: Currently running sprints
• Planned: Upcoming sprints not yet started
• Completed: Finished sprints for retrospective review

Sort Options

Sort the sprint list by:

• Date — chronological ordering
• Name — alphabetical ordering
• Progress — completion percentage

Sprint Cards

Each sprint card in the list shows:

• Sprint name
• Start and end dates
• Number of tasks assigned
• Progress percentage
• Status badge (active, planned, completed)

Click any sprint card to open its detail view.

Sprint Detail

The sprint detail view provides four tabs, each offering a different perspective on sprint work.

Board Tab

The Board tab shows a Kanban board filtered to only tasks assigned to this sprint. It works identically to the main project Board:

• Drag and drop tasks between columns
• Click task cards to open the task drawer
• View task counts per column

This focused view removes noise from tasks outside the sprint, letting you concentrate on current sprint commitments.

Team Tab

The Team tab shows sprint work distributed across team members:

• Each team member's assigned tasks
• Completion status per member
• Effort distribution visualization

Managers use this view during stand-ups to quickly assess who might be overloaded or blocked.

Analytics Tab

The Analytics tab provides sprint-specific charts:

Burndown Chart: Shows remaining work over time against the ideal burndown line. The gap between actual and ideal lines reveals whether the sprint is on track.

Burnup Chart: Shows completed work accumulating over time against the total scope. Scope changes become visible as the total line moves.

These charts update in real-time as tasks move through the workflow. Use them during daily stand-ups or sprint reviews to assess progress objectively.

Details Tab

The Details tab shows sprint metadata and configuration:

• Sprint name and description
• Start and end dates
• Sprint goals
• Total story points or task count
• Creation and last-modified timestamps

Edit sprint properties directly from this tab when you have the appropriate permissions.

Creating a Sprint

Sprint creation happens in the GitScrum web application. Once created, sprints appear automatically in the VS Code extension's Sprint List.

To assign tasks to a sprint, use the task drawer on the Board panel and set the sprint field.

Pro Tips (Once You Are Comfortable)

• Stand-up ready: Open the Sprint Detail Board tab during daily stand-ups. Share your screen and walk through tasks by column — no browser needed.

• Analytics check: Glance at the Burndown Chart once daily. If the actual line is above the ideal, the team may need to reduce scope or address blockers.

• Quick sprint switch: Use the Sprint List filters to toggle between "Active" for current work and "Completed" for retrospective data.

• Team balance: Check the Team tab mid-sprint. If one member has significantly more tasks, rebalance before the sprint risks falling behind.

Permissions

Sprint access follows your GitScrum project role:

• Agency Owners and Managers: Full access — view all tabs, edit sprint details, manage sprint tasks
• Developers: Can view all sprint data, move tasks within the sprint board
• Clients: View-only access to sprint progress (if granted project access)

How to Report a Problem or Request a Feature

If sprint data does not load correctly or you have suggestions, submit feedback through GitScrum Studio.

In the Sidebar of the web application, click on Support Tickets and open a ticket describing your experience.