Tag: Atlassian

Atlassian Usage-Based Pricing: What Your Overage Is Really Telling You 

Atlassian Usage Based Pricing

Starting December 3, Atlassian’s Usage-Based Pricing (UBP) model moves from a usage report in Atlassian Administration to a line item on the invoice. 

Key Takeaways

  • Starting December 3, Atlassian Usage-Based Pricing (UBP) moves from a usage report in Atlassian Administration to a line item on the invoice. 
  • UBP doesn’t fundamentally change how organizations license Atlassian products; usage-based charges apply only when consumption exceeds the monthly allowances included with a plan. 
  • Usage meters fall into three categories (Activity, Stock and Outcome), and each needs a different response. 
  • Before turning anything off, identify which meters drive consumption, which usage ties to business outcomes, and which exists because nobody has revisited the design. 
  • Cprime’s Assess, Right-size and Sustain approach helps manage UBP without slowing delivery or limiting adoption. 

Most conversations about UBP have focused on cost, which is understandable because nobody likes surprise charges. However, in conversations with customers, we’ve noticed a different concern emerging. While most people understand they’ll pay for overages, they’re less certain about what those overages actually mean and whether they represent a problem that needs to be addressed. 

An invoice can tell you what was consumed, but it can’t explain whether that consumption helped teams work more effectively, accelerated delivery, or improved service outcomes. That’s where interpretation becomes more important than the charge itself. 

How to Interpret Atlassian Usage Meters 

Not all usage meters behave the same way, which is why overages need to be evaluated differently depending on what is being measured. 

Category Examples You pay when The fix 
Activity Rovo credits, automation steps, Bitbucket build minutes Something runs Design and habits 
Stock Assets objects, Bitbucket storage You keep it, every month Hygiene and retention 
Outcome CSM AI agent resolutions A request is resolved without a person Quality and unit economics 

A spike in any of these categories can trigger an overage, but the appropriate response depends on what is actually being measured. 

What Atlassian Usage-Based Pricing Is and Isn’t 

Usage-Based Pricing doesn’t fundamentally change how organizations license Atlassian products. Most customers will continue to pay for subscriptions based on their existing plans, with usage-based charges applying only when consumption exceeds the monthly allowances included with those plans. 

The bigger shift is that platform usage becomes more visible and measurable. Activities that were previously viewed as background operations, such as automation execution, AI interactions, asset growth, and build consumption, now have a direct connection to operating costs. That visibility can help organizations make better decisions, but only if the data is viewed in context. 

For example, a spike in Rovo usage may indicate strong AI adoption, while increased automation consumption could point to both business growth and opportunities to simplify workflows. The objective isn’t to eliminate usage or keep every meter below its allowance at all costs. It’s to understand which activities support business outcomes and which patterns indicate inefficiencies that should be addressed. As teams, processes, and systems continue to evolve, managing usage becomes an ongoing operational responsibility rather than a one-time optimization effort. 

What to Do First About Atlassian UBP Overages 

The instinctive reaction to a potential overage is to start looking for things to turn off. That’s rarely the best place to start. 

Before making any changes, we recommend answering three questions: 

  • Which meters are driving consumption? 
  • Which consumption is tied to business outcomes? 
  • Which consumption exists simply because nobody has revisited the design? 

Those questions become the foundation of our Assess, Right-size, and Sustain approach. 

Assess 

The first step is establishing a baseline. Organizations need to understand which meters are consuming the most resources, who is driving that consumption, and whether it supports meaningful work or simply generates additional platform activity. 

For larger environments, this usually requires collaboration between administrators, platform owners, and business stakeholders. The goal is to determine which usage supports business outcomes and which activities can be reduced without affecting delivery, service, or development work. 

Right-size 

Once consumption patterns become clear, opportunities for improvement are usually easier to identify. Development teams often find opportunities within Bitbucket where adjustments to pipeline design, build frequency, and storage practices can reduce consumption without affecting delivery outcomes. Administrators reviewing Automation Steps frequently uncover legacy rules, duplicate automations, or inefficient workflows that continue to consume resources long after their original purpose has been forgotten. 

Adoption data becomes equally important at this stage because usage metrics alone don’t explain whether people are deriving meaningful value from the capabilities they’re consuming. 

Through Cprime’s System of Work Accelerator, organizations can compare platform usage against adoption patterns. That makes it easier to determine whether a source of consumption reflects meaningful business value or simply ongoing platform activity, helping teams avoid cutting capabilities they genuinely rely on. 

Sustain 

This is usually the step organizations underestimate. While allowances reset every month, usage patterns continue to evolve as teams create new workflows, adopt AI capabilities, expand projects, and connect additional systems. Organizations that stay ahead of UBP tend to establish clear ownership of key meters, review consumption trends regularly, and provide guidance that helps administrators and users make better decisions as the environment evolves. 

Ready for December 3? Prepare for Atlassian UBP 

The organizations that get ahead of UBP won’t necessarily be the ones with the lowest consumption. They’ll be the ones that understand what their usage is telling them and have a plan for acting on it. 

Cprime is offering a UBP Readiness Solution to help organizations understand their exposure before overages appear on invoices, identify the biggest drivers of consumption, and establish a practical plan that balances cost management with continued adoption of AI, automation, and service management capabilities. 

Take Control of Atlassian Usage-Based Pricing

Understand your usage exposure, identify high-impact opportunities to optimize costs, and build a practical plan to manage Atlassian Usage-Based Pricing without slowing delivery or limiting adoption.

Frequently asked questions (FAQs) 

When does Atlassian Usage-Based Pricing start appearing on invoices? 

Starting December 3, Atlassian’s Usage-Based Pricing (UBP) model moves from a usage report in Atlassian Administration to a line item on the invoice. 

Does UBP change how Atlassian products are licensed? 

No. UBP doesn’t fundamentally change how organizations license Atlassian products. Most customers continue to pay for subscriptions based on their existing plans, with usage-based charges applying only when consumption exceeds the monthly allowances included with those plans. 

What are the Atlassian usage meter categories? 

There are three: Activity meters (such as Rovo credits, automation steps and Bitbucket build minutes) charge when something runs; Stock meters (such as Assets objects and Bitbucket storage) charge when you keep something every month; and Outcome meters (such as CSM AI agent resolutions) charge when a request is resolved without a person. 

What should I do first if I expect an overage? 

Don’t start by turning things off. First identify which meters are driving consumption, which consumption is tied to business outcomes, and which exists simply because nobody has revisited the design. 

What is the Assess, Right-size and Sustain approach? 

It is Cprime’s three-step approach to managing UBP: establish a baseline of consumption (Assess), reduce inefficient usage without cutting capabilities teams rely on (Right-size), and assign meter ownership and review trends regularly (Sustain). 

Does an overage always mean something is wrong? 

No. A spike in Rovo usage may indicate strong AI adoption, while increased automation consumption could point to business growth as well as opportunities to simplify workflows. The goal is to understand which usage supports business outcomes, not to keep every meter below its allowance at all costs. 

How Finance and TBM Leaders Use AI Cost Management to Prove Value Before the Next Funding Review 

Finance and technology leaders reviewing AI costs against business outcomes ahead of a funding review

The next AI budget request lands on the table, and the first question is a simple one. What will we get for it? The usual answers sound reasonable. Unit costs are coming down, productivity should go up, and the business expects to run more efficiently. Each one expresses hope, but none of them ties the money to an outcome someone owns. 

In a webinar hosted by Cprime, Carollyn Gehrke, Digital Product Manager at Cprime, and Lauren Bateman, who leads Technology Business Management (TBM) Finance at FedEx, shared how they approach AI cost management. Their advice was to build evidence of value on purpose, well before anyone asks for it. 

AI consumption is up 30%. Is that good news? 

Gartner expects worldwide AI spending to reach $2.7 trillion in 2026, almost 50% more than the previous year. Closer to home, finance says AI spend is up 20%. The platform team reports consumption up 30%. Leadership wants to know if that’s good news, and neither number can say. If usage grew because people adopted the tool and saved thousands of hours, you have a strong story. If not, you’re holding cost nobody can defend. Part of the problem is that the answer sits across strategy, portfolio, finance, and technology teams. 

From pilot to production, the questions get harder 

Picture a customer service team piloting an AI assistant. Early on, it needs a real problem, a modest budget, and one person who decides whether the pilot continues. When the team wants to roll it out, the bar goes up. It now needs a value hypothesis, a baseline such as current resolution times, and someone to confirm the improvement is real. Once agents rely on it daily, the questions turn to run cost and whether usage still supports the business case. 

Finance’s role shifts too, from setting spending limits on experiments to confirming that run costs match the value the business signed up for. TBM for AI helps most when it covers that whole journey. 

Every token needs a business case 

Platform teams usually track compute, storage, tokens, and inference well. What’s missing is context, such as which priority a workload supports, which service benefits, and who owns the business case. Without it, a token count only tells you how busy the system was. 

Suppose the assistant’s costs jumped last quarter. If adoption grew and resolution times dropped, that may justify more investment. If adoption stayed flat, the same cost line tells a very different story. 

That context usually exists, spread across costing, planning, FinOps, and strategic portfolio management tools. TBM pulls it together and allocates cost to the services that use it. As Cprime’s look at cloud economics in the age of AI explains, FinOps for AI spots the spike in inference costs, and TBM shows which business service drove it and whether the outcome justifies it. 

One AI bill, three owners 

A workable split gives technology the platform and its efficiency, gives finance transparency and controls, and leaves the business accountable for the outcome. On a shared platform, each business unit needs to see what it uses and what it gets back. A good check is whether every cost can be traced to someone who answers for it, which gets easier once finance and IT are aligned through TBM. 

