Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Sprint / Agile Board
- Development tracker
- Finance system
- File store
Sprint / Agile Board connects a project's dated sprint scopes to assigned stories, status boards, milestones, impediments and risks. A Delivery Lead sets the project and scope; team members work stories and record time against the project and, when relevant, a story.
Projects in one list
| Project code | Project name | Owner | Start date | End date | Status | |
|---|---|---|---|---|---|---|
| PORTAL-26 | Customer portal refresh | Priya Nair | 31 Oct | 09 Nov | Active | |
| DISPATCH-26 | Warehouse dispatch dashboard | Yuki Tanaka | 28 Oct | 01 Nov | Active | |
| BILLING-26 | Invoice automation rollout | Omar Faris | 17 Oct | 19 Oct | Active | |
| FIELD-26 | Field service mobile app | Jonah Price | 17 Oct | 22 Oct | Active | |
| PARTNER-26 | Partner onboarding portal | Marcus Reed | 17 Oct | 21 Oct | Active |
Scope Reviewer decides whether to accept the submitted scope.
Every feature works on the same records. Pick one to see the screen your team works in.
The Delivery Lead creates a project for an organization, names an owner and sets the planned start and end dates.
Milestones
| Milestone name | Project | Owner | Due date | Status | |
|---|---|---|---|---|---|
| Checkout pilot ready | Field service mobile app | Mei Lin | 31 Oct | Missed | |
| Partner portal design approved | Support workflow redesign | Mei Lin | 16 Oct | Missed | |
| Inventory sync integration test | Warehouse dispatch dashboard | Jonah Price | 18 Oct | Missed | |
| Invoice export acceptance | Support workflow redesign | Elena Costa | 19 Oct | Missed | |
| Mobile field trial | Field service mobile app | Aisha Bello | 04 Nov | Missed |
The Project Manager groups stories inside a dated sprint scope linked to a project.
Approval conditions
| Sprint code | Sprint name | Owner | Estimated hours | Start date | End date | |
|---|---|---|---|---|---|---|
| SPR-2026-12 | Sprint 12: checkout recovery | Mei Lin | 6 | 20 Oct | 28 Oct | |
| SPR-2026-13 | Sprint 13: account settings | Nicolas Vega | 15 | 02 Nov | 05 Nov | |
| SPR-2026-14 | Sprint 14: search relevance | Grace Kim | 13 | 18 Oct | 25 Oct | |
| SPR-2026-15 | Sprint 15: invoice exports | Nicolas Vega | 3 | 27 Oct | 05 Nov | |
| SPR-2026-16 | Sprint 16: mobile navigation | Nicolas Vega | 14 | 23 Oct | 01 Nov |
A story belongs to a sprint scope and can have an assignee, priority, estimate and due date.
Stories
| Story key | Title | Assignee | Sprint scope | Priority | Status | |
|---|---|---|---|---|---|---|
| PORTAL-482 | Save interrupted checkout | Nicolas Vega | Sprint 17: access controls | Low | Blocked | |
| PORTAL-491 | Add invoice download link | Priya Nair | Sprint 13: account settings | Medium | Blocked | |
| DISPATCH-217 | Filter orders by delivery date | Jonah Price | Sprint 19: release hardening | High | Blocked | |
| BILLING-308 | Show stock by warehouse | Aisha Bello | Sprint 14: search relevance | Critical | Blocked | |
| MOBILE-174 | Send invite reminder email | Grace Kim | Sprint 16: mobile navigation | Low | Blocked |
Team members hold a role, practice and weekly capacity.
Stories
| Story key | Title | Sprint scope | Priority | Status | Due date | |
|---|---|---|---|---|---|---|
| PORTAL-482 | Save interrupted checkout | Sprint 18: reporting filters | Low | Backlog | 28 Oct | |
| PORTAL-491 | Add invoice download link | Sprint 17: access controls | Medium | In progress | 21 Oct | |
| DISPATCH-217 | Filter orders by delivery date | Sprint 14: search relevance | High | In review | 16 Oct | |
| BILLING-308 | Show stock by warehouse | Sprint 12: checkout recovery | Critical | Blocked | 19 Oct | |
| MOBILE-174 | Send invite reminder email | Sprint 12: checkout recovery | Low | Done | 27 Oct |
Impediments record the reported problem, severity, project and owner.
Risks
| Risk code | Description | Project | Owner | Probability | Impact | |
|---|---|---|---|---|---|---|
| RISK-2026-017 | Carrier API may miss cutoff | Invoice automation rollout | Elena Costa | Low | Low | |
| RISK-2026-018 | Export volume may delay billing | Customer portal refresh | Jonah Price | Medium | Medium | |
| RISK-2026-019 | Legacy roles need migration | Product search upgrade | Jonah Price | High | High | |
| RISK-2026-020 | Pilot users need training | Field service mobile app | Nicolas Vega | Low | Low | |
| RISK-2026-021 | Search index may lag updates | Warehouse dispatch dashboard | Jonah Price | Medium | Medium |
Team members record work date, hours, project and optionally a story on a time entry.
Approval conditions
| Entry number | Team member | Project | Work date | Hours | Status | |
|---|---|---|---|---|---|---|
| TE-97564 | Grace Kim | Warehouse dispatch dashboard | 23 Oct | 3 | Submitted | |
| TE-93663 | Jonah Price | Partner onboarding portal | 31 Oct | 3 | Submitted | |
| TE-68453 | Marcus Reed | Partner onboarding portal | 14 Oct | 2 | Submitted | |
| TE-62916 | Omar Faris | Product search upgrade | 21 Oct | 8 | Submitted | |
| TE-29627 | Elena Costa | Partner onboarding portal | 12 Oct | 7 | Submitted |
Plan and review a sprint ships ready to use. One step needs a named approval before the work moves on: Review scope (Scope Reviewer).
Name the project owner and schedule.
Set the scope baseline and dates.
Put each story with its sprint and assignee.
Give open blockers severity and an owner.
Send the complete baseline into review.
Inspect the pending receipt and record the outcome on the scope.
Open any project to see its impediments, the roles that work on it, its process stages and its approvals on one page.
Project name, Owner, Start date and End date.
Each line is linked to this project.
Admin, Delivery Lead and Project Manager, each with their own permissions.
Set project and Plan sprint scope, with the role that acts.
Review scope, with who decides.
Customer portal refresh · Active
| Impediment key | Title | Project |
|---|---|---|
| BLOCK-2026-041 | Order sync fails after timeout | Customer portal refresh |
| BLOCK-2026-042 | Test data missing for returns | Field service mobile app |
| BLOCK-2026-043 | Export queue stalls on large files | Product search upgrade |
Signed in as Scope Reviewer
| Decision | Approver | |
|---|---|---|
| Review scopeInspect the pending receipt and record the outcome on the scope. | Scope Reviewer | |
| Approve sprint scopes | Scope Reviewer |
Everyone opens Sprint / Agile Board to the work that is theirs. Pick a role to see what it starts with.
Maintains access, project structure and delivery records.
Owns project delivery and resolves scope and schedule decisions.
This is the first screen this role sees.
Sprint scopes · Delivery Lead
| Sprint code | Sprint name | Owner | Estimated hours | Start date | End date | |
|---|---|---|---|---|---|---|
| SPR-2026-12 | Sprint 12: checkout recovery | Mei Lin | 6 | 20 Oct | 28 Oct | |
| SPR-2026-13 | Sprint 13: account settings | Nicolas Vega | 15 | 02 Nov | 05 Nov | |
| SPR-2026-14 | Sprint 14: search relevance | Grace Kim | 13 | 18 Oct | 25 Oct | |
| SPR-2026-15 | Sprint 15: invoice exports | Nicolas Vega | 3 | 27 Oct | 05 Nov | |
| SPR-2026-16 | Sprint 16: mobile navigation | Nicolas Vega | 14 | 23 Oct | 01 Nov |
Plans sprint scopes, assignments and blocker follow-up.
This is the first screen this role sees.
Sprint scopes · Project Manager
Works assigned stories, raises impediments and submits hours.
This is the first screen this role sees.
Stories · Team Member
Checks submitted hours and the approval outcome recorded by the workflow.
This is the first screen this role sees.
Time entries · Time Reviewer
| Entry number | Team member | Project | Work date | Hours | Status | |
|---|---|---|---|---|---|---|
| TE-97564 | Grace Kim | Warehouse dispatch dashboard | 23 Oct | 3 | Submitted | |
| TE-93663 | Jonah Price | Partner onboarding portal | 31 Oct | 3 | Submitted | |
| TE-68453 | Marcus Reed | Partner onboarding portal | 14 Oct | 2 | Submitted | |
| TE-62916 | Omar Faris | Product search upgrade | 21 Oct | 8 | Submitted | |
| TE-29627 | Elena Costa | Partner onboarding portal | 12 Oct | 7 | Submitted |
Reviews submitted sprint scopes and records the outcome on the scope.
This is the first screen this role sees.
Sprint scopes · Scope Reviewer
| Sprint code | Sprint name | Owner | Estimated hours | Start date | End date | |
|---|---|---|---|---|---|---|
| SPR-2026-12 | Sprint 12: checkout recovery | Mei Lin | 6 | 20 Oct | 28 Oct | |
| SPR-2026-13 | Sprint 13: account settings | Nicolas Vega | 15 | 02 Nov | 05 Nov | |
| SPR-2026-14 | Sprint 14: search relevance | Grace Kim | 13 | 18 Oct | 25 Oct | |
| SPR-2026-15 | Sprint 15: invoice exports | Nicolas Vega | 3 | 27 Oct | 05 Nov | |
| SPR-2026-16 | Sprint 16: mobile navigation | Nicolas Vega | 14 | 23 Oct | 01 Nov |
Read sprint effort, capacity, blockers and approvals from the records your team maintains.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Planned | 49 | ||
| Active | 17 | 35% | |
| On hold | 7 | 41% | |
| At risk | 3 | 43% |
Sample counts per stage
Compare sprint scope estimated hours with story estimate hours and story actual hours by sprint scope.
Group Stories by sprint scope and Status to see completed and blocked work.
Compare team member weekly capacity hours with assigned estimate hours and assigned actual hours.
Compare project estimated hours, actual hours and logged hours by project.
Group Impediments by Severity, Status and Owner.
Group Risks by Probability, Impact, Status and Owner.
Compare milestone due date and Status by project and owner.
Group time entries by Status, team member and Project with Hours.
See how Sprint / Agile Board fits your kind of team.
A delivery team planning product iterations can group stories by sprint scope and keep blockers close to the board.
A services team can connect an organization, project schedule, milestones and sprint scopes to the same delivery record.
An internal team can plan project work in sprint scopes while recording risks, impediments and review decisions.
Each stage of plan and review a sprint names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Give your team a way to ask for a clear view of sprint work and handoffs.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 13 tablesStart with one team and one process, then add the rest once the basics are running.
Add the organization, owner, schedule and active project record.
Add a dated sprint scope and assign stories to active team members.
Block a story, triage an impediment with severity and inspect its receipt.
Submit a complete scope and a positive time entry, then inspect the scope intake receipt and the time approval decision and receipt.
Bring in milestones, risks and historical work after the team can use the first project reliably.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Sprint / Agile Board for your business. Start with one active project, one sprint scope and a small assigned story backlog.
Link each story to a sprint scope, assign a team member and update its status as work moves through backlog, progress, review, blocked and done.
The blocked story queue gives the Project Manager a place to follow up. An impediment can hold severity, owner and the path to verification.
An open impediment with severity moves to triaged and receives an operation receipt. The Project Manager can use the triage queue to inspect the result.
Set its owner, estimate, start date and end date. Submission records a pending receipt for review when that baseline is ready.
Assign a Scope Reviewer to inspect the submitted scope, its linked stories and the pending receipt. The reviewer then records the outcome on the scope.
A team member submits dated, positive hours against a project. The approval records a review decision and operation receipt.
Yes. Milestones have due dates, statuses and owners. Risks hold probability, impact, mitigation and ownership for project follow-up.
Team member records show weekly capacity alongside assigned estimates, actual effort and logged hours.
Start free, then use Proto to change fields, steps and approvals before your team goes live.