Follow every story of the sprint on one board.
Sprints give a product team a steady rhythm: plan a few weeks of work, build it, show it, and start again. In Tape, a sprint is a record, every story points to its sprint, and a board shows the team where each story stands.
Set up your backlog and sprints
Create two database apps. To add fields, open the app menu (tooltip Follow, export and more…) and select Customize record layout. Learn more about creating a database app →
Stories: one record per story, bug, or chore, with a
Single selectfield for the type, aNumberfield for the story points, an assignee as aMemberfield, and aStatusfield such as To do, In progress, and In review asIncomplete, and Done asCompleted.Sprints: one record per sprint, with the dates in a
Datefield with an end date, a sprint goal, and a status such as Planned, Active, and Done. Learn more about the date field →
Add a Relation field called Sprint to Stories, and choose Sprints under Select a database. A story without a sprint is in the backlog. Learn more about the relation field →
Plan the next sprint
Open a view of the backlog: a filter where the Sprint field
Is empty. Learn more about filters →Pick the stories the team can finish, and set their Sprint field to the next sprint.
Write the sprint goal into the sprint record, so everyone knows what matters most.
To see the stories from the sprint, add a References block to the record layout of Sprints. Opening a sprint then shows all its stories under Related records, so the plan is in one place. Learn more about references →
Each sprint shows its goal and all its stories.
Run the sprint on a board
Create a team view of Stories with the layout Board, grouped by the status, and a filter on the current sprint. Everyone drags their cards from To do to Done as the work progresses. Learn more about board views →
Show what matters on the cards: the type and the story points, so the team sees the size of the work at a glance.
My work: a filter on the assignee with
Myselffor your own cards.Track progress: point at the view in the view list, click
•••(tooltipSettings), and selectStatus bar→For viewto see how many stories are complete. Learn more about the status bar →
Review and close the sprint
What got done: a table of the sprint's stories grouped by status. Under the Points column, select
CalculateandSumto add up the story points. Learn more about table calculations →Velocity: add a
Calculationfield to Sprints that adds up the story points of the stories that link to it. Write the name of the database app, for exampleStories.Story_points.sum. Over a few sprints, you see how much the team can take on. Learn more about the calculation field →Carry over: move unfinished stories to the next sprint, and set the sprint's status to Done.
Add up the story points of the sprint under Points.
Tip: Break a big story into steps with a task list inside the story, or into smaller related records. Read the guide on breaking tasks into steps →
Learn more
FAQs
Can bugs and stories live in the same database app?
Can bugs and stories live in the same database app?
Yes. Use a Single select field for the type, and filter views by it when you need only bugs. Read more in the issue tracker guide. Read the issue tracker guide →
Can I see a timeline of my sprints?
Can I see a timeline of my sprints?
No, not as a timeline view. Tape has table, board, and list views. Show the dates of each sprint in a table of the Sprints database, sorted by start date. Learn more about views →
Can the board show only one sprint?
Can the board show only one sprint?
Yes. Add a filter on the Sprint field. Update the filter when the next sprint starts, or keep one view per sprint. Learn more about filters →
Still have more questions? Find answers and get help from community experts in the Tape community →.