Governance should grow with the investment. Keep early experiments short, capped, and owned by a named person, and add visibility as a service reaches more users or handles more sensitive data and critical work. 

Measure AI ROI one decision at a time 

You don’t need a complete AI cost model to start. Pick a real decision, like expanding a pilot or renewing a platform contract. Define success, baseline the cost and consumption behind it, and link that baseline to the strategy, owner, and funding source. Then agree on who reviews it, how often, and what results mean you continue, adjust, or stop. 

At review time, compare results to the baseline, check unit economics like cost per transaction, and be honest about whether a pilot has failed or simply hasn’t had a fair run. The evidence only has to be good enough for the next decision. 

Where Cprime fits in 

Cprime, a TBM Council member, helps finance and technology leaders bring TBM, FinOps, and strategic portfolio management into one operating model. That work includes allocation models for shared platform costs and review cadences your teams can run themselves. Cprime’s Enterprise AI TBM Value Lifecycle Framework, covered in the webinar, follows each AI investment from pilot to production. 

Four questions to answer before your next funding review 

The next funding conversation will hinge on four things. What are you buying, for whom, why now, and what happens next? Without those answers, confidence in the next AI investment takes the hit. 

Start with the AI decision on your calendar next quarter. Name the person who’ll make it, and work out the minimum evidence they need. To see the full framework, watch the webinar on demand. 

Ready to prove the value of your next AI investment? 

Cprime helps finance and technology leaders connect TBM, FinOps, and strategic portfolio management so every AI dollar traces to an owner and an outcome. Talk to our experts about building the evidence your next funding review will ask for.

Frequently asked questions (FAQs) 

Is rising AI consumption a good sign?
Not on its own. A 30 percent rise in consumption or a 20 percent rise in AI spend cannot say whether the money is working. If usage grew because people adopted the tool and saved thousands of hours, that is a strong story. If not, it is cost nobody can defend.

How do AI cost questions change from pilot to production?
A pilot needs a real problem, a modest budget, and one person who decides whether it continues. A rollout needs a value hypothesis, a baseline such as current resolution times, and someone to confirm the improvement. In production, the questions turn to run cost and whether usage still supports the business case.

Why do AI token and inference costs need business context?
Platform teams track compute, storage, tokens, and inference well, but without context a token count only shows how busy the system was. Business context shows which priority a workload supports, which service benefits, and who owns the business case, so a cost spike can be judged against adoption and outcomes.

How do TBM and FinOps work together on AI costs?
FinOps for AI spots the spike in inference costs. TBM pulls together context spread across costing, planning, FinOps, and strategic portfolio management tools, allocates cost to the services that use it, and shows which business service drove the spike and whether the outcome justifies it.

Who should own AI costs?
Split ownership three ways. Technology owns the platform and its efficiency, finance owns transparency and controls, and the business is accountable for the outcome. On a shared platform, each business unit should see what it uses and what it gets back, and every cost should trace to someone who answers for it.

How do you measure AI ROI?
Start with one real decision, such as expanding a pilot or renewing a platform contract. Define success, baseline the cost and consumption behind it, and link it to the strategy, owner, and funding source. At review, compare results to the baseline and check unit economics like cost per transaction.

What questions should you answer before an AI funding review?
Four: What are you buying, for whom, why now, and what happens next? Without those answers, confidence in the next AI investment takes the hit. Start with the AI decision on your calendar next quarter, name the person who will make it, and work out the minimum evidence they need.

Atlassian Strategy Collection Explained: How Focus, Funds and Talent Connect Strategy to Spend 

Atlassian Strategy Collection demo: the Funds tab in Focus showing cost items for Xprime’s AI Engineering focus area

A leader asks why an initiative is $2M over forecast, and nobody can answer without building a spreadsheet first. Finance holds the budget while strategy teams own the priorities and delivery teams manage the work in Jira. Few organizations can follow a dollar from the priority it serves to the work it pays for. 

Atlassian Strategy Collection closes that gap by bringing strategy, money and people into the same system as the work. Leaders can then review each initiative with its goals, budget, staffing and delivery status in one view. Here is how its components fit together and how one initiative looks inside them. 

Focus, Funds and Talent at a glance 

Strategy Collection is organized around the priorities a company has already chosen. Focus and Talent are its core apps, and Funds adds the financial view inside them. 

Component What it connects What leaders get 
Focus Company priorities to focus areas, goals and initiatives Execution status that rolls up to leadership without anyone rebuilding a report 
Funds Budget, forecast, actuals and baseline to the initiatives they pay for Spend broken down by initiative and cost item, rather than one total per department 
Talent People, capacity and labor cost to the priorities they support A view of who is working on each priority and where staffing falls short 

Focus links each initiative to the work already underway in Jira, Jira Product Discovery, Atlassian Goals and Atlassian Projects. Teams keep working in the tools they use today, and the status leadership sees comes from that work directly. 

Following one initiative through the system 

Consider Xprime, a fictional enterprise software company with 18,500 employees. One of its strategic priorities is an engineering initiative with an FY26 budget of $50M, managed as a single focus area. The same setup applies to any priority, whether that is a platform modernization effort, a new product line or an operational efficiency program. 

Measure Value 
FY26 budget $50M 
Actuals to date $31.3M 
Variance vs. forecast –$1.78M 
Benefits realized so far $358K 

In Funds, the $50M is broken down into individual cost items, such as a $12M engineering team, contractors, infrastructure and software licenses, each phased month by month. When the initiative runs $1.78M off forecast, finance can see which cost items and which months account for the difference. Expected benefits are recorded next to the costs and tracked against what has been realized so far. 

In Focus, the same initiative rolls up to the goals and company priority it supports. In Talent, leaders can see which people are allocated to it and whether capacity matches the plan. Delivery status comes from the Jira projects where the work is being done. 

Watch the demo below which follows Xprime’s $50M budget from the focus area down to individual cost items and the benefits the initiative is expected to return. 

What changes for each leader 

The same connected view answers different questions depending on who is looking at it. 

  • Finance leaders see variance by cost item and month as it happens. 
  • Portfolio and strategy leaders can compare initiatives on cost, progress, staffing and benefits before deciding where to reallocate budget. 
  • Engineering and delivery leaders get status that flows from Jira without extra reporting and can use Talent to show where funded work is short of people. 

Setting up Strategy Collection for your organization 

Strategy Collection provides the structure, and the value depends on how it is configured. Every organization has to decide how its priorities cascade into focus areas, how its chart of accounts maps to cost items and how benefits are defined and signed off. Cprime works through these decisions with finance, PMO and engineering leaders, then connects Focus to existing Jira and Jira Product Discovery instances so data flows without manual reporting. As an Atlassian Platinum Solution Partner specializing in Enterprise Strategy & Planning, Cprime brings deep implementation experience to each Strategy Collection rollout. 

For a detailed Xprime walkthrough and the complete framework, download our eBook on Atlassian Strategy Collection, Spend That Can Defend Itself. 

Follow every dollar from priority to work

Get the full Cprime walkthrough and the complete framework for connecting strategy, spend and people with Focus, Funds and Talent in Atlassian Strategy Collection.

Frequently asked questions (FAQs) 

What is Atlassian Strategy Collection?
Atlassian Strategy Collection brings strategy, money and people into the same system as the work. Leaders can review each initiative with its goals, budget, staffing and delivery status in one view, instead of building a spreadsheet to answer basic questions about spend.

What are Focus, Funds and Talent in Atlassian Strategy Collection?
Focus connects company priorities to focus areas, goals and initiatives. Funds connects budget, forecast, actuals and baseline to the initiatives they pay for. Talent connects people, capacity and labor cost to the priorities they support. Focus and Talent are the core apps, and Funds adds the financial view inside them.

Do teams have to stop using Jira to use Strategy Collection?
No. Focus links each initiative to the work already underway in Jira, Jira Product Discovery, Atlassian Goals and Atlassian Projects. Teams keep working in the tools they use today, and the status leadership sees comes directly from that work.

How does Funds help explain budget variance?
Funds breaks a budget into individual cost items, such as teams, contractors, infrastructure and software licenses, each phased month by month. When an initiative runs off forecast, finance can see which cost items and which months account for the difference. Expected benefits are tracked against what has been realized.

How does Strategy Collection help different leaders?
Finance leaders see variance by cost item and month as it happens. Portfolio and strategy leaders can compare initiatives on cost, progress, staffing and benefits before reallocating budget. Engineering and delivery leaders get status that flows from Jira and can use Talent to show where funded work is short of people.

What needs to be decided when setting up Atlassian Strategy Collection?
Each organization has to decide how its priorities cascade into focus areas, how its chart of accounts maps to cost items, and how benefits are defined and signed off. Cprime works through these decisions with finance, PMO and engineering leaders, then connects Focus to existing Jira and Jira Product Discovery instances.

FinOps vs. ITFM vs. SPM vs. AI Governance: Why Four Disciplines Still Can’t Answer One Question 

Comparison of FinOps, ITFM, SPM and AI governance by core question, owner, unit of analysis and limitation

Most leadership teams can say what they spent on technology last year, but few can answer the question boards are now asking: is our technology spend funding the right work? AI has made the gap harder to ignore, with 93% of organizations exceeding their AI budgets (McKinsey) and 56% of CEOs reporting no significant financial benefit from AI (PwC). 

FinOps, IT Financial Management (ITFM), Strategic Portfolio Management (SPM) and AI governance each answer part of that question, but none was built to link spend to the priority it supports. Here’s where each discipline’s view ends, and how the four can be connected. 

How the four disciplines compare 

 FinOps ITFM SPM AI governance 
