Total tasks
0Across your portfolioPortfolio View
Plan, track and deliver better — together
Total tasks
0Across your portfolioCompletion rate
0%Tasks marked doneIn progress
0Currently being worked onTo do
0Tasks yet to startWORK OVERVIEW
Priority work at a glance
DELIVERY
Committed vs completed story points
Use completed points across multiple sprints to understand delivery patterns.
CURRENT SPRINT
Remaining story points
Delivery workspace
Review capacity, plan work, and spot delivery risks before committing.
DELIVERY CONTROL
Move committed work through delivery and monitor remaining effort against planned pace.
Ready to plan
Tasks not currently assigned to the selected sprint.
Sprint commitment
Tasks already assigned to the selected sprint.
SPRINT CONFIGURATION
Set sprint goals, dates, capacity, and lifecycle status. Existing task assignments continue to use the sprint name field.
Capacity and delivery windows for this project
AGILE PLANNING
Create and manage project planning horizons. Each PI can contain multiple Features.
Project-scoped, reusable records
DELIVERY SCOPE
Define product capabilities, assign each Feature to a PI, and connect stories and tasks to the same records.
Every Feature belongs to one PI
START HERE
A practical guide to planning work, understanding Agile terminology, tracking delivery, and reading your charts.
Use the project selector to work in the right project. Keep work for one product or team together.
Open Program Increments to set the planning horizon, then create Features within that PI. This keeps names consistent across the project.
Open User Stories, select a Feature, and add a short, user-focused outcome with acceptance criteria.
Make tasks small enough to estimate, assign, and finish. Add a clear description, owner, priority, and dates when useful.
Select the saved User Story when creating a task. Its Feature and PI are inherited; choose a Sprint independently and estimate story points.
Move tasks from To Do to In Progress to Done as work changes. Review insights regularly and adjust the plan when reality differs.
Arcflow provides fields to organize work. Teams may use different Agile frameworks, so agree on definitions and use them consistently.
A workspace for a team's related tasks, stories, and planning.
A longer planning period that may contain multiple sprints. Use your organization's agreed PI names.
A fixed timebox, often one to four weeks, in which a team plans and completes work.
A product capability that may be delivered through several user stories.
A concise description of value from a user's perspective. Example: “As a customer, I want to track my order so I know when it will arrive.”
Specific conditions that must be true for the story to be accepted. Write them so another person can verify them.
A unit of work that someone can own and move through the board.
A smaller action inside a task. Use it for clarity, not to fragment every tiny action.
A relationship where one task relies on another. A blocked task may not progress until its dependency is resolved.
Work-in-progress limit: a cap on items in a status column, used to expose overload and encourage finishing.
Work considered for future delivery but not necessarily committed to a sprint.
Work planned for one sprint that remains incomplete at the sprint's end.
Work is understood enough to be queued but has not started.
Someone is actively working on it. Keep WIP realistic.
The agreed completion conditions are met and the work is verified.
Update status when the work actually changes, not just to make a chart look better. If review or testing is a distinct stage, define how your team represents it (for example, task description/checklist or story lifecycle).
Draft → Ready → In Progress → In Review → Accepted. Draft means the story is still being shaped; Ready means the team believes it can start; In Progress means implementation has started; In Review means it is awaiting validation; Accepted means the story has been reviewed and meets its acceptance criteria. This lifecycle is distinct from the To Do / In Progress / Done status on individual tasks.
Story points are a relative estimate of effort and uncertainty for a story or piece of work. They are not hours, days, money, or a measure of an individual's productivity.
Very small and well understood compared with the team's baseline.
Small, limited complexity, few unknowns.
Moderate work with several steps or some uncertainty.
Large or uncertain. Consider splitting it into smaller deliverable stories.
The task editor stores points on each task. Story cards can show the sum of points across linked tasks; Agile Insights uses committed and completed points for its sprint metrics. Avoid assigning the full story estimate to every task, or the totals will be inflated. Choose one consistent policy: estimate stories and report story-level points, or estimate tasks and sum them—do not mix the two.
Shows the share of tasks marked Done out of the tasks included in the view. A high percentage is only meaningful if statuses are current and the scope is clear.
The points planned or committed for the selected sprint, based on the app's sprint data and fields. Treat it as the planned workload, not a promise of guaranteed delivery.
Points attached to work recorded as completed. Compare with committed points to understand how much planned work was finished.
Compares committed and completed points across sprints. Use several sprints to understand a team's own delivery pattern; one sprint is noisy. Velocity is for forecasting, not individual performance evaluation.
Shows remaining work over time against a reference/ideal trend. If actual remaining work stays above the ideal line, work may be progressing more slowly than planned or scope may have increased. A flat line can mean no work has been completed or data has not been updated.
Work that remains incomplete after the sprint it was planned for. Repeated spillover can point to over-commitment, hidden dependencies, interruptions, or work that is too large.
Open tasks whose end/due date has passed. Review date accuracy, blockers, priority, and whether the plan needs to change.
A calendar view to see work dates and sprint timing. It depends on task dates and consistent sprint labels.
Find tasks by task name, story, assignee, feature, or other indexed/displayed text.
Narrow the displayed work to a planning period, capability, or owner. Remember that metrics may reflect the currently selected scope.
Change the order in which tasks appear; sorting does not change their status or priority.
Set a maximum for a column to highlight overload. A limit is a conversation starter; it does not replace team coordination.
A table for scanning, sorting, selecting, and bulk-updating tasks.
A visual board grouped by task status. Move work through the flow as it progresses.
Review stories, their linked tasks, lifecycle, and aggregate points.
Review sprint calendar and delivery metrics to support planning and retrospectives.
Feature: Account security
User Story: As a user, I want to reset my password so I can regain access securely.
Acceptance criteria: A valid reset request sends a time-limited link; invalid/expired links are rejected; success confirms the password was changed.
Tasks: Build reset-request screen (3 points); implement reset-token validation (5 points); add tests and review (2 points).
Total task-estimated points: 10, if your team uses task-level estimates consistently.
Sprint: Sprint 04. PI: PI 2026-Q4. Owner: assigned team member. Status: tasks move To Do → In Progress → Done; story moves through its own lifecycle to Accepted after verification.
See current workload, sprint outcomes and delivery risks for the selected project.
Assign sprint dates to tasks to generate sprint reporting.
Committed points
0Estimated effort in selected sprintCompleted points
0Effort in completed tasksRemaining points
0Work not yet completedOverdue tasks
0Open tasks past their due dateTask distribution by status
Completed effort across dated sprints
Not enough dated sprint data yet. Add start and end dates to sprint tasks.
Historical delivery performance based on recorded sprint snapshots.
Planning view of sprint date ranges
Committed vs completed by sprint
Account
Your signed-in account and access for the selected project.
First name
-Last name
-Firebase UID
-Selected project
-Project ID
-Your role
-