Atlassian Collections - App collections for teams

Following recent changes to its terminology (e.g., the term "projects" in Jira has been replaced by "apps"), Atlassian has introduced Collections (app collections).

The basic idea behind the Collections is to create a place where plans, code, service and strategy can be brought together. Atlassian's app collections have been designed as specific, results-oriented packages that unify daily work and add AI where it actually helps.

Collections are sets of apps and AI agents put together by Atlassian that are tailored to the way teams actually work (Teamwork Graph). Instead of combining apps themselves, a bundle is launched that already shares data, permissions and context. For example, a Loom recording can become a summarized Confluence page, which is then linked to the work in Jira without having to jump from app to app.

The aim is to create a networked platform that covers all aspects of the requirements.

The first effects can be seen in the fact that Jira Service Management (JSM) can no longer be licensed separately, but only as part of the "Service Collection".

Here is a brief overview of the collections:

Atlassians Teamwork Collection is intended to be the solution for all teams and projects. It combines planning, knowledge, asynchronous videos and AI in one workspace so that everyone involved has the same overview and the workflow never comes to a standstill.

This collection includes:

• Jira
• Confluence
• Loom

Goals:

• Accelerate the time to market of products (not just updates)
• Increase agility
• Maximization of ROI

As the name suggests, the Strategy Collection is designed for planning and strategy. By integrating with other Atlassian Cloud Apps, planning and work can be brought together.

This collection includes:

• Focus (an app for corporate strategies)
• Talent (an app for planning knowledge workers)
• Align (an app for work planning in companies)
• Rovo (the artificial intelligence from Atlassian)

Goals:

By implementing this bundle solution, executives gain real-time insights into:

• Goals
• Dependencies
• Capacities

This should enable a faster transition from the results to the resulting actions. Atlassian recommends combining this collection with Jira Cloud Premium to achieve the best possible results.

The Atlassian Service Collection contains a series of AI-supported, service-oriented applications for employees and customers, which are intended to promote communication between service employees and customers. In addition, the omnichannel communication that is sorely missed by many is likely to be added.

This collection includes:

• Jira Service Management (JSM)
• Customer Service Management (CSM)
• A flexible Configuration Management Database (CMDB)
• Rovo agents

Goals:

• Faster resolution of customer problems
• Smooth communication
• Improved management of requests (regardless of type)
• More flexibility through the use of a CMDB

The Atlassian Software Collection maps a Software Development Life Cycle (SDLC) that runs on an AI platform.

This collection includes:

• Rovo Dev (AI agents for developers)
• DX (measuring the productivity and impact of AI)
• Pipelines (scalable CI/CD automations)
• Bitbucket (collaborative source code management)
• Compass (software catalog for teams).

Goals:

• More transparency in terms of:
  • Code
  • Üipelines
  • Developer experience
• Better measurability
• Avoidance of friction losses within the SDLC

To summarize...

...the collections should reflect the daily work with a measurable return on investment. In addition, there should be fewer routine tasks, a better work flow and ultimately better results.

It remains to be seen to what extent this approach and the merging into collections is relevant for small and medium-sized customers - especially when the price component is taken into account.