Well hasn’t the last year flown! I cannot believe we are already talking about the Atlassian team event again so soon. While we are still a fair few weeks away, it will fly by. So what do we need to discuss?

TEAM ‘23, THE FLAGSHIP EVENT FOR ATLASSIAN IS SET TO BE A BANGER!

I mean, come on. We all know what is happening next week. But just in case you didn’t, Team ‘23, the flagship Atlassian event is in Vegas where we will get a chance to hear all the biggest announcements with all of our fellow Atlassian enthusiasts. There are four tracks you can choose from, depending on your needs to help fit the agenda and event around you.

Since it’s inception, Atlassian has always surrounded itself with agile ways of thinking. But like all, times have moved on, but the mindset of challenge the way we do hasn’t. DevOps pushes this mindset. It brings forward two major areas that have often struggled to see eye to eye in a way that is only beneficial for all members of staff and the business. In this article we learn what Atlassian did in 2022 and are doing in 2023 to improve their tools to facilitate DevOps.

TEAM ‘23, THE FLAGSHIP EVENT FOR ATLASSIAN IS SET TO BE A BANGER!

This year, we return to Vegas, for what is predicted, to be with 4000 of our fellow Atlassian users. There are four tracks you can choose from, depending on your needs to help fit the agenda and event around you.

So that’s a wrap for here in Berlin. Atlassian Unleash was a blast for so many reasons, including having a chance to present with Appfire on reducing tech debt, so lets break it down and see what we learnt. Atlassian wanted the Unleash event to deep dive into the agile & DevOps experiences within the ecosystem. We saw the keynote focus on some of Atlassian’s newest adventures in the form of Jira Product Discovery & Compass.

Talented teams can create amazing software with great organisation of the product strategy and end user experiences. Jira Software has helped these teams by bringing them further structure to their work. However, developers spend their lives coding, and are often in Jira the least, which can create disconnect between the tickets and their code. This can cause headaches for product owners (POs) or project managers (PMs) overseeing the vision and releases. So how do we keep developers coding, but keep transparency for the PMs and POs to build strategy and understand current standings?