Core question Is cloud spend efficient? Where is the IT budget going? Which initiatives come first? What is AI costing, and what are the risks? 
Typical owner FinOps team, cloud CoE CIO office, IT finance, TBM office PMO, portfolio and product leaders Chief AI Officer, risk, legal, AI CoE 
Unit of analysis Accounts, workloads, tags Cost pools, towers, services Priorities, initiatives, value streams Models, use cases, policies 
Limitation Measures efficiency, not alignment with priorities Explains cost, not strategic value Tracks priorities, usually without actual cost Manages risk, not portfolio trade-offs 

FinOps 

FinOps manages cloud spend through rightsizing, commitment coverage and unit cost. It shows whether resources are used efficiently, but not whether the workloads support a current priority, and it misses the labor, licenses and contracts outside the cloud bill. Cprime’s FinOps practitioners typically start with a maturity assessment and build the practice in stages, from tagging and cost allocation to showback, chargeback and shared forecasting. 

ITFM 

ITFM uses the Technology Business Management (TBM) taxonomy to allocate the full cost of technology to IT services and the business units that consume them. It can show that a business unit consumed $8M in application services, but not whether that spending advanced the strategy. Cprime helps IT finance teams design TBM-aligned cost models and set up the planning and forecasting cycles that make them useful to business leaders. 

SPM 

SPM decides which initiatives are funded and staffed, and in what order, often through Lean Portfolio Management. It usually works from planned budgets rather than actual cost, which matters more as cloud and AI usage vary month to month. Cprime’s SAFe-aligned Lean Portfolio Management practice designs the portfolio processes, including strategic themes, portfolio Kanban and Lean budgeting. See how Chevron improved financial alignment through strategic portfolio management with Cprime. 

AI governance 

AI governance keeps track of the models and use cases in play, sets policy, manages risk and increasingly monitors costs such as tokens, inference and licenses. It isn’t built to decide whether a use case deserves funding over other investments, and much of what AI actually costs is spread across cloud bills, software contracts and payroll, outside governance’s view. Cprime closes that gap by running AI use cases through the same portfolio and funding processes as any other investment, so each one has a sponsor, a full cost profile and an expected outcome. 

Connecting the four disciplines 

Pulling all four data sets into one dashboard rarely helps, because the disciplines use different units, schedules and definitions of cost and value, and no one owns the connections between them. What works is a shared operating model that traces cloud spend to budget, budget to priority and priority to results, with AI investment held to the same standard. 

Cprime builds it with practitioners who have run FinOps, ITFM, SPM and AI governance programs inside large enterprises, working alongside specialists in Agile transformation and organizational change management. Our engagements move through four stages: 

Align the business: map leadership’s priorities, decisions and funding gates in one view, signed off by executives before anything is built. 

Design the system: turn that map into a single model connecting strategy, funding and people, with guides and runbooks generated from it. 

Activate the change: train teams and give them an AI agent that explains why the system works the way it does. 

Evaluate and regenerate: assess every change for effort, risk and cost before it’s built, with documentation updating automatically. 

How tooling fits 

Cprime’s approach doesn’t depend on any single platform. Many organizations already use tools for one or more of these disciplines, and the operating model can be built around what’s in place. 

IBM Apptio’s portfolio spans cloud cost management, IT financial management and strategic portfolio management. Cprime is a long-standing IBM Apptio partner and was named Apptio’s Americas SPM Partner of the Year for 2025. 

Atlassian Strategy Collection connects strategic priorities, budgets and people to the work teams manage in Jira. Cprime is an Atlassian Platinum Solution Partner, with specializations in Enterprise Strategy & Planning, Service Management and Cloud Migration. 

To see how this operating model comes together in Atlassian Strategy Collection, download our eBook, Spend That Can Defend Itself, which walks through how Focus, Funds and Talent connect strategy, spend and people. 

Make every technology dollar defend itself

See how Focus, Funds and Talent connect strategy, spend and people in Atlassian Strategy Collection, so you can show leadership which priority each dollar of technology and AI spend supports.

Frequently asked questions (FAQs) 

What is the difference between FinOps, ITFM, SPM and AI governance?
FinOps checks whether cloud spend is efficient. ITFM shows where the IT budget goes. SPM decides which initiatives come first. AI governance tracks what AI costs and the risks it carries. Each one answers part of the spending question, but none links spend to the priority it supports.

Why can’t FinOps show whether cloud spend supports business priorities?
FinOps measures efficiency through rightsizing, commitment coverage and unit cost. It shows whether resources are used well. It doesn’t show whether the workloads support a current priority, and it doesn’t cover the labor, licenses and contracts that sit outside the cloud bill.

How does ITFM use the TBM taxonomy?
ITFM uses the Technology Business Management (TBM) taxonomy to allocate the full cost of technology to IT services and the business units that consume them. That explains where costs land, but not whether the spending advanced the strategy.

Why does strategic portfolio management struggle with cloud and AI costs?
SPM usually works from planned budgets rather than actual cost. That gap grows as cloud and AI usage vary from month to month, so portfolio decisions can rest on numbers that no longer match what is actually being spent.

Where does AI governance fall short on AI investment decisions?
AI governance tracks models and use cases, sets policy, manages risk and increasingly monitors costs such as tokens, inference and licenses. It isn’t built to decide whether a use case deserves funding over other investments. Much of AI’s real cost also sits in cloud bills, software contracts and payroll, outside governance’s view.

How can organizations connect FinOps, ITFM, SPM and AI governance?
Combining all four data sets in one dashboard rarely works, because the disciplines use different units, schedules and definitions of cost and value. What works is a shared operating model that traces cloud spend to budget, budget to priority and priority to results, with AI investment held to the same standard.

Atlassian Team ’26 Europe: What Cloud Leaders Asked and Why Tools Alone Don’t Change Outcomes 

Cprime team at the Atlassian Team ‘26 Europe booth in Amsterdam

One question kept coming up in Amsterdam 

The licences are bought, the data has moved, and people have logged in. So why does the business case still feel like a promise? We heard some version of that question at the Cprime booth during Atlassian Team ’26 Europe (6 to 8 October 2026, RAI Amsterdam). For years, the hard part was the Atlassian Cloud migration. Now leaders want to know when the return shows up. 

Key takeaways from Atlassian Team ’26 Europe 

  • Rovo AI: start with two or three repetitive tasks, such as the weekly status report, and track the hours saved before scaling. 
  • Ways of working: treat the Atlassian Cloud migration as day one. Simplify workflows, agree what “done” means, and give leaders one dashboard they trust. 
  • Usage-based pricing: audit licences and apps, remove dormant accounts and duplicate apps, and link remaining spend to outcomes. 
  • Apps and Data Center: Atlassian Cloud now handles much of what custom apps did. Rebuild only the logic that sets your business apart on Atlassian Forge. 
  • Jira Service Management: connect JSM to Jira and Confluence early so service, engineering, and knowledge work from the same picture. 

From migration to momentum 

The leaders we met at the event have already moved to Atlassian Cloud and are curious to know what comes next. Our answer is simple: tools alone don’t change outcomes. The platform creates the opportunity, and the value comes from how teams plan, collaborate, and deliver on it every day. When ways of working evolve alongside the technology, the return follows. 

Five themes stood out. Each one shows where that shift is already happening, and where the biggest opportunities are waiting. 

1. From access to adoption: making Rovo AI count 

Many teams already have Rovo AI (Atlassian’s AI for search, chat, and agents), and the leaders we met are eager to make the most of it. Their questions were practical. What should we automate first? Which Rovo use cases are worth the effort, and how do we prioritise? How do we show the business it’s paying off? 

We’ve found that teams who see results start small and stay focused. Rolling Rovo out to everyone at once makes it hard to build new habits or measure impact. A few targeted use cases build momentum quickly. 

Where to start: pick two or three time-consuming, repetitive tasks. The weekly status report is a great example. Someone in the PMO often spends half a morning pulling updates from Jira and Confluence. A Rovo agent can draft it in minutes, and the project lead reviews it and hits send. Track the hours saved for a month, share the results, then take on the next task. 

2. Atlassian Cloud has changed the platform, but not the way of working 

Most leaders we spoke to moved to Cloud for faster releases, better visibility, and less overhead. A lot of them haven’t seen those yet. It’s a familiar pattern. A company lifts dozens of Jira projects into Cloud, complete with the custom fields, workflows, and five-step approvals someone built ten years ago. The clutter comes along for the ride, so reports stay slow and planning still lives in spreadsheets. 

What helps: treat migration as day one, because the value comes from what you change after go-live. Strip back the workflows, agree on what “done” means, and give leaders one dashboard they trust.  

The same thinking applies at portfolio level. With its Strategy Collection, Atlassian is moving beyond work management by connecting strategy and investment to delivery. Its portfolio management capabilities are becoming a real alternative to traditional platforms. At Cprime, we’re exploring this with customers now and working closely with Atlassian’s Strategy Collection team as the offering evolves. 

Underneath it all sits the Teamwork Graph, the connected layer that links goals, people, knowledge, and work across Atlassian. The intelligence is already there. The opportunity is to use it better by keeping strategy, knowledge, and execution aligned. Our System of Work Accelerator, which we demonstrated to customers in Amsterdam, is a practical place to start. It shows how you’re using your Teamwork Graph today and where to strengthen your data and connections to support Rovo and your strategic goals. Pair that with the right skills and habits, and leaders can see how work contributes to their objectives and show what AI is really delivering.  

3. Atlassian usage-based pricing puts every licence in the spotlight 

The shift to Atlassian usage-based pricing has put cost firmly on the agenda. When you pay for what you use, every app and automation needs a reason to exist. Finance spots the gaps fast, and “Are we getting value?” stops being a feeling and becomes a number someone has to stand behind. 

