On this page & nearby
Part 3 of 4
Run a sprint — start delivering
Everything's in place. Plan and start a sprint, work the board, watch your progress, then close it out with a retrospective. On a Kanban project there are no sprints — look out for the If you chose Kanban notes along the way.
15
Plan & start a sprint
Choose a chunk of work for a fixed stretch of time, commit to it as a team, and start.
Project › Sprints · Backlog
- Open Sprints and click New sprint. Give it a name, a short sprint goal and, if you like, a start date — the end date follows from the project's sprint length.
- Click Plan in backlog and move items into the sprint — drag them, or use a row's ⋯ › Move to. Take the top of your ordered list, as much as the team can realistically finish.
- Optional: click Capacity on the sprint's card to set how many points each person can take, and compare it with what you've committed and the team's recent velocity.
- Ready? Click Start sprint. Only one sprint runs at a time — the next one can start once the current one completes.
🧑🏫Creating, starting and completing sprints is for the project's Product Owner and Scrum Masters (and workspace Owners/Admins).
⏭️If you chose Kanban — there are no sprints, so skip this step. Go straight to the board and pull the next card whenever someone has capacity.
16
Work the board
The board is where the day-to-day happens — cards move left to right as work progresses.
Project › Board
- Open the Board to see the running sprint's work in the stages you set up. Use the search, filters and quick filters (Only my items, Recently updated), or Group by assignee or epic.
- Drag a card from one stage to the next as it moves along. If a stage won't take it — a WIP limit, a transition or an entry rule — the column says Can't move here and why.
- Click a card to open it in a side panel (more details under All fields). Add comments and attachments, log time, add subtasks, link related items and watch it to hear about changes.
💬Comments are a permanent record — they capture the history of a decision, so they stay put once posted. A work item added by mistake can be removed from its ⋯ menu › Delete work item (the Product Owner, Scrum Masters and Admins can delete any; Developers the ones they reported).
⏭️If you chose Kanban — the board shows all your ongoing work, with no sprint. An Ageing quick filter shows just the cards that have sat still too long, and cards that reached Done more than 14 days ago drop off the board to keep it tidy.
17
Track progress
Charts that show whether you're on course — no spreadsheets required.
Project › Reports
- Open Reports. The Sprint tab has the Burndown (how much is left in the sprint) and the Sprint report.
- The Delivery tab shows Velocity (how much you finish each sprint), sprint completion and cycle & lead time (how long items take to reach Done from when work starts, or from when they were created).
- The Flow tab covers work in progress, throughput, work item age and cumulative flow (how much work sits in each stage over time); the Team tab shows who holds the open work.
📊Some charts sit on higher plans. Every plan has the Burndown, the Sprint report and the Team tab. Velocity, cumulative flow, cycle & lead time and the flow metrics are Starter and up — on Free they show an upgrade prompt instead.
⏭️If you chose Kanban — there's no Sprint tab. Start with the Flow tab (Starter and up): work in progress, throughput and how long items have been open.
18
Complete the sprint
Wrap up the cycle cleanly and roll anything unfinished forward.
Project › Sprints
- On Sprints, click Complete sprint on the running sprint — usually at the end of its dates, but you can complete it early.
- Choose where unfinished work goes under Move unfinished work items to: the backlog, or a sprint you've already created. Add optional retrospective notes if you like.
- Plan and start your next sprint whenever you're ready — the rhythm repeats from Step 15.
🔁This is the loop — plan, work, review, complete, repeat. Each cycle your velocity chart gets more accurate, so planning the next sprint gets easier. A completed sprint is kept as a record: its board becomes read-only, but you can still move an item out of it later.
19
Run a retrospective
A quick team look-back after each sprint — what went well, what to improve, and what to do about it.
Project › Retro
- The Scrum Master (or the Product Owner, if there's no Scrum Master) opens Retro, picks the sprint and clicks Start retrospective.
- The team adds cards under Went well, Improve, Discussion and Kudos, then votes — one vote per person per card — on what matters most.
- Turn the top themes into action items with an owner and a due date. Create work item turns an action into a task, so improvements actually happen next sprint.
🌱Action items from earlier retrospectives that aren't done yet appear under Still open from earlier retros, so nothing slips. Retrospectives are a Starter-plan feature and up, and Stakeholders can read along. A five-minute look-back each sprint is the easiest way for a team to get better over time.
⏭️If you chose Kanban — there's no Retro page. Many Kanban teams hold a short regular review using the Flow reports instead.
Part 1 · Workspace
✓Workspace created & email verified1
✓Workspace name & timezone confirmed1
✓Plan & included features reviewed2
✓Your account set up (two-factor on)3
✓Team invited4
✓Workspace access levels set5
✓Pods set up (optional)6
✓Teams built7
✓Custom fields added (optional)8
✓Slack, GitHub & security (optional)9
Part 2 · Your first project
✓Project created10
✓Workflow shaped11
✓Visibility set12
✓Project roles set (Product Owner, Scrum Master, Developers)12
✓Backlog filled13
✓Backlog organised14
Part 3 · Run a sprint
✓First sprint planned15
✓Sprint started15
✓Board in use16
✓Progress tracked in reports17
✓First sprint completed18
✓Retrospective run19
This checklist is a personal reminder, saved only on this device and browser. It isn't shared with your team — everyone who opens this page keeps their own list. Your real setup lives in the Verdeshell Flow app.