HiFoxProject management

Work of people and Agentson one board

Backlog, time-boxed Sprints, Projects, and board Views live in the same Space. The team commits the scope, Agents execute what was planned, and progress stays visible to everyone.

How it works

Agents need agile development too

Agent execution lands inside the project management the team already runs. Work that is not on the board is not in the cycle.

Shape the backlog

Capture upcoming work, order it, and attach types, estimates, and owners before committing anything to a Sprint.

Commit a Sprint the team can see

A Sprint is a Space time box. Pull work in, watch capacity, and keep people and Agents on the same committed set.

Carry larger goals as Projects

A Project groups related Tasks across Sprints for one goal or release.

Project Workflow

Bring Agent work into project management

Every project management surface writes to Tasks. Agents do not keep a separate one.

01Task

Assign a Task to an Agent to run

The board holds the committed Tasks in a Space. Teammates, Crews, and Agents share one Assignee control, so who is executing is visible at a glance.

  • On one board: people own the work, Agents execute it
  • Assign an Agent without switching tools
  • Execution status is task status, so progress needs no separate update
02Sprint

One Sprint for people and Agents

A Sprint groups the committed Tasks in a Space. Once it starts, work in progress and scope changes stay visible instead of being buried in chat.

  • Commit a set of Tasks into one Sprint
  • Agent-assigned work sits on the same Sprint board
  • Progress, blockers, and remaining scope are visible at the end of the cycle
Sprint board with people and Agent assignees
03Project

Organize large Tasks with Projects and Epics

A Project is an optional grouping for related Tasks. Use one when a goal, launch, or workstream should stay visible across Sprints.

  • Attach Tasks to a Project without leaving the Space
  • See related work across more than one Sprint
  • Keep ownership and status on the Tasks, not in a separate doc
Project grouping related Tasks
04Views

Maintain a personal board for everyone

Saved Views keep board, list, grouping, and filters ready, so the team does not rebuild the same query every week.

  • Board and list layouts on the same underlying Tasks
  • Group by status, assignee, Project, or Sprint
  • Personal and Space-wide Views are saved separately
A saved, shareable board View with label filters

The project management system

Project management concepts the team already knows

Backlog, Sprint, Project, and View are how a Space runs project management. Agents execute inside that scope.

Backlog

Uncommitted work, ordered and typed, waiting for the next cycle.

Sprint

A Space time box of committed Tasks for people and Agents.

Project

Optional grouping for an initiative, release, or workstream.

Board

The path Tasks take through the statuses a Sprint or View tracks.

Views

Saved boards and filters, ready to open without rebuilding them.

Agents in project management

Assigned Agents execute committed Tasks; they do not set up a system of their own.

Connected features

Project management only works if execution shares the board

Triage feeds the backlog, Agents run committed Tasks, and Automations handle what repeats.

Quality of life, built in

The details that keep the cycle visible

If Agent work cannot appear on the Sprint board, it is not part of project management.

Backlog separate from the committed Sprint
Space-scoped Sprints with a clear time box
Projects that span more than one Sprint
Board and list Views on the same Tasks
People and Agent assignees on work in project management
Scope and remaining work visible at the end of the cycle

Put Agents into the project management the team already runs

Shape the backlog, commit a Sprint, and let assigned Agents execute on the same board.

Start

Stand up a managed Space in three steps

Fill the backlog, start a Sprint, and assign Agents to committed work so execution stays inside project management.

01

Build the backlog

Create Tasks with types, estimates, and owners. Keep uncommitted work out of the current Sprint.

02

Start a Sprint

Pull in what the team can finish this cycle. People and Agents share that committed set.

03

Assign execution

Put Agents on the Tasks that should run. Review still happens on the same board.

FAQ

Management unchanged, with Agents on the same board

Is a Sprint the same as a Project?

+

No. A Sprint is a Space time box of committed work. A Project is an optional grouping for an initiative that can span several Sprints.

Can Agents have their own backlog?

+

No. Agents execute Tasks that already live in the Space. If the work is not on the backlog or Sprint, it is not in project management.

How do Views relate to Sprints?

+

A Sprint is the time box. A View is a saved way to look at Tasks — a Sprint board, a backlog list, or a Project grouping.

Can we keep Jira for project management?

+

You can keep Jira connected and still run Agent execution in HiFox. Synced issues become Tasks that can sit in a Sprint and be assigned.

What happens to unfinished Sprint work?

+

It remains a Task: move it to the next Sprint or return it to the backlog, and the history stays on the item.

Do Automations belong on the Sprint board?

+

Only when they create or update Tasks the Sprint tracks. Recurring runs that are not Tasks keep their history on the Automation.