A practical first step: audit what you’re paying for, check who actually uses it, and cut what nobody needs. Dormant accounts and two apps doing the same job are the usual quick wins. Then link what’s left to the outcomes it supports, so your next budget meeting starts with evidence. Our System of Work Accelerator FAQs go deeper. 

4. Moving from Data Center to Cloud: your apps may not be the blocker you think they are 

For teams still on Data Center, the biggest worry about moving to Cloud is their apps. Years of ScriptRunner scripts and custom apps now support critical processes, and rebuilding them feels risky, expensive, and disruptive. The good news is that Atlassian Cloud now handles much of that work out of the box. The custom logic that truly sets your business apart can be rebuilt on Atlassian Forge, Atlassian’s cloud app development platform, allowing you to keep what matters, simplify what doesn’t, and open the door to Cloud capabilities like Rovo along the way. 

Before you decide: take a fresh look at your apps. Our Cloud Migration Blueprint maps what can move as is, what Cloud already handles, and what’s worth rebuilding, so you can reduce your migration scope and your licence bill in one go. 

5. Beyond the help desk: Jira Service Management steps up for IT service 

Interest in Jira Service Management (JSM) went far past basic ticketing. Leaders want one connected IT service management (ITSM) platform for incidents, changes, problems, and assets, so their teams can resolve issues faster and see what’s really driving them. 

Picture a bank’s mobile app going down. The incident in JSM links to the Jira ticket for the fix, and the fix links to the Confluence page that explains what happened. Everyone works from the same picture, and Rovo can surface answers faster because the knowledge is already connected. 

Make it count: connect JSM to the rest of your Atlassian tools early. The sooner service, engineering, and knowledge sit together, the faster your teams can move from firefighting to improving. We’ve seen what this makes possible. For one Fortune 50 technology company, we built a JSM solution that cut average handling time by 15 minutes per issue and is forecast to save millions of dollars a year. 

A theme to watch: developer experience 

Developer experience came up again and again at the event. Engineering leaders want a clearer view of how their teams deliver, and whether their growing AI investment is paying off. It’s the same question behind all five themes: are your tools changing how work actually gets done? For product and engineering teams, Rovo-augmented product development is how we help answer it, by bringing AI into planning, building, and shipping so leaders can see the impact. 

How Cprime turns Atlassian investment into impact 

Our insights come from more than 20 years of helping organisations change how they work. When PayPal moved to Atlassian Cloud, we helped rework its workflows and improve the developer experience for more than 35,000 active users, as part of the largest Atlassian Cloud migration in history. It’s also why Atlassian named us its Partner of the Year for Cloud Transformation Services. 

If you want your Atlassian investment to pay back, here’s where we’d put your energy: 

  • Changing how teams work: Treat Cloud as an operating model shift and plan for it that way. Plenty of partners can move your data, but the bigger gains come from rethinking how teams plan, track, and deliver once they’re there. That’s why large organisations often migrate with one partner, then bring Cprime in for this part. 
  • Adoption that sticks: Put as much effort into your people as into the platform. Atlassian has made adoption a top priority, and it should be yours too. Rovo and Cloud only pay off when teams know how to use what they already have, so start with a few proven use cases, train the people who’ll use them, and keep building new habits around them. 
  • Going deep where it counts: Resist the urge to fix everything at once. Pick the few areas where value is leaking most and get those right first. For the leaders we met, that meant getting more value from Atlassian Cloud, driving Rovo AI adoption, or expanding JSM across IT service. It’s the same focus we apply to our own work. 

Ready to get more from Atlassian Cloud?

On Cloud but not seeing the return yet? Book a System of Work Accelerator conversation. We’ll look at how AI-ready your setup is and show you where to act first.

Frequently asked questions (FAQs) 

What were the main themes at Atlassian Team ‘26 Europe?
Leaders who had already moved to Atlassian Cloud wanted to know when the return shows up. Five themes stood out: making Rovo AI adoption count, changing ways of working after migration, managing cost under usage-based pricing, rethinking apps when moving from Data Center, and expanding Jira Service Management for IT service. Developer experience was a theme to watch.

How should teams get started with Rovo AI?
Start small and stay focused. Pick two or three time-consuming, repetitive tasks, such as the weekly status report. A Rovo agent can draft it in minutes for a project lead to review. Track the hours saved for a month, share the results, then take on the next task.

Why isn’t Atlassian Cloud delivering a return yet?
Often the old ways of working moved with the data, including legacy custom fields, workflows, and approvals. The value comes from what you change after go-live: strip back the workflows, agree on what “done” means, and give leaders one dashboard they trust.

How does Atlassian usage-based pricing change licence management?
When you pay for what you use, every app and automation needs a reason to exist. Audit what you’re paying for, check who actually uses it, and cut what nobody needs. Then link what’s left to the outcomes it supports.

Are apps a blocker for moving from Data Center to Atlassian Cloud?
Not always. Atlassian Cloud now handles much of the work that ScriptRunner scripts and custom apps once did, and the custom logic that sets your business apart can be rebuilt on Atlassian Forge. Cprime’s Cloud Migration Blueprint maps what can move as is, what Cloud already handles, and what’s worth rebuilding.

How does Jira Service Management improve IT service?
Jira Service Management brings incidents, changes, problems, and assets onto one connected platform. When an incident links to the Jira ticket for the fix and the Confluence page that explains it, everyone works from the same picture, and Rovo can surface answers faster. For one Fortune 50 company, Cprime’s JSM solution cut average handling time by 15 minutes per issue.

What is the Cprime System of Work Accelerator?
The System of Work Accelerator shows how you’re using your Teamwork Graph today and where to strengthen your data and connections to support Rovo and your strategic goals. Cprime demonstrated it to customers in Amsterdam, and it’s a practical place to start if you’re on Cloud but not seeing the return yet.

The Hidden Cost of a Drifting Targetprocess Environment 

AdobeStock_1930309210

Picture the quarterly investment review. The portfolio report shows one number. A business leader quotes another from a spreadsheet. Everyone turns to the one administrator who knows how the report is built. 

If that sounds familiar, your platform may have drifted. Drift is common in Targetprocess environments because the platform is so flexible. It adapts to how each team and portfolio work. But without a shared operating model to guide that flexibility, small and reasonable changes add up, and the leaders accountable for investment decisions end up paying for it. 

To help Apptio Targetprocess customers get more value from their platform, Cprime hosted an IBM Targetprocess webinar led by Solutions Advisor Carollyn Gehrke. Drawing on nearly 30 years in technology business management (TBM), portfolio, and product management, she explained how drift happens and how to reverse it. 

How platforms drift 

Carollyn compares a Targetprocess environment to a growing city. In her analogy, roads are the workflows and fields that move work through the system. Neighborhoods are the teams and portfolios that use it. Street signs are the views and reports people rely on to find their way. Detours are the exceptions added to meet an urgent need. 

No city decides to become hard to navigate. It happens one road at a time, until residents know where they want to go but not how to get there. Targetprocess grows the same way. An urgent report gets a new field, one team gets its own workflow, and one leader gets a custom view. Over time, the configuration reflects years of requests more than the strategy it was built to serve. 

When people get lost, it is easy to blame the tool. However, the real causes are usually unclear ownership, inconsistent processes, undocumented decisions, and unmanaged change. 

Targetprocess may be where the problem becomes visible. It is rarely where the problem begins. 

Why one fix is never enough 

Three problems drain value from portfolio platforms, and each one fuels the next. 

  1. Complexity comes first. Flexibility turns into risk when fields, workflows, and reports stop working as one system. 
  1. Adoption follows. If leaders quote numbers the system does not show, the platform is being worked around. 
  1. Key person dependency completes the set. The environment becomes fragile when one person holds every shortcut and hidden connection. 

For TBM leaders, the impact is concrete. When the data behind funding decisions is uncertain, every investment call carries more risk. 

If your Targetprocess expert left tomorrow, what would be at risk? 

Most Targetprocess environments have one person who knows every shortcut, exception, and workaround. Four questions show how exposed you are. Who understands why the configuration works the way it does? Where are decisions and exceptions recorded? Who can fix a broken report or integration? How quickly could someone else take over? 

If every answer points to the same name, you have a key person dependency. These experts are extremely valuable, so the goal is to turn what they know into something the whole organization owns. 

Treat the platform as a product 

TBM leaders already manage technology spend as a portfolio. The platform behind enterprise agile planning deserves the same discipline. 

Start with strategy, then decide what to fund, change, continue, and stop. Design the data, workflows, and views those decisions need, plan for adoption, and measure whether the investment delivers. Most organizations start by asking what the tool can do. A better first question is which decisions the business needs to make. 

Targetprocess best practices 

You do not need to start over. A five-step framework fixes what you already have. 

  • Stabilize by finding the problems that matter most. 
  • Standardize how changes are approved, documented, and managed. 
  • Enable people with documentation and training they can actually use. 
  • Align platform priorities with your portfolio strategy. 
  • Sustain progress by tracking usage, technical health, and integration reliability. 

To make the gains last, document the intent behind each configuration decision and design views around the decisions people actually make. 

Start small. In the first 30 days, run a Targetprocess configuration health check to find your biggest risks, dependencies, and most valuable use cases. Over the next quarter, set clear ownership, governance, and support. After that, share the platform roadmap openly and keep improving with intent. 

The cost of waiting 

Invest 10 to 15 percent annually in user adoption and understanding. It may sound high. But count what complexity already costs. Leaders stop trusting reports. Administrators lose weeks to exceptions. Teams build workarounds. The organization changes while the system stands still. 

Complexity carries a cost. It just never appears on the budget. 

Stabilizing the platform protects what you have already invested. Leaders get numbers they can trust, knowledge stays inside the organization, and more people use the system. 

