Major incidents are inevitable, and fixing them is the top priority for any ops or DevOps team. But what happens after service is restored? Do teams take the time to fully understand what went wrong, then follow up to prevent it happening again?
In the ‘90s, we used to think of blogs as online diaries, filled with oversharing and bad graphic animations. But since then, they’ve grown into a full-blown industry. Influencers are now able to make whole careers out of successful blogs and it’s difficult to find a company that’s not using a blog as part of its marketing strategy.
Many teams choose Atlassian Server products because they want or need control over their data and infrastructure. But did you know that Atlassian offers another option for you to deploy on your own infrastructure? This alternative is called Atlassian Data Center, our self-managed enterprise offering, which provides the same functionality you know and love in our Server products, but has additional capabilities to better serve enterprise organizations.
I’ve been on a lot of teams in my journey from a software engineer to head of product for Confluence Cloud. All of the best ones have had one thing in common: they were comprised of people from different walks of life who could view the world from different perspectives. So naturally when I started hiring my own teams, I knew promoting diversity at the workplace would be a priority for me.
Product roadmaps are one of the most powerful documents a team can build. A good roadmap makes sure that everyone working on a product – from senior executives, to product leaders, to design, to development – understands the status of work and are aligned on upcoming priorities.
When you take a step back and think about society’s big technological breakthroughs — the printing press, the television, the Internet — they were revolutionary because they completely disrupted the way that the world shares knowledge. If you haven’t heard of it, knowledge sharing is pretty much exactly what it sounds like: it’s the exchange of information between different people, teams, organizations, or communities.
The job of the IT professional has become more difficult over the past decade. This is not necessarily due to the workload, but because of the dramatic shift we’ve seen in the way our organizations, employees, and customers are now operating in a software-powered world.
Cloud is a big part of Atlassian’s future, and we’re more focused than ever on delivering a great Server to Cloud migration experience. When developing software, there is no better way to test than doing it yourself. So that’s what we did. In an effort to learn more, understand pain points, and make a better experience for our customers, we migrated our whole company’s Jira and Confluence instances to the Atlassian Cloud.
At Atlassian, we’re big believers in open work. We’ve seen how our teams and our customers’ teams achieve more when collaboration and communication are at the foundation of everything they do. We know that having the right set of integrated tools is critical to moving work forward.
Jira Software, historically, has been known as a desktop tool for software teams to plan, track, and release great products. Our team has been hard at work since we released our first version of Jira Cloud for iPhone to release features and functionality that make working across all mobile operating systems and desktop as seamless as possible for our users, allowing work to move forward from anywhere.
