Jira and Confluence: reliable execution data and an operating model people use

Where Jira and Confluence sit in the chain

In the Strategy-to-Execution chain, Jira carries execution and the work of teams, Confluence carries the operating model itself, and the portfolio side usually lives in Clarity or Planisware. Tools & Data describes how the three fit together. This page covers the execution and knowledge side.

Jira: the execution data

A hierarchy that reflects the model. Portfolio Epics, features, stories, and intermediate levels where your structure needs them. Every work item is linked to the initiative and the strategic theme it serves. That is what makes strategy traceable down to the teams.

Workflows that serve governance. Workflow schemes, fields, screens and permissions built to produce usable data, not piled up request after request. A Jira configured without a model produces a hierarchy that soon nobody respects.

Delivery, dependencies and capacity. Dependencies that are declared on both sides, team and train capacity, planning by increment. The data PI Planning and the portfolio need is produced by the work itself.

Flow metrics without data entry. Indicators are built on the history of transitions, not on declarative fields: actual cycle time, age of work in progress, arrival and completion rates, predictability, distribution by type of work. Nothing is asked of the teams, so the measures stay accurate over time.

Jira Align, where it is genuinely needed. Implementation and take-over, connecting trains, PIs, objectives and dependencies, and setting the boundary with Clarity when both are in place.

Confluence: the operating model, kept current

A reference that people use is not a document library. It is a space organised by role, where everyone finds what they have to do, when, and with whom.

• The governance reference: forums, agendas, decisions expected, funding and prioritisation rules.
• Decision processes: who decides what, in which forum, on what criteria.
• Journeys by role: Epic Owner, Business Owner, RTE, VMO, each with their responsibilities and their meetings.
• Automated deployment, so the reference can evolve without being rebuilt by hand, with restricted access where budget information requires it.
• AI-assisted knowledge management: pages updated when a rule changes, and an assistant that answers questions about the model and cites the source page. See AI-Augmented Strategy & Execution.

Connecting execution to the portfolio

Jira to Clarity or Planisware, Jira to finance tools and resource reference systems, with one source of truth for each data item and no manual reporting re-entry. That link is what allows the portfolio to decide on facts, and leadership to follow a priority all the way to the teams.

Common situations

A portfolio run in spreadsheets while everything happens in Jira. We put the missing hierarchy in place and build portfolio views directly on Jira data. The spreadsheet no longer has a reason to exist.

A Jira that every team has configured its own way. An audit of the schemes, a common foundation with the freedoms left to teams, and a gradual convergence plan. Dozens of Jira projects are not realigned in one go.

A governance reference nobody reads. Restructured by role rather than by document, with each forum described by its agenda and the decisions it is expected to take.

What it has made possible

Large services group. A complete Confluence governance reference, deployed with automated tooling and organised by role, with portfolio views fed from Jira. Read the case study