Building a platform leaders trust 

Picture the end state. Configuration is simple. Decision rights are clear. Leaders trust the data enough to fund from it. No single person holds all the keys. 

Getting there starts with a new question: how will the platform keep supporting growth, governance, and investment decisions as the organization changes? 

When ownership is clear and every change connects to strategy, Targetprocess becomes a trusted view of where the organization stands and where its investments should go. 

Watch the on-demand webinar for practical steps to simplify your Targetprocess environment and strengthen adoption. 

How can Cprime help 

Cprime works alongside technology finance and portfolio leaders to assess platform health, establish the operating model, and build the internal capability to sustain it. Your team keep ownership of the decisions. If your environment feels harder to manage each quarter, a Targetprocess configuration health check is a practical place to start

Frequently asked questions (FAQs) 

Why do Targetprocess environments drift? 

Targetprocess is flexible enough to adapt to how each team and portfolio works. Without a shared operating model guiding that flexibility, small and reasonable changes, such as a new field for an urgent report, a team-specific workflow, or a custom view for one leader, add up until the configuration reflects years of requests more than the strategy it was built to serve. 

Is Targetprocess itself the cause of configuration problems? 

Rarely. The real causes are usually unclear ownership, inconsistent processes, undocumented decisions, and unmanaged change. Targetprocess may be where the problem becomes visible, but it is rarely where the problem begins. 

What three problems draining value from portfolio platforms like Targetprocess? 

Complexity, adoption, and key person dependency. Complexity turns flexibility into risk when fields, workflows, and reports stop working as one system. Low adoption shows up when leaders quote numbers, the system does not show. Key person dependency makes the environment fragile when one person holds every shortcut. Each problem fuels the next. 

How do you know if your Targetprocess environment has a key person dependency? 

Ask four questions: Who understands why the configuration works the way it does? Where are decisions and exceptions recorded? Who can fix a broken report or integration? How quickly could someone else take over? If every answer points to the same name, you have a key person’s dependency. 

What are the Targetprocess best practices for fixing a drifting environment? 

Use a five-step framework: Stabilize by finding the problems that matter most; Standardize how changes are approved, documented, and managed; Enable people with usable documentation and training; Align platform priorities with portfolio strategy; and Sustain progress by tracking usage, technical health, and integration reliability. 

Where should you start when fixing Targetprocess configuration drift? 

Start small. In the first 30 days, run a Targetprocess configuration health check to find your biggest risks, dependencies, and most valuable use cases. Over the next quarter, set clear ownership, governance, and support. After that, share the platform roadmap openly and keep improving with intent. 

How much should organizations invest in Targetprocess adoption? 

Invest 10 to 15 percent annually in user adoption and understanding. Without it, complexity carries a hidden cost: leaders stop trusting reports; administrators lose weeks to exceptions, and teams build workarounds. 

Jira Service Management Won’t Fix a Broken ITSM Process. ITIL Can

IT service team mapping ITIL practices before configuring Jira Service Management

Many IT leaders believe the right platform will fix their service desk. Swap the old ticket log for a modern suite, and efficiency should follow. 

It won’t. Software is an amplifier. Digitize a chaotic process, and you get automated chaos. ITIL practices give the process its shape before the platform scales it. 

Cprime sees this pattern often in service management engagements. In a recent onboarding review, the lead of a specialized healthcare IT team described the starting point plainly: 

“The team’s processes are very far from being matured. There is very little documentation… A lot of the ITIL stuff they hadn’t heard of ITIL until I turned up.” 

Much of the team’s knowledge lived in people’s heads rather than in documented processes. That detail separates a high-return transformation from an expensive one. Improving service management is more than a technology project. It is a chance to establish a better way of working. 

What happens when ITSM processes aren’t mature? 

A new service desk can expose process gaps, but it won’t resolve them on its own. The same is true of an existing platform carrying years of configuration and workarounds. 

When teams lack consistent ITIL-aligned practices, three problems tend to emerge: 

  1. Tribal knowledge replaces standard workflows. Issues get resolved based on who answers the phone, rather than a defined incident management practice. 
  1. Root causes stay hidden. Without formal problem management, teams spend most of their bandwidth fighting the same fires. 
  1. Process feels like an uphill struggle. As the team lead noted, introducing service management into an unstandardized environment is hard. Resistance is high when process has never been taught. 

The result isn’t necessarily a bad service desk. It’s a service management operation without a consistent operating model behind it. 

Jira Service Management is a force multiplier for good process 

Jira Service Management gives organizations a flexible platform that connects service teams, development, operations, and the wider business. Flexibility, however, is different from process maturity. 

If workflows, ownership, escalation paths, and service definitions are unclear, configuration alone won’t solve the problem. Think of it this way: 

  • Immature processes + modern technology = faster execution of inconsistent processes 
  • Defined ITSM practices + modern technology = scalable service management 

The technology matters. What you choose to standardize, automate, measure, and improve matters just as much. 

Start with ITIL practices, then configure the platform 

The most important work in a JSM implementation happens before configuration begins. The same principle applies when you improve an existing service management environment. 

1. Define how work should flow 

Start with the core ITIL practices that matter most to your organization. Then answer the operating questions behind them. How should incidents be classified and prioritized? What qualifies as a service request? When does an incident become a problem? Who owns each stage? Which changes need review or approval? 

These decisions form the foundation for effective service management. They apply whether you are implementing JSM for the first time or improving an existing environment. 

2. Standardize before you customize 

It’s tempting to recreate every workflow and workaround from a legacy service desk. Resist that instinct. 

Use proven ITSM and ITIL best practices as your starting point. Then decide where your organization has legitimate reasons to vary. The goal is to build a better service desk, rather than reproduce the old one on a new platform. 

3. Build capability alongside the technology 

Process maturity doesn’t come from configuration alone. Teams need to understand the practices they’re adopting and why those practices matter. 

That means giving service teams the knowledge to manage incidents, problems, changes, and requests consistently. It also means building workflows that make those practices easier to follow. For teams that need stronger internal ITIL knowledge, Cprime offers ITIL 5 Foundation training alongside transformation work. 

Questions to answer before you configure JSM 

Before you build workflows, automation, or custom fields, make sure your team can answer these questions: 

  • What does good incident management look like for our organization? 
  • How do we distinguish an incident, a problem, and a service request? 
  • Who owns each stage of the service management process? 
  • What is our change enablement process? 
  • Which processes should be standardized across teams? 
  • Where do we genuinely need to customize? 
  • What should we automate, and what still requires human judgment? 
  • How will we measure whether service delivery is improving? 

If these questions lack clear answers, configuration shouldn’t be the first step. 

What an ITIL-aligned service management environment looks like 

An effective service management transformation brings process and technology together in three layers. 

Establish the foundation: Define and align core ITSM practices using ITIL as the framework. Account for your organization’s specific services, teams, and operating model. 

Configure for the way work should happen: Translate those practices into JSM workflows, request types, queues, SLAs, automation, and reporting. Avoid over-customizing the platform. 

Enable the people who run it: Give teams the training to use new processes well and keep improving them after go-live. 

For organizations with more complex needs, this can extend into broader service management transformation. JSM then connects development, operations, and business teams into a more consistent service experience across the enterprise. 

How Cprime brings ITIL expertise to service management 

As an Atlassian Platinum Solution Partner with an ITSM specialization, Cprime applies deep ITIL expertise across its service management work. Whether you’re implementing JSM, migrating from a legacy desk, or fixing an underperforming operation, we start with the process. 

Our teams bring practical ITIL knowledge to assessments, process design, workflow development, JSM implementations, migrations, and ongoing optimization. We help you find where service management is breaking down and establish more effective practices. Then we use technology to make those practices scalable and measurable. 

As a result, you don’t have to choose between process expertise and technology expertise. Cprime brings both together, so service management works for the people who run it and the business they support. 

To go deeper, read Cprime and ITIL: The Key to Unlock Optimized ITSM. 

Ready to fix the process before you configure the platform?

Talk to Cprime’s service management experts about where your ITSM practices stand today. We’ll help you define ITIL-aligned processes first, then configure Jira Service Management to scale them.

Frequently asked questions (FAQs) 

Can Jira Service Management fix a broken ITSM process? 

Not on its own. Jira Service Management amplifies the process you give it. If workflows, ownership, and service definitions are unclear, configuration only speeds up inconsistency. Define ITIL-aligned practices first, then configure JSM to make them scalable. 

What is the difference between ITIL and ITSM? 

ITSM (IT service management) is how an organization designs, delivers, and supports IT services. ITIL is the most widely used framework of best practices for doing ITSM well. It covers practices such as incident, problem, change, and service request management. 

Does Jira Service Management support ITIL practices? 

Yes. JSM supports ITIL-aligned practices such as incident management, problem management, change enablement, and service request management. It does this through workflows, request types, queues, SLAs, and automation. Your team still needs to define how those practices should work. 

What should we define before configuring Jira Service Management? 

Define how incidents are classified and prioritized, what counts as a service request, and when an incident becomes a problem. Also agree who owns each stage, which changes need approval, and how you will measure service delivery. 

What is the difference between an incident, a problem, and a service request? 

An incident is an unplanned interruption or drop in quality of a service. A problem is the underlying cause of one or more incidents. A service request is a user asking for something standard, such as access or new equipment. 

Should we recreate our legacy service desk workflows in JSM? 

Usually not. Recreating every legacy workflow carries old workarounds into the new platform. Start from proven ITIL best practices instead, then customize only where your organization has a legitimate reason to vary. 

Do service teams need ITIL training for a JSM implementation? 

Training works best alongside the implementation. Teams follow practices more consistently when they understand why each one matters. Cprime offers ITIL 5 Foundation training to help service teams build that knowledge during their transformation. 

