Feature 3 of 8 · Projects
Projects & Delivery
Everything a delivery team needs to plan and run work, as its daily tool: backlogs, sprints, boards, releases, milestones and intake, on one shared structure so figures mean the same thing in every project.
What teams can do
Set up
A project in one guided wizard
Details, Delivery (account, programme, delivery model, workstreams, dates), an optional Azure DevOps import, and Review. Nothing is created until Review is confirmed, so nothing is left half-made.
Staff
A team with hours and a cost
Add people with a project role, an access level, hours a week, dates and a cost per hour. The Team page shows how booked each person is everywhere, and what the team costs.
Plan
Backlog, sprints and scope
Drag work into sprints, take a suggested sprint scope, and run a plan check that flags unestimated, oversized or blocked items before the sprint starts.
Run
Board, standup and insights
A Kanban board with WIP limits, a person-by-person standup, and sprint insights that name the decisions needing attention.
Ship
Releases that fill themselves
Every open work item sits in its workstream's next planned release. Marking a release released moves unfinished work on to the next one.
Commit
Milestones with baselines
The committed date moves only by a deliberate, recorded re-baseline. Forecasts and slippage are measured against it, and feed schedule health.
Intake
Requests from outside the team
Publish a form anyone with the link can fill in. Every report waits in a triage queue until a lead accepts it into a work item, marks it a duplicate, declines it or marks it spam. The reporter follows progress on a tracking page.
Import
Bring Azure DevOps work across
Hierarchy, area paths, iterations, states, assignees, estimates, tags and dates. Re-importing updates rather than duplicates.
One structure for every project
| Tier | Type | Estimated in |
|---|---|---|
| 0 | Epic | Dates (from what sits under it) |
| 1 | Feature | Dates (from what sits under it) |
| 2 | Story · Improvement | Story points |
| 2 | Bug | Hours |
| 3–4 | Task · Subtask | Hours |
Because tiers are fixed, hours logged on a task under a bug count as defect effort everywhere. A project can add its own types, but its settings warn when it drifts, because its figures would stop lining up with other projects.
Workstreams: chosen once
When a project is created, its Workstreams are set to The project (one workstream) or Each epic. In an each-epic project, every release and milestone belongs to one epic, and the weekly status reports each epic as its own section. It can't change later, because releases and milestones are filed by it.
Inside a project
| Section | For |
|---|---|
| Overview | Health with the reason for each dimension, what needs attention, what lands next, recent changes, each workstream. |
| Board · Backlog · Sprints | The daily work: the board, all unfinished work as a tree, and each sprint's plan, standup and insights. |
| Work items | Every work item with the full filter set. Filtered views are shareable links. |
| Intake | Forms, their links and the triage queue. |
| Milestones · Releases · Areas | The plan: committed dates, what ships when, and which part of the product work belongs to. |
| Reports | The weekly status and delivery reports. |
| Team | Members, access, allocations, hours, cost and staffing advice. |
| Settings | Workflow and board, hierarchy, fields, screens, labels, policies, integrations. |
Built for speed
- Find anything: Ctrl K searches pages, projects and work items. Every work item number is unique across all projects, so
#101188works anywhere. - Change many at once: tick rows to change status, assignee, priority or sprint. Anything refused stays ticked to fix and retry.
- Spot duplicates early: similar items are listed as a new title is typed.
- Each project shapes its own forms: which fields appear, in what order, and which are required.
Why it matters for leadership
- Comparable delivery data across every team, because the structure is shared.
- Schedule commitments you can hold to account, because milestones keep their baseline.
- Lower onboarding cost for teams moving from Azure DevOps.
- A front door for requests that keeps stakeholders informed without chasing.
Step by step: Projects and the team, Backlog, sprints and board and Milestones and releases in the User guide.