All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Sprint / Agile Board · Available now

Keep sprint work, blockers and approval evidence together.

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.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewActive Projects
Sprint / Agile Board · Projects

Active Projects

Projects in one list

New project
Projects in view
6
Active
6
Project codeProject nameOwnerStart dateEnd dateStatus
PORTAL-26Customer portal refreshPriya Nair31 Oct09 NovActive
DISPATCH-26Warehouse dispatch dashboardYuki Tanaka28 Oct01 NovActive
BILLING-26Invoice automation rolloutOmar Faris17 Oct19 OctActive
FIELD-26Field service mobile appJonah Price17 Oct22 OctActive
PARTNER-26Partner onboarding portalMarcus Reed17 Oct21 OctActive
6 of 6 records
PORTAL-26Projects · PRJ-93292
Active
Project nameCustomer portal refresh
OwnerPriya Nair
Start date31 Oct
End date09 Nov
Review scopePRJ-93292 · PORTAL-26

Scope Reviewer decides whether to accept the submitted scope.

Waiting for Scope Reviewer
ApproveReturn
Example screen with sample data
Tables, ready to use
13
Saved views
13
Roles with set permissions
6
Reports and dashboards
8
Features

See sprint work in its current state

Every feature works on the same records. Pick one to see the screen your team works in.

Projects

The Delivery Lead creates a project for an organization, names an owner and sets the planned start and end dates.

  • Starting record
  • Named owner
  • Current position
  • Organizations
  • Projects
  • Milestones
  • Risks
Explore projects
OverviewMilestones At Risk
Sprint / Agile Board · Projects

Milestones At Risk

Milestones

New
Milestone nameProjectOwnerDue dateStatus
Checkout pilot readyField service mobile appMei Lin31 OctMissed
Partner portal design approvedSupport workflow redesignMei Lin16 OctMissed
Inventory sync integration testWarehouse dispatch dashboardJonah Price18 OctMissed
Invoice export acceptanceSupport workflow redesignElena Costa19 OctMissed
Mobile field trialField service mobile appAisha Bello04 NovMissed
6 of 6 records
Checkout pilot readyMilestones · MLS-89111
Missed
ProjectField service mobile app
OwnerMei Lin
Due date31 Oct
Example screen with sample data
Process

Plan, work and review each sprint

Plan and review a sprint ships ready to use. One step needs a named approval before the work moves on: Review scope (Scope Reviewer).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Set project

    Name the project owner and schedule.

    PORTAL-26PRJ-93292 · Delivery Lead
    Set projectBy Delivery Lead
  2. Plan sprint scope

    Set the scope baseline and dates.

    PORTAL-26PRJ-93292 · Project Manager
    Plan sprint scopeBy Project Manager
  3. Assign stories

    Put each story with its sprint and assignee.

    PORTAL-26PRJ-93292 · Project Manager
    Assign storiesBy Project Manager
  4. Triage impediment

    Give open blockers severity and an owner.

    PORTAL-26PRJ-93292 · Project Manager
    Triage impedimentBy Project Manager
  5. Submit sprint scope

    Send the complete baseline into review.

    PORTAL-26PRJ-93292 · Project Manager
    Submit sprint scopeBy Project Manager
  6. Review scope

    Inspect the pending receipt and record the outcome on the scope.

    PORTAL-26PRJ-93292 · Scope Reviewer
    Review scopeBy Scope Reviewer
    ApprovalScope Reviewer decides whether to accept the submitted scope.
Inside a record

Connect the systems your team uses

Open any project to see its impediments, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Project name, Owner, Start date and End date.

  2. 2
    Impediments

    Each line is linked to this project.

  3. 3
    Who works on it

    Admin, Delivery Lead and Project Manager, each with their own permissions.

  4. 4
    Process stages

    Set project and Plan sprint scope, with the role that acts.

  5. 5
    Approvals

    Review scope, with who decides.

Active ProjectsPORTAL-26
Sprint / Agile Board · Projects

PORTAL-26

Customer portal refresh · Active

Log activity
1
Record details
Project nameCustomer portal refresh
OwnerPriya Nair
Start date31 Oct
End date09 Nov
2
Impediments

PORTAL-26

Impediment keyTitleProject
BLOCK-2026-041Order sync fails after timeoutCustomer portal refresh
BLOCK-2026-042Test data missing for returnsField service mobile app
BLOCK-2026-043Export queue stalls on large filesProduct search upgrade
Impediments
6
3

Who works on it

  • AdminManage Organizations, Projects, team members, Users
  • Delivery LeadManage Projects, sprint scopes, Milestones, Risks
  • Project ManagerManage sprint scopes, Stories, Impediments, Milestones
4

Process stages

  • Set projectDelivery Lead
  • Plan sprint scopeProject Manager
5

Approvals

  • Review scopeScope Reviewer
    Approved
Example screen with sample data
Approvals

Keep review decisions attached to the work

OverviewApprovals
Sprint / Agile Board · Overview

Approvals