Why Atlassian Rovo Alone Doesn’t Improve Delivery (and What Closes the Gap) 

Delivery leader reviewing Atlassian Rovo sprint insights connected to Jira and DevOps signals

Key takeaways 

  • Atlassian Rovo improves delivery only when it is designed into sprint, release, and dependency workflows. 
  • DORA’s 2025 research finds that AI amplifies an organization’s existing strengths and weaknesses. 
  • Four gaps stall delivery impact: design, integration, validation, and adoption. 
  • Closing those gaps turns Rovo from AI search into delivery intelligence that leaders can measure. 

For delivery leaders, the next question is how that capability translates into measurable improvements in delivery. 

Are teams identifying risks earlier? Are sprints becoming more predictable? Is less time spent assembling status updates? 

Access to AI tools alone doesn’t guarantee these outcomes. Realizing value depends on how teams use Rovo within their existing delivery processes and workflows. 

This article explores the gap between AI access and delivery impact, what recent research suggests, and how organizations can better connect Rovo to the work of planning, coordinating, and delivering.  

Why doesn’t Atlassian Rovo improve delivery on its own? 

Atlassian Rovo improves delivery only when it is built into the workflows where delivery decisions happen. Out of the box, Rovo offers AI search, chat, and general-purpose agents. Delivery gains need more: custom agents, connected DevOps signals, validated outputs, and routines that use them. 

Most rollouts stop at activation. Teams use Rovo Search to find a Confluence page or ask Rovo Chat to summarize a Jira epic. That saves time for individuals. Yet it does not tell a release manager whether Friday’s release is at risk. 

In other words, Rovo AI becomes a faster way to find information. Delivery intelligence still has to be designed, integrated, and adopted. Our guide to getting started with Atlassian Rovo agents covers the activation stage in more detail. 

What the research says about AI and software delivery performance 

This pattern extends well beyond Rovo. Google Cloud’s DORA program surveyed nearly 5,000 technology professionals for its 2025 State of AI-assisted Software Development report. Its central finding is that AI acts as an amplifier. It magnifies the strengths and weaknesses an organization already has. 

DORA also found that AI is now linked to higher delivery throughput. At the same time, AI continues to increase delivery instability. Teams have sped up, while the systems around them have not caught up. 

Atlassian’s 2025 State of Developer Experience research shows the same tension. Sixty-eight percent of developers save more than 10 hours a week with AI. Meanwhile, half of developers lose more than 10 hours a week to organizational inefficiencies. 

Developers also spend only about 16% of their time coding. Their biggest time drains are finding information, adapting to new technology, and switching between tools. 

This is the AI productivity paradox in delivery terms. Time saved in one step gets absorbed by friction in the next. Without deliberate design, extra AI output can bury the signal leaders need under more noise. 

The four gaps between Rovo activation and delivery impact 

Across Atlassian environments, the same four gaps keep Rovo from changing delivery outcomes. 

1. The design gap 

Agile coaches and delivery leads usually know which insights teams need. Examples include sprint health, carryover risk, blocked dependencies, and release readiness. However, that knowledge rarely becomes working Rovo agents. 

Rovo Studio makes agent creation more accessible. Still, production-grade Rovo Actions often require Forge development skills that many delivery teams lack. 

2. The integration gap 

Delivery signals live in many places, including Jira, Bitbucket, CI/CD pipelines, and testing platforms. When those signals stay disconnected, Rovo agents cannot reason about readiness or risk. 

Atlassian’s Teamwork Graph links work, people, and knowledge into shared context, as our Atlassian Team ’26 recap explains. Even so, delivery data from outside tools has to be connected and structured deliberately. 

3. The validation gap 

Teams act on AI insights only when they trust them. Trust is already a hurdle for AI in software teams. In DORA’s 2025 research, 30% of respondents reported little or no trust in AI-generated code. 

Delivery insights face the same test. If a sprint summary misstates carryover once, teams stop reading it. Validating agent outputs against real delivery data keeps that trust intact. 

4. The adoption gap 

Insights change outcomes only when they appear where decisions happen. Those moments include stand-ups, sprint reviews, release go/no-go calls, and portfolio check-ins. 

If agent outputs live in a separate chat window, usage fades within weeks. Adoption has to be designed into team routines and reinforced over time. Structured AI adoption and change coaching provides that continuity, so the gains last. 

What closes the gap: from AI search to delivery intelligence 

Delivery intelligence turns live work and DevOps data into trusted insights inside delivery workflows. On Atlassian, it combines Rovo agents, connected signals, validation, and adoption design. Organizations that close the gap tend to follow four moves. 

Start with delivery decisions 

Identify the decisions that slow delivery today. Common examples are sprint commitments, release readiness, and cross-team dependency calls. Then define the insight each decision needs and who acts on it. 

Connect the signals 

Integrate Jira, Bitbucket, CI/CD, and test data into the context Rovo agents use. As a result, agents gain the evidence they need to flag risk early in the sprint. 

Build and validate focused agents 

Build agents for high-value workflows first, such as automated sprint summaries or release notes drafted from merged pull requests. Test each output against real delivery data before teams rely on it. 

Embed, measure, and expand 

Place agent outputs inside existing ceremonies and dashboards. Baseline delivery KPIs first, then track change over several sprints. Once the first agents prove their value, expand to new workflows. 

The result is faster decision flow. Teams spend fewer hours assembling status and see earlier signal on the risks that matter. 

How do you measure whether Atlassian Rovo is improving delivery? 

Measure delivery outcomes, and treat usage data as a leading indicator only. Useful metrics include reporting effort per sprint, cycle time, sprint carryover, delay frequency, and time to answer status requests. 

DORA metrics add a stability lens. Change failure rate and deployment rework rate show whether faster delivery is also safe delivery. 

Set a baseline before the first pilot. Then compare results sprint by sprint, so leaders gain value visibility in delivery terms they already use. 

How Cprime helps 

Cprime helps engineering and delivery leaders make Atlassian Rovo operational through Rovo-Augmented Product Development. As Atlassian’s largest solution partner for more than 12 years, Cprime brings Atlassian, Agile delivery, and AI implementation expertise together. 

Every engagement starts with a Rovo delivery workflow assessment. It identifies where agents can generate actionable insights, where DevOps signals are disconnected, and which validation risks affect accuracy. 

From there, Cprime designs, builds, and validates Rovo agents inside sprint, release, and dependency workflows. The work runs as an ongoing program, so adoption holds as teams and priorities change. 

Clients typically see 70% less sprint reporting effort and 40 to 60% fewer delivery delays. Teams also recover more than five hours per sprint for delivery work. Explore our broader Atlassian Rovo services to see how this connects to enterprise-wide AI adoption. 

Turn Atlassian Rovo into Delivery Intelligence

Most teams activate Rovo and stop at search. Cprime’s Rovo-Augmented Product Development starts with a Rovo delivery workflow assessment, then designs, builds, and validates agents inside your sprint, release, and dependency workflows, so leaders see earlier risk signals and teams spend less time assembling status.

Frequently asked questions (FAQs) 

Does Atlassian Rovo improve software delivery performance? 

It can, when it is designed into delivery workflows. Out of the box, Rovo offers AI search, chat, and general agents. Delivery gains come from custom agents, connected DevOps signals, validated outputs, and adoption inside sprint and release routines. 

Why are most teams only using Rovo for search? 

Search works immediately, with no design effort required. Delivery use cases need defined insights, integrated data from Jira, Bitbucket, and CI/CD pipelines, and often Forge development skills. Without that work, Rovo stays a search tool. 

What is delivery intelligence in Atlassian? 

Delivery intelligence turns live work and DevOps data into trusted insights inside delivery workflows. Examples include automated sprint summaries, release notes from merged pull requests, dependency alerts, and real-time status visibility. 

Do we need Forge developers to build Rovo agents for delivery? 

Simple agents can be built in Rovo Studio without code. Production-grade Rovo Actions that read or update delivery data often require Forge development. Many teams partner with Atlassian specialists to fill that skills gap. 

How do you measure the ROI of Atlassian Rovo? 

Baseline delivery KPIs before a pilot, then track change sprint by sprint. Useful measures include reporting effort, cycle time, carryover, delay frequency, and DORA stability metrics. Usage counts alone do not prove delivery impact. 

Is Atlassian Rovo included with Jira Cloud? 

Rovo is available on Standard, Premium, and Enterprise Cloud plans of Jira, Confluence, and Atlassian collections. Usage is measured in Rovo credits, and allowances vary by plan. Check current packaging in Atlassian Administration. 

How long does it take to see delivery impact from Rovo? 

Most organizations start with a focused assessment and a pilot in one workflow. Working agents are typically delivered within weeks. Validation and expansion across additional workflows follow over the next few sprints. 

What Is Agentic SDLC? How Rovo Agents Are Reshaping the Software Delivery Lifecycle 

Agentic SDLC with Rovo agents coordinating work across the software delivery lifecycle

Most software teams already use AI. Developers accept code suggestions, and product managers draft user stories from a prompt. Yet delivery rarely gets faster in a way leadership can measure. 

The reason is simple. Coding was never the only bottleneck. Instead, delays pile up in the handoffs: refining requirements, chasing dependencies, reviewing code, writing release notes, and assembling status updates. 

Agentic SDLC targets exactly those gaps. Rather than helping one person type faster, it puts AI agents to work across the whole software delivery lifecycle. In the Atlassian ecosystem, those agents are Rovo agents. 

Below, we explain what agentic SDLC means, how Rovo agents reshape each stage of delivery, and what it takes to make them produce real results. 

What is agentic SDLC? 

