Sprint Planning Board with Automatic Completion Tracking

Overview

Agile teams often outgrow sticky notes and basic boards quickly. The sprint is a parent concept with stories underneath, but most monday.com setups treat them as flat items — losing the relationship between sprints and their stories.

This template uses subitems to model the sprint-story relationship properly. Each sprint is a parent item. User stories and tasks are subitems with their own statuses, timelines, and owners. When all stories reach "Accepted", the sprint auto-completes. When stories slip, the sprint timeline adjusts. When anything gets blocked, the scrum master knows immediately.

Who This Template Is For

• Development teams running scrum or kanban with sprints
• Scrum masters who want automated sprint health tracking
• Engineering managers who need visibility into sprint progress without daily stand-up reports
• Cross-functional teams where designers, developers, and QA work on shared sprints

Board Structure

Groups

• Sprint Backlog — upcoming sprints being planned
• Current Sprint — the active sprint
• Completed Sprints — finished sprints (keep last 3-4 for velocity tracking)

Columns

Subitems (User Stories Per Sprint)

Setting Up the Automations

Automation 1: Sprint Auto-Complete

This uses the All Subitems Reach a Status Trigger.

What it does: When every user story in a sprint reaches "Accepted", the sprint automatically moves to "Complete". No manual checking at sprint end — the board tells you when you are done.

How to set it up:

1. Open the Automations Centre
2. Search for Community Cookbook recipes
3. Select: When ALL subitems reach a specific status
4. Set target status to Accepted
5. Set action to change Sprint Status to Complete

Note: "Accepted" is deliberately different from "Done" — this means stories have been reviewed and accepted by the product owner, not just finished by the developer.

Automation 2: Sprint Timeline Sync

This uses the Sync Parent Dates from Subitem Timelines.

What it does: As story timelines shift during the sprint (a story takes longer, a new story is added), the parent sprint's timeline adjusts to show the actual date range.

How to set it up:

1. Select: Roll up subitem timelines to the parent item
2. Map subitem timelines to the parent Sprint Start, Sprint End, and Timeline columns
3. Activate

This is especially useful during sprint planning — as you assign stories with dates, the sprint timeline builds itself.

Automation 3: Blocker Alerts

This uses the OR Status Trigger.

What it does: When any story hits "Blocked", the scrum master is notified immediately. Blocked stories are the number one sprint killer — catching them early makes the difference.

How to set it up:

1. Select: When a column matches any of these values
2. Set values to: Blocked
3. Set action to notify the Scrum Master

Tips and Variations

• Velocity tracking: At the end of each sprint, fill in the Velocity column with actual points completed. Over time, this data helps with capacity planning and commitment accuracy.
• Sprint retrospective: Add subitems for "What went well", "What to improve", and "Action items" at the end of each sprint. Keep them in the Completed Sprints group for reference.
• Bug tracking integration: For bugs discovered mid-sprint, add a "Bug" type subitem. Track bug-to-feature ratio per sprint using the Type dropdown.
• Definition of Done: Add a "DoD Checklist" text column to stories listing criteria (code reviewed, tested, documented). The story should only move to Accepted when all criteria are met.
• Cross-sprint dependencies: Use the Connect Boards column to link stories that depend on items in other sprints or on other teams' boards.

What You Will Need

• A monday.com account (Standard plan or above)
• Community Cookbook installed from the monday.com marketplace
• About 15 minutes for initial setup

Frequently Asked Questions

What if not all stories are completed in a sprint?+

Can I use this for kanban instead of scrum?+

How do I handle stories that span multiple sprints?+