Skip to main content

62 docs tagged with "ops"

View all tags

AI governance

Route AI governance — view (manage to set role caps)

Bulk actions

Route View Tasks plus the permission for each action

Capacity and planned hires

What this page is — A grid of net plannable hours — one row per person or planned hire, one column per time box of the scenario — computed from the organisation's working calendar, holidays, approved leave, each person's allocation and the project's focus factor.

Define — sizes, skills, people and hires

What this page is — The Define tab, the first tab of Planning. It holds what a plan is made of before anything is assigned: the size scale, the skills the project plans with and who has them, each person's hours per week, and the planned hires.

Dependencies

What this page is — The two steps of Plan by → Dependencies: mapping what waits for what, then fitting the sprints around it.

Goals, burndown and insights

What this page is — What a time box is for — its goal and success criteria — and the ways the committed plan is watched afterwards: an AI goal check, a daily burndown, five Risk radar signals, a delivery forecast that follows the plan's links, and new report fields.

Invoicing

What this page is — How a finished (or running) stage — or an achieved contract line (a priced milestone) — becomes an invoice in Orbit Books, and the bills that go to the contractors who did the work.

Jira sync

Route Configure Jira sync, mappings and run syncs

Objectives, review, merge and commit

What this page is — The end of a PI session: the Objectives each team commits to (with business value), the Review tab with team demos and the confidence vote, the adjustment round, and Merge & commit, which turns every team's board into one plan written to the tasks.

Overview

Orbit Ops is where work is planned, tracked, timed and billed. Its centre is the Task Management

Overview

Route Page Access of Task Configuration

Phases, sprints and milestones

What this page is — The rules that relate the three kinds of Roadmap entry — a phase contains sprints and milestones; a task sits in one time box and may contribute to one milestone.

PI Planning for integrators and assistants

What this page is — Every way software, rather than a person in the session, reaches PI Planning: the read-only Orbit Public API and the matching MCP tools, the questions the Orbit Assistant answers, the two e-mails and the webhook a session sends, and the live connection the page itself uses.

PI Planning overview

What this page is — The map of PI Planning: several teams plan one programme increment (a phase of a project and the sprints under it) together, each on its own board, against one shared clock, and the result is merged and committed to the tasks once.

Plan with AI

Route Plan with AI (plus Create Tasks to apply; Manage Milestones to create phases)

Planning assistants

Routes Plan with AI (notes → tasks, sprint planning), AI assist on tasks (release notes), Edit member capacity (capacity table)

Planning for integrators and assistants

What this page is — Every way software, rather than a person at the Planning screen, reaches the plan: the Orbit Public API, the planning.committed webhook, the MCP tools an AI agent uses, the client SDKs, and the questions the Orbit Assistant can answer about plans, capacity and hires.

Planning settings

What this page is — The per-project rules Planning works by: how tasks are estimated (hours, points or days), how a size becomes hours, how much of a day is plannable, what the team calls a sprint or a phase, what happens when dates fall outside their phase, and whether a commit tolerates drift.

Planning teams

What this page is — The standing teams your organisation plans with: who is in each team, in which role and at what share of their time, who leads it, and which projects it plans in. Teams live in Organization Settings; each project picks the teams that plan in it.

Planning workspace

What this page is — A sandbox for a project's sprints and phases. You plan placements, assignees, estimates, capacity and goals inside a named scenario; nothing reaches the live tasks until you press Commit.

Program board, dependencies and risks

What this page is — The two whole-programme views of a PI session: the Program board (every team's plan side by side, with the cross-team dependencies between them) and the Risks tab (the ROAM board of team and programme risks).

Report Builder

Route Open the report builder (view) / Manage saved reports

Risk radar

Route View risk radar (Manage risk radar to recompute and change settings)

Running the live session

What this page is — The controls that run a PI session while it happens: the session bar with the shared clock, the facilitator's buttons, the Broadcast to everyone, who is online, and the Discussion tab where teams ask, answer and share.

Scenarios and commit

What this page is — The life of a scenario: seed it from the live tasks, shape it on a drag-and-drop board (by hand or with an AI suggestion), keep it in step with reality through drift and rebase, compare it with others, and commit it in one transaction.

Session set-up, brief and team boards

What this page is — Everything that happens before and around the planning itself: creating a PI session, the Brief tab where the facilitator decides which team plans which category, publishing, and the Team boards tab where each team plans its own work.

Setting up a project

What this page is — The guided set-up: six questions that turn a bare project into one that is ready to plan — how the work is measured, whether it carries a value, who is on it, what its task types and categories are, and what its phases look like.

Subtasks

Route: /org/tasks?id= → Subtasks tab

Time logs

Route: /org/tasks?id= → Time Logs tab

Value and the contract

What this page is — How a customer contract that is priced by milestone becomes traceable money on the plan: the amount on each Milestone, the share each contributing task carries, and the Value tab that reads it all back.