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 be tough to keep the process together. That said, having the correct tools in place can alleviate the manual labor of staying organized and can sustain

Continue reading »

In a DevOps world, work is often merged to master multiple times a day, but it’s not always easy to know when changes ship. Developers have full control over deploying their changes to customers which makes it extra important that those changes are tracked. The good news is that teams can automate much of this process using JIRA Software or JIRA Service Desk. Here are six actionable steps for better release management in the JIRA platform.

Continue reading »

Agile software development supports a release plan, but it's challenging to coordinate that on a multi-team level when you've got a lot of dependencies between teams. Rosetta Stone, a language learning technology company, found a solution to this challenge by bringing their entire development organization together about once per quarter to map out 10 to 12 weeks of work. And last week, I was lucky enough to watch how they do this at their 5th program increment planning (dubbed "PI5"). Here's how it worked.

Continue reading »

Our twitter chat has now ended! For a recap, check out the questions and answers on the #AskJIRABB hashtag, and stay tuned for more events to come. Are you a JIRA Software or Bitbucket user? How about an Agile fan or Git enthusiast? We're looking at you. To honor one of Atlassian's core values, Don't *%# the customer, we want you to use us as a resource. Today, Atlassian's Product managers and developer advocates will unite to give your team the leg up on any JIRA Software/Bitbucket, Git or agile

Continue reading »

Using both JIRA Software and Portfolio for JIRA, teams can see whether the day-to-day work they're doing maps directly to the company's overall strategy. But people often ask me "well, what happens in Portfolio for JIRA and what happens in JIRA Software?". So I decided to throw together a quick diagram to show you how they fit together.

Continue reading »

We built JIRA Core because we realized business and back-office teams could benefit from JIRA in the same ways software teams do. JIRA Core extends the workflow functionality and customizability of JIRA to business teams so they can track work, manage projects, and stay on top of everything. JIRA Core lets business teams define their processes, break down and track issues, and organize work. Issues in JIRA Core can represent all kinds of things: a task, a document... even a person. Just about anything you want to track can be an issue. Read on to see more of the many examples!

Continue reading »