Do you need Jira Align? What Focus, Talent, Plans, and Product Discovery cover

Align (formerly Jira Align) is built for large organizations that run a scaled agile framework, with program increments planned across many teams. Most organizations that ask about it need something narrower, and Focus and Talent, with Jira Plans, Jira Product Discovery, and Atlassian Analytics, cover those jobs with less setup and without restructuring Jira first.

What Align is for

Align is Atlassian's enterprise portfolio execution app. It plans and tracks work across portfolios, programs, and teams, shows progress, risks, and dependencies across them, and maps capacity and investment to priorities. It supports SAFe, LeSS, Scrum@Scale, Disciplined Agile, the Spotify model, and custom or hybrid models. Teams keep working in Jira or Azure DevOps, and Align coordinates the layers above them, with work planned in program increments.

Align is now one of three apps in the Atlassian Strategy Collection, alongside Focus and Talent. The three are sold only together, and the collection requires Jira Cloud Premium at minimum. That changes the question. If you buy the collection, you already have Align, so the decision is not whether to pay for it but whether to implement it, and what covers the same jobs if you do not. For background on the collection itself, read Atlassian Strategy Collection explained.

The jobs people buy Align for

When teams say they need Align, they usually mean one or more of six jobs. Here is what covers each one without it.

Strategy to delivery alignment

Focus holds the strategy as a hierarchy of focus areas, one to ten levels deep, with goals or OKRs on each. It links Jira epics and anything above them from Premium and Enterprise sites, maps each Jira status to a Focus status, and rolls progress up the hierarchy. Insights flag overdue target dates, goals nobody has updated, and staffing gaps.

Portfolio and program planning

Jira Plans (formerly Advanced Roadmaps), included with Jira Premium and Enterprise, combines work items from boards, spaces, and filters into one plan across many teams. You can add hierarchy levels above epic, such as initiatives, roll up dates and estimates, auto-schedule work, and use a Program board that lays out scheduled work over a period of 7 to 16 weeks. Changes stay in the plan until you commit them to Jira.

Cross-team dependencies and capacity

Plans shows dependencies between work items, including ones that live outside the plan, and turns them red when they fall off track. It schedules against each team's capacity and velocity, and scenarios let you compare versions of the plan before you commit. Talent adds the people side: positions synced from your HR system and allocated to focus areas, so leaders see where positions against a priority are unfilled.

Idea intake and prioritization

Jira Product Discovery captures ideas and the insights behind them, including requests routed in from a Jira Service Management portal with an automation rule. Teams prioritize ideas in views such as a value against effort matrix and share roadmaps. A prioritized idea becomes a Jira epic, or links to an existing one, and Focus links that epic to a focus area. Atlassian does not document a direct link from Focus to ideas, so the epic is the handoff. Ideas can also appear as a field in Jira Plans and carry a Goals field tied to the same goals you attach to focus areas.

Workforce allocation

Talent reads position, worker, and organization data from Workday or an HRIS S3 connector, synced every six hours. Managers allocate positions in their reporting line and admins allocate in bulk. With labor rates turned on, Focus shows labor cost by focus area. Today a position can be allocated to one focus area.

Executive reporting

Focus rolls up work, goals, positions, and funds on every focus area, and Rovo can summarize a focus area before a review. For custom dashboards, Atlassian Analytics queries the Atlassian Data Lake, which holds Focus, Talent, Goals, Jira, and Jira Product Discovery data, and blends it across apps and sites. Analytics needs a Cloud Enterprise plan for Jira, Jira Service Management, or Confluence, and it is not part of the Strategy Collection. Atlassian has started renaming it Insights.

What this does not replace

This is not feature parity, and nobody should sell it as one. Align is organized around program increments, with agile teams, program teams, and portfolio teams, and with Jira fix versions arriving as release vehicles. It ships terminology sets for SAFe, Disciplined Agile Delivery, and LeSS, and lets you rename its major objects. It coordinates teams in Azure DevOps as well as Jira, while Focus links work from Jira and Align. Plans has a Program board and team capacity, but it is a planning view on top of Jira, not a framework.

When Align is still the right call

• You run a scaled framework with program increments across many teams. If SAFe or a similar model is how you plan, with shared increment planning across programs and portfolios, Align is built for that cadence.
• Delivery is split between Jira and Azure DevOps. Align coordinates both. Focus and Plans work from Jira.
• You already run Align well. Existing Jira Align customers can get Focus and Talent at no additional cost, and Atlassian Support can connect Align to Focus so Align epics roll up to focus areas. Keep what works and add Focus above it.
• Your program office needs framework terms on every screen. Align's terminology sets keep the words your teams were trained on.

Why the Focus and Talent path is easier to implement

The difference is what each path asks of Jira before leadership sees anything. According to Atlassian's Jira Align help center, the Align Jira connector needs:

• A dedicated Jira user for the integration, with a long list of space permissions, including Administer Jira, Browse spaces, Manage sprints, Edit work items, and Transition work items, plus the Browse Users and Groups global permission and its language set to English.
• The Story Points field editable by that user on the create and edit screens.
• Workflows that require only a reason when a work item changes state, and no other fields.
• Portfolios, programs, and program increments set up in Align before the connector runs, then each Jira space mapped to an Align program and each Jira board mapped to an Align team.
• Teams ready for a Jira epic to arrive in Align as a feature, not as an epic.

Atlassian's Align quickstart is written for Super Admins and says to complete the steps in order, and its Jira integration guide is written for Jira system administrators working with an Align solutions architect. None of that is unreasonable for a large program office. It is real work, and the plan stays in the deck while it happens.

Focus asks for less. An app admin connects Jira Premium or Enterprise sites from Focus admin settings, maps statuses, and links the epics and higher-level work that already exist. Focus does not map boards to teams or ask for workflow changes, and no shared cadence is required. Talent reads from your HR system, not from Jira. Plans works on the boards, spaces, and filters you already have, including team-managed spaces. Product Discovery hands off through ordinary Jira epics.

What the Focus path still asks of you

Easier does not mean no setup. Focus needs a hierarchy agreed with leadership before any focus area exists, and a status mapping for the workflows you link. A focus area holds up to 250 linked work items. If you want an initiative level above epic, that change applies to every company-managed space on the site and cannot be undone. Jira Product Discovery is a separate subscription billed per creator, and Atlassian Analytics needs an Enterprise plan. Analytics also does not apply row-level permissions from your apps, so scope its Data Lake connection with care.

How to decide

Start with Focus and Talent. Put the plan from your decks into Focus, allocate people in Talent, set goals top down, and link the Jira work that already exists, with Plans for the teams that plan together. If you then find that many teams need a shared increment cadence with planning at the program level, add Align and connect it to Focus. Our guide on scaled agile and governance covers how much framework you need, and Jira standardization before capacity planning covers the cleanup worth doing first.

Atlas Bench, an Atlassian Platinum Solution Partner, implements Focus, Talent, and the Jira around them as our Strategy Collection implementation.