Agentic SDLC is a software delivery model where AI agents plan, execute, and coordinate work across the lifecycle. Humans set direction, review outputs, and own the decisions. 

Traditional SDLC relies on people to move work between phases. AI-assisted development speeds up individual tasks inside those phases. Agentic SDLC goes further, because agents also carry work across the boundaries between phases. 

 DimensionAI-assisted development Agentic SDLC 
Scope One task, one user Multi-step workflows across teams 
Trigger A person writes a prompt A prompt, a workflow event, or an automation rule 
Context The open file or chat window Work items, docs, code, and pipeline signals 
Output A suggestion to accept or reject Actions: updated tickets, reviews, summaries, release notes 
Human role Operator Director and approver 

Why the software delivery lifecycle needs agents now 

Generative AI software development tools made coding faster. However, a faster coder doesn’t guarantee a faster release. Work still waits on refinement, reviews, approvals, and reporting. 

Meanwhile, the context teams need is scattered. Requirements sit in Confluence, work sits in Jira, and code sits in Bitbucket or GitHub. Pipeline signals live somewhere else again. As a result, people spend hours stitching that context together by hand. 

Agents change the economics of that stitching. Because they can read across systems and act on what they find, they absorb the coordination work that slows delivery. Engineers and product leaders then get time back for design, judgment, and problem-solving. 

Where Rovo agents fit in an agentic SDLC 

Atlassian Rovo is the AI layer built into the Atlassian Cloud platform. It powers search, chat, and agents across Jira, Confluence, and connected tools. Four parts matter most for agentic SDLC. 

  • Teamwork Graph. Rovo draws on Atlassian’s Teamwork Graph to connect context across Jira, Confluence, Bitbucket, Compass, and more. Agents therefore understand how work connects, not just what a single ticket says. 
  • Rovo agents. These task-specific assistants handle workflows like issue triage, backlog grooming, and documentation edits, and teams can trigger them via chat, automation rules, or the /ai command. 
  • Rovo Studio. Studio is a no-code/low-code workspace for defining agent behavior, knowledge sources, and actions, while developers can go deeper with Forge. 
  • Rovo Dev. Atlassian positions Rovo Dev as a context-aware agent that handles planning, coding, and reviews, available in the terminal, the IDE, and beyond. 

Together, these pieces give teams the raw material for an agentic SDLC. Still, raw material isn’t a working system, as the later sections explain. 

How Rovo agents reshape each stage of delivery 

1. Planning and requirements 

Backlog refinement is often where velocity stalls first. Rovo agents can turn a rough idea or Confluence brief into structured Jira work items. They can also suggest acceptance criteria, subtasks, and likely dependencies. 

Product managers still decide what matters. However, they start from a solid draft instead of a blank ticket. Refinement sessions then focus on trade-offs rather than typing. 

2. Design and code planning 

Before writing code, developers often ramp up across five or six tools. Rovo Dev shortens that ramp with code plans that pull knowledge from across the Atlassian platform. 

Consequently, new team members onboard faster. Experienced engineers, meanwhile, spend less time hunting for context. 

3. Build 

During implementation, Rovo Dev can generate code aligned to the approved plan, including refactoring, new tests, and docs. It works in the terminal and IDE, so developers stay in their normal flow. 

The real difference from generic coding assistants is context. Because Rovo Dev draws on the Teamwork Graph, it knows why a change exists, not just what the file contains. 

4. Code review and quality 

Review queues are a classic bottleneck. Rovo Dev can analyze code, suggest improvements, and validate changes against acceptance criteria in Jira. 

This shifts quality left. Reviewers focus on architecture and risk, while the agent handles consistency checks and obvious gaps. 

5. Release and documentation 

Release notes rarely get anyone’s full attention, yet they can hold up deployments. Custom Rovo agents can draft notes from merged pull requests and completed work items. Similarly, they can assemble readiness summaries for change approvals. 

Teams still sign off on every release. Nevertheless, the documentation is ready when the code is. 

6. Delivery intelligence and status reporting 

The final stage closes the loop. Custom agents can generate sprint summaries from live delivery data and flag cross-team dependencies. They can also surface risk before a commitment slips. 

Leaders get current answers without calling another status meeting. Over time, each sprint becomes a feedback loop that improves predictability. This is where agentic SDLC meets value stream management and software delivery management. 

What an agentic SDLC requires to work 

Organizations are rapidly enabling Rovo after moving to Atlassian Cloud, and leadership expects it to improve delivery visibility. Yet most teams use it mainly for search. On its own, that won’t change delivery performance. Four gaps usually stand in the way. 

Insight design: Agents need a clearly defined job. Someone has to decide which sprint, release, and dependency insights actually help teams decide faster. 

Integration: Delivery signals live in Jira, Bitbucket, CI/CD pipelines, and testing tools. If those signals never reach Rovo, agents can’t produce meaningful insights. 

Engineering capability: Rovo Actions require Forge development expertise many teams do not have. Without it, agents stay limited to reading rather than acting. 

Validation and trust: AI outputs must be checked against real delivery data. Otherwise, teams quietly stop trusting the agent, and then stop using it. 

Governance runs across all four. Clear approval points, audit trails, and access policies keep agents accountable. Helpfully, Rovo only accesses data a user is already permitted to see. 

Humans stay in charge 

Agentic doesn’t mean unsupervised. The strongest implementations keep people accountable for priorities, architecture, and release decisions. Agents take on repetitive, context-heavy work, so humans can apply judgment where it counts. 

That balance also drives adoption. When engineers see agents removing toil rather than second-guessing them, usage grows on its own. 

From Rovo features to delivery outcomes 

None of these capabilities are out of reach. Rovo agents, Rovo Studio, and Rovo Dev are available on the Atlassian platform today. Still, they only reshape delivery when someone designs, connects, and validates them inside real workflows. 

That’s why so many teams stall after the pilot. Production-grade agents require Atlassian, Agile, DevOps, and AI skills that rarely sit in one team. 

Introducing Rovo-Augmented Product Development 

Rovo-Augmented Product Development is Cprime’s approach to turning Rovo into a working delivery intelligence layer. We design, build, and validate Rovo agents inside sprint, release, and DevOps workflows. 

Every engagement begins with a Rovo delivery workflow assessment. It identifies workflows where agents can generate actionable insights, gaps in DevOps signal integration, data and validation risks, and initial agents that can show measurable impact. 

The outcomes are concrete: 

  • Sprint intelligence: 70% less reporting effort, with more than five hours freed per team per sprint. 
  • Release documentation: Release notes produced from merged pull requests and completed work, accelerating documentation cycles by 90%. 
  • Dependency detection: Clients typically see 40 to 60 percent fewer delivery delays. 
  • Real-time status: Status response accelerates by up to 95 percent, and meetings shorten. 

As an Atlassian Platinum Solution Partner, Cprime brings the Forge, DevOps, and adoption expertise that turns Rovo from a search tool into a delivery advantage. 

Put Rovo Agents to Work Across Your Delivery Lifecycle

Most teams enable Rovo and stop at search. Cprime’s Rovo-Augmented Product Development starts with a delivery workflow assessment, then designs, builds, and validates Rovo agents inside your sprint, release, and DevOps workflows, so they deliver measurable gains in reporting, documentation, and delivery predictability.

Frequently asked questions (FAQs) 

What is agentic SDLC? 

Agentic SDLC is a delivery model where AI agents plan, execute, and coordinate work across the software lifecycle. Humans set direction and approve outcomes. 

How is agentic SDLC different from AI-assisted development? 

AI-assisted development speeds up single tasks for one person. Agentic SDLC uses agents to run multi-step workflows across tools, teams, and lifecycle phases. 

What are Rovo agents? 

Rovo agents are AI agents built into Atlassian Cloud. They use Teamwork Graph context to act inside Jira, Confluence, and connected tools. 

What is the difference between Rovo agents and Rovo Dev? 

Rovo agents handle focused jobs across teams, such as triage or summaries. Rovo Dev is Atlassian’s agent for engineers, covering code planning, generation, and review. 

Do AI agents replace developers? 

No. Agents absorb repetitive, context-heavy work. Developers keep ownership of architecture, design decisions, and final approvals. 

Do we need Forge to build Rovo agents? 

Not always. Rovo Studio supports low-code agents. However, custom Rovo Actions that act on other systems typically require Forge development. 

How do we start with agentic SDLC on Atlassian? 

Begin with a delivery workflow assessment. Then pilot one or two high-value agents, validate them against real data, and expand from there. 

Atlassian Rovo FAQ

Feature_Atlassian

PLEASE NOTE: Atlassian Rovo is evolving rapidly as Atlassian expands AI capabilities across Jira, Confluence, and connected enterprise tools. Features, integrations, availability, and workflows may vary based on your Atlassian products, subscription tier, admin configuration, and current Atlassian releases. 

Getting started with Atlassian Rovo 

What is Atlassian Rovo? 

Atlassian Rovo is Atlassian’s AI solution for enterprise search, chat, agents, and workflow assistance. It helps teams find knowledge across Atlassian and connected third-party tools, ask questions in natural language, summarize information, and use AI agents to support work inside tools like Jira and Confluence. 

How do I access Atlassian Rovo in my Atlassian Cloud instance? 

Users can access Atlassian Rovo through supported Atlassian Cloud products when Rovo is available and activated for their site. Once enabled, users can open Rovo Chat via the chat icon in the bottom-right corner, search from the top navigation bar, or utilize Rovo Studio. Access depends on your organization’s Atlassian plan, admin settings, product availability, and permissions. 

Is Atlassian Rovo included in my Jira or Confluence subscription plan? 

