Browse Inside Atlassian
Filters
Inside Atlassian: how we do marketing project management with Jira Core and Confluence
Marketing can be a cyclical process. We marketers typically plan projects, assign work, review content, publish, and then…. start all over again. At the beginning of each quarter, we approach this process with bright-eyed enthusiasm, big ideas, and a clear plan of attack. But as the months wear on, and more (or unexpected) work accumulates, it can […]
Inside Atlassian: the secret to legendary service
Back in 2001, our co-CEOs Mike and Scott started a global business from Australia with $10,000 on a credit card. They knew that nothing less than legendary service would be needed to be successful. Service, both external and internal, is part of Atlassian’s DNA. Check out our ebook to get practical tips from Mike on Atlassian’s service culture, a topic that is close to his heart.
Inside Atlassian: tracking blog categories and performance with Jira custom fields
I can hold my own with math and numbers, but I don’t love them. I have to admit though, I’m starting to love data. Like many marketers, I spend a lot of time thinking about blogs. And blogging itself is becoming increasingly data-informed (if not fully data-driven, but that’s another story). How awesome is it that […]
Inside Atlassian: Jira workflows for tracking blog projects
Chances are, your marketing team manages blog projects on spreadsheets. You probably track who is working on it, what state it’s in, when it’s going to be published, what it’s about, how it fits into larger marketing campaigns… And that’s just the stuff you’re concerned with before it’s published. It’ll come as no surprise that Atlassian’s marketing team uses Jira Core, Confluence, and Hipchat to keep our blogs running smoothly. So today I’m going to get all meta with a blog about how we use Jira Core, including some example workflows, to track our blogs.
Inside Atlassian: how our site reliability engineers do incident management
“Ohhhhh $#!τ. We broke Confluence.” In one of our first Confluence Cloud releases in 2016, we broke our users’ ability to edit pages. As the head of Atlassian’s site reliability engineering group, this kind of thing falls right into my wheelhouse. In this post, I’ll walk you through how we responded to the situation to get Confluence working again. I’ll give an insider’s view of our incident management process, as well as how we’ve configured Atlassian tools to support this work.
Inside Atlassian: how IT & SRE use ChatOps to run incident management
Any team that slings code for a living deals with service issues. They know all too well the hated red alert… the dreaded text in the middle of the night… the loathsome ping from a coworker telling them that $#!π just hit the fan. But what separates good services from great services is the ability to recover swiftly with minimal affect on users. And a big factor in swift recovery is ChatOps.
Separating the signal from the noise: how Atlassian does proactive support
I’m part of a team called Service Enablement, which is a special project group within the broader support team at Atlassian. We work closely with the support, engineering, product, and design teams to ensure that we provide a feedback loop between customers and the product. Most importantly, we try to prevent major incidents from happening before they happen – because we care about you as customers, and we want you to be customers for life.
What agile retrospectives won’t improve, and what you can do about it
Retrospectives are one of those essential rituals of agile practice. They’re fast, they’re easy, and a great way for a team to focus on how to improve what they’re doing. But the thing with retrospectives is that they sometimes become all about the practice of your team, rather than the intent of your team. They become all about the team’s shoulda woulda coulda, rather than the team’s purpose…
PMs weigh in: prioritizing customer feedback and backlog grooming
Gathering customer feedback, turning feedback into actionable inputs, and then prioritizing those inputs for your development team are some of the most important functions of a PM. They’re also the most challenging. Every PM has their way of balancing and prioritizing their products backlog, but we want to give you some additional tips and techniques […]
Cambodia trek 2015: Atlassian and Room to Read
On November 18th, twelve Atlassians from across the globe met in Phnom Penh to participate in our annual trek with Room to Read, an organization dedicated to breaking the poverty cycle through the power of education. Their focus is on improving literacy and gender equality in education throughout Asia and Africa.
Inside Atlassian: a product manager and a dev manager walk into a planning meeting…
Product planning meetings are one of the most important meetings in a product’s lifecycle so we decided to take you inside a product planning meeting at Atlassian by filming the latest Portfolio for Jira planning meeting (filming the planning meeting of a planning tool seemed only fitting). These product planning meetings tend to happen quarterly and last about four hours (don’t worry – we time-lapsed it for you of course!).
Examples of capturing customer feedback for agile development
Customer feedback in agile development is a three-step process of gathering, documenting, and prioritizing. Here are examples from our product managers.
Inside Atlassian: designing software with the customer at heart
I decided to sit down with different Jira designers to learn how they reimagined Jira as Jira Software, Jira Core, and Jira Service desk from a design perspective. The stories were endless, but three things kept popping up in each designer’s story: design spikes, live data prototyping, and a stellar feedback collector.
Inside Atlassian: building a culture of innovation
Fostering a culture of innovation isn’t about providing ping-pong and free beer. It’s about your values and how you live them. Here’s a look at how we build a culture of innovation and how your company can, too.
Keeping projects on track: four lessons for development managers
Imagine you had a product with millions of users, over five million lines of code, and more than 100 developers working on it. And then your company decided that this product had the opportunity to become an even more successful platform. Check out how two of our development managers co-coordinated Jira’s move from product to platform.