Azure DevOps
Azure Boards Pricing and Review: Backlogs, Sprints and GitHub
Azure Boards organizes engineering work into backlogs, boards and sprints, with capacity planning to help a team decide what it can take on. It is the planning part of Azure DevOps: you can use it while retaining GitHub repositories, so adopting a more structured backlog need not mean moving your code.
The strongest reason to consider it is the connection between a planned work item, a sprint commitment and implementation activity. Start with Boards and its access levels before estimating the cost of the wider DevOps platform.
From backlog to a sprint the team can staff
Boards supports Kanban and Scrum-style work, including setting sprint capacity. A useful evaluation starts with your actual work-item types, team and iteration dates. Those choices determine how the backlog represents your process; the product does not remove the need to agree what a ready or completed item means.
With a GitHub connection, work-item references can link commits and pull requests to the planned change. The documented Services integration supports GitHub.com and GitHub Enterprise Server. Repository administration and Azure project or collection permissions are part of setup. Agree how engineers will use AB# references, and avoid connecting the same GitHub repository across several Azure DevOps organizations: Microsoft warns that linking can behave unexpectedly in that arrangement.
Azure Boards pricing and who needs Basic
Azure DevOps Services pricing lists the first five Basic users free, with a per-user subscription beyond that allowance. Basic includes Boards, private Git repositories and specified pipeline and artifact allowances. Free Stakeholder access lacks the full agile tools and repository access, so it is unsuitable as a blanket substitute for engineer seats.
Basic + Test Plans is a separate per-user subscription. Choose it for test management; ordinary sprint planning uses Basic. Existing Visual Studio entitlements or eligible GitHub Enterprise access can affect incremental seat cost; compute, storage and security consumption also need their own estimate. Confirm these against the Services pricing page for your account.
Set up the connection; import work if switching
If you are moving existing work, CSV import/export provides a bulk work-item path. New records require Work Item Type and Title without IDs; updates use IDs. Process fields and identity formatting need checking. Rehearse records containing the history, attachments and relationships you rely on, because CSV support alone does not establish that all of them transfer.
Azure DevOps Services is the hosted offer described here. Server licensing, integration parity and operating responsibilities require a separate evaluation. Ask for the support response coverage your team requires before purchasing.
When to choose another approach
GitHub Projects is worth trying first when flexible boards and iteration fields beside existing issues meet the need. Jira is an alternative for configurable issue processes and cross-team planning. The software-team comparison helps separate those buying jobs.
For Boards, take a representative backlog, configure one team's capacity and link a pull request. Include a contractor in the access check; if switching, include a difficult record in an import rehearsal.