Yes. Rovo in all its forms is automatically included in every paid Cloud plan, including Jira, Confluence, and Jira Service Management. The range of features depends on your Atlassian Cloud plan, product configuration, and Atlassian’s current packaging. Organizations should verify eligibility through Atlassian Administration or current Atlassian documentation. 

What is the difference between Rovo AI Search, Rovo Chat, and Rovo Agents? 

Rovo AI Search helps users find information across Atlassian and connected third-party tools. Rovo Chat lets users ask natural-language questions, summarize information, and get contextual assistance. Rovo Agents are configurable AI teammates designed to help users complete specific tasks, support workflows, and take action based on defined instructions and knowledge sources. 

What is the difference between Atlassian Intelligence and Atlassian Rovo? 

Atlassian Intelligence and Atlassian Rovo are closely related, but they are not the same thing. Atlassian Intelligence is the underlying AI capability embedded within Jira, Confluence, and other Atlassian products, while Rovo is Atlassian’s broader AI solution for enterprise search, chat, agents, and cross-platform workflow assistance across both Atlassian and connected third-party tools. 

Rovo AI Search and knowledge discovery 

How does Rovo AI Search work? 

Rovo AI Search uses natural-language search to help users find information across Atlassian products and connected third-party apps. It draws from indexed sources, permissions, relevance signals, and work context to surface results that are more useful than keyword matching alone. 

How is Atlassian Rovo different from Jira or Confluence search? 

Jira and Confluence search are primarily focused on content within those individual products, and will generally locate exact text matches with limited search operators. Atlassian Rovo uses natural language and semantic understanding to provide a broader AI-powered search experience that can connect knowledge across Jira, Confluence, and approved third-party tools, helping users find information across a larger work context. 

Why can’t I find all Jira issues or Confluence pages in Rovo AI Search? 

Rovo AI Search only surfaces information the user is allowed to access and that has been indexed or connected properly. Missing results may be caused by permissions, connector configuration, indexing delays, product availability, deleted content, or content that is outside the connected knowledge sources. 

How does Atlassian Rovo decide what content appears in search results? 

Atlassian Rovo uses factors such as search intent, content relevance, user permissions, available connectors, and indexed knowledge sources to determine which results appear. It leverages the Teamwork Graph—Atlassian’s proprietary data layer—to surface the most relevant information based on context. Users should only see content they are authorized to access under existing Atlassian and connected-app permissions. 

How often does Atlassian Rovo refresh or index content? 

Atlassian Rovo continuously indexes content across Atlassian tools like Jira and Confluence. For connected third-party platforms such as Google Drive, SharePoint, and Slack, Rovo uses admin-configured connectors to regularly sync and update searchable content. 

Can Atlassian Rovo connect to Slack, Google Drive, SharePoint, or other external tools? 

Yes. Atlassian Rovo can connect to approved third-party tools through Rovo connectors and the Atlassian Teamwork Graph. Supported connections include tools such as Google Drive, SharePoint, Slack, GitHub, Microsoft Teams, and other enterprise apps. If you find that a connector is available from Atlassian, but not in your instance, check with your Atlassian Cloud admin. 

Rovo security, permissions, and governance 

Does Atlassian Rovo respect Jira and Confluence permissions? 

Yes. Atlassian Rovo is designed to respect existing permissions in Jira, Confluence, and connected tools. Users should only see content they already have permission to access, which makes permissions hygiene an important part of any Rovo rollout. 

Is company data used to train Atlassian Rovo or Atlassian Intelligence models? 

Atlassian states that customer data sent to AI models through Rovo is used to generate a response, not to train third-party AI models. Organizations should still review Atlassian’s current data handling, privacy, and residency documentation to confirm how their data is processed in their specific environment. 

What security and compliance considerations should organizations understand before using Atlassian Rovo? 

Organizations should review permissions, connected data sources, admin controls, AI usage policies, data residency requirements, and compliance obligations before deploying Rovo broadly. Rovo respects existing permissions, and customer data is never used to train LLMs. It’s important to note that the Atlassian Cloud Platform complies with SOC 2 and ISO 27001, but is not HIPAA compliant at this time. 

How can enterprises govern AI usage in Atlassian Rovo? 

Enterprises can govern Atlassian Rovo through admin controls, permissions management, and AI governance settings within Atlassian Administration and Rovo Studio. Organizations can control access to AI features, manage who can create Rovo Agents, and align Rovo usage with existing security and compliance policies. 

Rovo Chat, AI responses, and reliability 

What is Rovo Chat and how does it work? 

Rovo Chat is an AI assistant built into Atlassian tools that functions like other popular GenAI chatbots like ChatGPT and Claude, so the learning curve should be short. Rovo Chat uses available work context from Atlassian and connected third-party apps. Users can ask questions, summarize information, draft content, find relevant work, and get help based on content they are permitted to access. 

How accurate are Atlassian Rovo responses? 

Rovo responses depend on the quality, freshness, and completeness of the information it can access. While useful for fast discovery and drafting, Rovo struggles with complex counting tasks and deterministic, multi-step workflows. Like other AI systems, Rovo should be used with human review, especially for business-critical, compliance-sensitive, or customer-facing decisions. 

Why does Atlassian Rovo sometimes generate incomplete or outdated information? 

Rovo may generate incomplete or outdated answers when source content is incomplete, stale, poorly structured, not yet indexed, or unavailable because of permissions or connector limitations. Better knowledge hygiene, current documentation, and well-managed permissions can improve answer quality. And, Atlassian Rovo is subject to the same occasional issues other natural language AI engines face, including hallucinations. 

Can Atlassian Rovo execute actions in Jira or only provide answers? 

Rovo can support actions and workflow assistance in Jira through supported agents, automations, and configured workflows. Depending on your organization’s security and governance requirements, Rovo Agents can either operate autonomously or require human approval before executing sensitive or irreversible actions. 

How does Jira Intelligence work with Atlassian Rovo? 

Rovo extends AI-powered capabilities inside Jira (Jira Intelligence) by going beyond immediate issue-level tasks to help users search across systems, summarize information, automate routine tasks, and connect work across Jira, Confluence, and other integrated tools. 

How does Confluence Intelligence work with Atlassian Rovo? 

Atlassian Rovo powers many of the AI capabilities within Confluence, including intelligent search, content generation, and workflow assistance. By connecting knowledge across Confluence, Jira, and integrated third-party tools, Rovo helps teams surface relevant information and act on it more efficiently. 

Rovo Agents and automation 

What are Atlassian Rovo Agents? 

Rovo Agents are configurable AI teammates that help teams reduce repetitive work, automate tasks, and move work forward more efficiently. They can assist with activities like summarizing information, creating or updating Jira issues and Confluence pages, supporting workflows, and surfacing insights across Atlassian and connected third-party tools. 

How do I create a Rovo Agent? 

Users with the right permissions can create a Rovo Agent by opening Atlassian Studio from the app switcher, selecting Agents, and choosing Create Agent. From there, define the agent’s purpose, configure its instructions and knowledge sources, and add skills to support specific workflows and tasks. 

What are the best real-world use cases for Rovo Agents? 

Common Rovo Agent use cases include summarizing Jira issues, generating Confluence updates, assisting with support triage, preparing release notes, analyzing customer feedback, creating test cases, answering internal knowledge questions, and helping teams reduce repetitive coordination work. 

Can Rovo Agents take actions in Jira or only provide recommendations? 

Rovo Agents can support actions in Jira when configured through supported workflows, skills, plugins, or Atlassian Automation. These can include organizing backlogs, creating epics, updating trackers, and logging work, for example. The specific actions available depend on agent configuration, permissions, product capabilities, and admin settings. 

How does Rovo Automation work in Jira Service Management and Jira Software? 

Rovo Automation connects AI capabilities to Jira Software and Jira Service Management workflows, helping teams reduce repetitive work and automate common tasks. Organizations can use Rovo actions and AI agents to summarize issues, support ticket workflows, generate updates, assist with software delivery, and build automation rules using natural-language prompts. 

What are the current limitations of Atlassian Rovo and Rovo Agents? 

Atlassian Rovo and Rovo Agents are designed to improve search, automation, and workflow efficiency across the Atlassian ecosystem, but they still require human oversight and well-structured data. Organizations may encounter limitations around complex cross-platform automations, large-scale data processing, advanced customization, and governance as AI usage expands across teams. 

Atlassian Rovo adoption and enterprise use cases 

What are the best Atlassian Rovo use cases for software development teams? 

Software development teams can use Atlassian Rovo to accelerate planning, reduce repetitive engineering work, lessen costly context switching, and surface knowledge across tools like Jira, Confluence, Bitbucket, and VS Code. Common use cases include implementation planning, code generation assistance, automated pull request reviews, release note creation, backlog organization, and contextual search across connected systems. 

How are organizations using Atlassian Rovo for IT support or incident management? 

Organizations can use Atlassian Rovo to summarize incidents, support ticket triage, surface relevant knowledge articles, assist service agents, automate repetitive updates, and help teams connect support activity with related Jira, Confluence, and third-party information. 

How can organizations improve adoption of Atlassian Rovo across teams? 

Organizations can improve Atlassian Rovo adoption by integrating AI into existing workflows, establishing clear governance, and focusing on practical, high-value use cases. Successful rollouts typically combine executive support, hands-on Rovo onboarding training, clean and well-structured data, internal AI champions, and ongoing feedback to help teams use Rovo effectively in their daily work. 

What does a successful Atlassian Rovo rollout look like? 

A successful Atlassian Rovo rollout typically starts with targeted, high-value use cases before expanding across teams and workflows. The most effective deployments combine executive sponsorship, practical training, clear governance, measurable adoption goals, and ongoing feedback to help teams integrate Rovo naturally into their daily work. Working with an experienced Atlassian Partner can make for a quick and successful Rovo rollout.