Signed in as Scope Reviewer

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • SS-41660SPR-2026-12
    Sprint 12: checkout recoveryRequested by Mei Lin
    Submitted1dActions
  • SS-55387SPR-2026-13
    Sprint 13: account settingsRequested by Nicolas Vega
    Submitted1dActions
  • SS-15777SPR-2026-14
    Sprint 14: search relevanceRequested by Grace Kim
    Submitted3dActions
  • SS-74787SPR-2026-15
    Sprint 15: invoice exportsRequested by Nicolas Vega
    Submitted6dActions

Who approves what

DecisionApprover
Review scopeInspect the pending receipt and record the outcome on the scope.Scope Reviewer
Approve sprint scopesScope Reviewer
2 approval rules · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens Sprint / Agile Board to the work that is theirs. Pick a role to see what it starts with.

Admin

Maintains access, project structure and delivery records.

  • Manage Organizations, Projects, team members, Users
  • View operation receipts, review decisions
Reports

Read effort and blockers from live records

Read sprint effort, capacity, blockers and approvals from the records your team maintains.

Overview
Sprint / Agile Board · Overview

Sprint / Agile Board dashboard

This quarter

Sprint scopes in view
6
Total estimated hours
56
Submitted
6

Projects by status

How far records got this quarter

StageReachedStep
Planned49
Active1735%
On hold741%
At risk343%

Number of projects by status

Sample counts per stage

0
-40Planned
-60Active
-20On hold
0At risk
-40Completed
Example screen with sample data
  1. 01Sprint estimate against actual

    Compare sprint scope estimated hours with story estimate hours and story actual hours by sprint scope.

  2. 02Story completion by sprint

    Group Stories by sprint scope and Status to see completed and blocked work.

  3. 03Capacity and assigned work

    Compare team member weekly capacity hours with assigned estimate hours and assigned actual hours.

  4. 04Project delivery hours

    Compare project estimated hours, actual hours and logged hours by project.

  5. 05Impediment exposure

    Group Impediments by Severity, Status and Owner.

  6. 06Risk portfolio

    Group Risks by Probability, Impact, Status and Owner.

  7. 07Milestone outcomes

    Compare milestone due date and Status by project and owner.

  8. 08Time approval outcome

    Group time entries by Status, team member and Project with Hours.

Controls

Check the source before a decision

Each stage of plan and review a sprint names the role that acts and the status it records, so a change is never anonymous.

OverviewPlan and review a sprint
Sprint / Agile Board · Process

Plan and review a sprint

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
1
Roles involved
5
Tables touched
10
Set project
Delivery Lead
StatusPlanned → Active
RecordsOrganizations, Projects
Plan sprint scope
Project Manager
StatusNot started → in progress
RecordsSprint scopes, Projects
Assign stories
Project Manager
StatusBacklog → in progress
RecordsSprint scopes, Team members, Projects
Plan and review a sprint
  1. Start
    Set projectPlanned → Active
    Organizations
  2. Step
    Plan sprint scopeNot started → in progress
    Sprint scopes
  3. Step
    Assign storiesBacklog → in progress
    Sprint scopes
  4. Step
    Triage impedimentOpen → Triaged
    Operation receipts
  5. Step
    Track blocked workIn progress → Blocked
    Team members
Example screen with sample data
AI agent

Ask for the next action

Give your team a way to ask for a clear view of sprint work and handoffs.

It can

  • Project Manager: Show blocked stories and their owners for the current sprint scope.
  • Delivery Lead: Compare assigned effort with weekly capacity and list open project risks.
  • Scope Reviewer: Show submitted scopes with owner, estimate and date range.
  • Time Reviewer: Show submitted time entries with project, team member and hours.

Stays with a person

  • A person still decides whether a scope is acceptable and who should work on a blocker.
  • Check the source record and permissions before acting on an agent summary.
Integrations

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
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 13 tables
13tables
  • Projects4
  • Sprint Scopes4
  • Stories4
  • Team Capacity4
  • Impediments and Risks5
  • Time and Review6
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Set the project

    Add the organization, owner, schedule and active project record.

  2. Plan the scope

    Add a dated sprint scope and assign stories to active team members.

  3. Rehearse interruptions

    Block a story, triage an impediment with severity and inspect its receipt.

  4. Rehearse reviews

    Submit a complete scope and a positive time entry, then inspect the scope intake receipt and the time approval decision and receipt.

  5. Extend the cycle

    Bring in milestones, risks and historical work after the team can use the first project reliably.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Sprint / Agile Board.

All questions
How do I get started?

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.

How do stories appear on the board?

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.

What happens when a story is blocked?

The blocked story queue gives the Project Manager a place to follow up. An impediment can hold severity, owner and the path to verification.

How is an impediment triaged?

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.

What is needed to submit a sprint scope?

Set its owner, estimate, start date and end date. Submission records a pending receipt for review when that baseline is ready.

Who reviews a sprint scope?

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.

How are time entries approved?

A team member submits dated, positive hours against a project. The approval records a review decision and operation receipt.

Can we track milestones and risks?

Yes. Milestones have due dates, statuses and owners. Risks hold probability, impact, mitigation and ownership for project follow-up.

Where can we see capacity?

Team member records show weekly capacity alongside assigned estimates, actual effort and logged hours.

Set up Sprint / Agile Board your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appSprint / Agile Board

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.