These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Sprint / Agile Board
- Data model
The tables behind Sprint / Agile Board
Sprint / Agile Board ships with 13 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 13
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Projects:
Organizations and Projects establish the delivery context; Milestones track dated checkpoints.
Sprint work:
Sprint scopes contain Stories, which can be assigned to team members.
Blockers:
Impediments and Risks belong to Projects and have owners.
Evidence:
Time entries, review decisions, operation receipts and record attachments preserve work and decisions.
Every table, by feature
- Projects4
- Sprint Scopes4
- Stories4
- Team Capacity4
- Impediments and Risks5
- Time and Review6
- Shared and settings1
- Organizations
Client and internal business organizations that projects are delivered for.
- Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Milestones
Dated checkpoints a project must meet.
Linked to Projects, Team members - Risks
Project risks with probability, impact, owner and mitigation.
Linked to Projects, Team members
- Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Sprint scopes
Groupings of work inside a project.
Linked to Projects, Team members - Stories
Individual pieces of work assigned to a delivery team member.
Linked to Sprint scopes, Team members, Projects - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members
- Sprint scopes
Groupings of work inside a project.
Linked to Projects, Team members - Stories
Individual pieces of work assigned to a delivery team member.
Linked to Sprint scopes, Team members, Projects - Team members
Delivery staff with role, practice and weekly capacity.
- Impediments
Defects and change items raised against project work.
Linked to Projects, Team members
- Team members
Delivery staff with role, practice and weekly capacity.
- Stories
Individual pieces of work assigned to a delivery team member.
Linked to Sprint scopes, Team members, Projects - Sprint scopes
Groupings of work inside a project.
Linked to Projects, Team members - Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Stories
- Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Stories
Individual pieces of work assigned to a delivery team member.
Linked to Sprint scopes, Team members, Projects - Impediments
Defects and change items raised against project work.
Linked to Projects, Team members - Risks
Project risks with probability, impact, owner and mitigation.
Linked to Projects, Team members - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members
- Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Stories - Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Projects - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members - Record attachments
Files attached to delivery records.
Linked to Team members - Stories
Individual pieces of work assigned to a delivery team member.
Linked to Sprint scopes, Team members, Projects - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members
Keys and references
A sprint scopes row references Projects. Stories references sprint scopes and may reference Projects and team members. Time entries references team members and Projects and may reference Stories through Task. Impediments, Milestones and Risks reference Projects. Review decisions can reference Projects. Record attachments identify a parent record through parent table name and parent record ID.
Migration order
- Load Organizations and team members.
- Create Projects and their Milestones and Risks.
- Create sprint scopes and link Stories.
- Add Impediments, time entries and review evidence.
- Check reference links, owners and status values on a sample project.
Set up Sprint / Agile Board your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.