4 Atlassian Tips to Bring your Service and Development Teams Together

9 February 2018 | Atlassian

Think of it this way. Support teams are receiving incoming ticket requests, they troubleshoot and strive for resolution on the majority of cases, however sometimes it’s outside of their control and there is a need to bring in the development troops to resolve an issue – ahem, software bug.

JIRA Service Desk is software that helps to define those workflow processes while keeping the communication open to all parties involved, including your customer! But this piece of software is not the only solution in the equation of increasing team collaboration across these departments.

Best practices are the missing puzzle piece to help you use your collaboration tools to their fullest potential. The following tips are Atlassian’s recommendations on best practices for bringing support and dev teams together.

1. Understand the feedback loop between your service and dev teams


The first step to bringing your service and dev teams closer together is understanding how their feedback loop provides value for your business. We can better understand this relationship by breaking down this loop into its two constituent parts: 1) your support team’s collection of product feedback from customers and 2) your dev team’s incorporation of this feedback into the product roadmap. Customers are then free to give feedback on these new feature releases, thus completing the virtuous cycle.

Management consultant Peter Drucker is quoted as saying, “you can’t manage what you can’t measure.” Though he never actually said this, the idea rings true. The feedback loop between service and dev teams is no different. Understanding the business value this loop provides requires you to understand how to measure it. Once you are able to quantify metrics that describe your feedback loop, you can then track how implementing best practices help you realize greater value. While the specific metrics you use to quantify this feedback loop may vary, some general metrics used at Atlassian are listed below.

For your support team:

  • Number of people submitting support tickets
  • Number of product feature requests
  • Number of reported bugs
  • Number of severity 1,2,3, etc. incidents
  • Customer satisfaction

For your development team:

  • Number of bugs fixed
  • Number of feature requests implemented
  • Hours spent on bug fixes
  • Hours spent on feature requests
  • Net promoter score

At Atlassian, they use a host of out-of-the-box and custom reports in Jira Software and Jira Service Desk to track how their feedback loop is performing. These reports allow their dev and support teams to track metrics on a weekly basis and set quarterly goals so they can identify and resolve issues faster.

2. Turn your employees into customers by dogfooding your product (or service)

As defined by Atlassian: Dogfooding is all about using the product that your company makes in order to understand the user experience and catch any pesky bugs before going into production.

For PMM Madison, she highlights how every morning when checking into the start of her workday, she uses 3-4 of the Atlassian products. She starts by logging into JIRA Software to review the tasks assigned for the day, checks Stride for any notifications, and browses Confluence to find any popular posts – all to put a finger on the Atlassian pulse.

She points out that regardless of where you work, dogfooding is a great tactic for bringing your service and dev teams together because it turns all of your employees into customers. Benefits extend far beyond helping your coworkers feel greater empathy for your customers. Your employees can act as the first line of defense against bugs and can provide product feedback on new features before they’re pushed to external customers.

When Atlassian announced their new chat tool, Stride, back in September 2017, according to Madison, it was an example of how Atlassian employees ‘dogfooded’ the product. By incorporating their employee feedback collection into the product, she advised they were able to submit thousands of pieces of feedback with ease, covering topics from bugs, usability, features, and aesthetics.

Furthermore, Madison explains that dogfooding isn’t just about feedback collection for product launches and feature releases. It’s also a crucial part of instituting a continuous feedback loop between your coworkers and your developers for everyday product use. She discloses that Atlassian employees are heavy users of Jira Software and Confluence with over 5,000 spaces in Confluence and over 900 boards in Jira Software. This transparency and usage allows for a large collection of feedback from their employees, but also creates another feedback loop between internal IT team and development teams. It also allows for knowledge sharing between your internal IT teams and your external support team to help identify common issues and fix problems faster.

Here at e-Core, we compare this advice to our consulting teams. By working with Atlassian solutions on a daily basis for over 10 years using workflows, automation, and templates, we’ve collaboratively challenged effectiveness and sought out best practice in our internal processes. In turn, we are able to share our experience with other teams outside of our organization to help them determine their workflows and processes offering guidance and alleviating the pain of trying to reinvent the wheel.

All-in-all, we back Madison and suggest you listen to her advice here to include your employees and coworkers in product feedback, support, and development process by dogfooding! After all, they have the biggest incentive to improve the product or service.

3. Make it easy for your users to ask for help


After you’ve taken the time to understand your feedback loop and started dogfooding your product, it’s time to focus on improving the first part of your feedback loop, making it easier for your users to ask for help. The strength of your feedback loop is directly related to the amount of feedback you collect from your users. Lowering barriers for customers to provide feedback will increase the volume of feedback you collect. That information will arm support and dev teams to make the right decisions about how best to serve customers.

At Atlassian, they use Jira Service Desk’s customer portal to give their customers and employees an easy-to-use way to ask for help. While their customers and employees can use email to submit tickets to their support teams, the overwhelming majority of support requests come through their portal because it’s so easy to use. In fact, their customer portal has proven so successful that all of their internal teams, from IT to Marketing to Legal, use it to field requests from anyone who needs help. At last count, they had about 100 internal service desks!

At e-Core, we use Jira Service Desk to track internal requests across departments. For instance, let’s say our HR department wants to communicate a job opening, they’ll submit an internal ticket request for supporting graphics and social media posting from our Marketing team through our Marketing Service Desk portal. Our team is easily assigned the work ticket and HR is aware of its status through completion.

In addition to providing a dedicated service portal for their customers and employees to visit, they’ve also recently launched their embeddable portal to allow help forms to be placed anywhere that’s convenient for your customers to get to them. With the embeddable portal it’s easy to put help forms anywhere on your website or in your web application so your customers can ask for help in the context of encountering the issue.

The benefits of using the customer portal extend beyond just making it easier for customers to ask for help. The portal also reduces the workload on your agents. The portal can be customized to collect the relevant information needed for agents to automatically triage any request and resolve issues faster. For example, Atlassian’s support customer portal comes with a bunch of optional fields that allow customers to provide their support request type, product, and license information. The end result is more feedback from customers, less work for support agents, and more actionable information for dev teams!

4. Bring your service and dev teams together under one process

Now that your customers can easily ask for help, it’s important to make sure your organization responds to their feedback. Focus on removing friction between your service and dev teams so you can start improving the product. Atlassian brings its service and development teams together with three simple strategies:

1.  Set up weekly meetings between service and dev team leads to review metrics and identify key issues

Setting up weekly meetings between service and dev teams helps everyone stay in sync with key performance metrics while ensuring teams are notified whenever important issues arise. For example, if support teams receive multiple support requests pertaining to the same issue, they can use this meeting to flag it to the dev teams to let them know its high priority. Accordingly, when dev teams know there is a new software update coming out, they can be proactive by using this meeting to surface the release support, provide them with release notes, and notify them of the correct actions to take should any issues arise.

2. Empower Service Enablement Teams to transform customer feedback into fixes and features

While Atlassian has blogged before about how they use their Service Enablement Teams (SET) to facilitate better collaboration between service and dev teams, it never hurts to reinforce a tactic that works. Atlassian uses Service Enablement Teams in order to accomplish two main goals: 1) aggregate feedback from support teams in order to provide meaningful guidance to dev teams on their product roadmap, 2) aggregate any information from dev teams regarding product changes so support can be prepared to handle every feature release. Having a dedicated team focus on these two outcomes clarifies ownership, aligns team functional goals with desired outcomes and breaks down silos to smooth the passage of key information between support and dev teams.

3. Consolidate service and dev work on one platform to keep everyone on the same page

Lastly, Atlassian uses Jira to keep service and dev teams in sync by taking advantage of powerful integrations between Jira Software and Jira Service Desk. When their support team receives a new request from their customers that require escalation to dev teams, there are plenty of options for their support agents to choose from.

They can link Jira Service Desk tickets to issues in Jira Software and vice versa. But that’s not all. Support agents can @mention developers on Jira Software or comment on Jira Software issues. Jira Software users can do the same thing on Jira Service Desk tickets. This allows both developers and customers to communicate directly with one another so they have the context they need to communicate more efficiently and resolve issues faster.

All these integrations help break down the silos between their development and support teams so they can more quickly incorporate customer feedback into their development process. Seamless integration means development teams can identify bugs faster, prioritize the features that customers care about most, and provide one consistent experience across customers, agents, and developers.

e-Core is a Platinum Enterprise Atlassian Solution Partner with over 180k hours/year dedicated to Atlassian related services. Join our mailing list to stay up-to-date with Atlassian solutions.


This post was derived from Atlassian’s Blog by Madison Friedman, Product Marketing Manager at Atlassian, published on January 12, 2018 with approval from Atlassian to repost, share and promote.

Read more:

Atlassian Open Forum NYC 2018

e-Core hosted the Atlassian Open Forum NYC at the Executive Conference Center on Broadway in Times Square. The forum was focused on taking ITSM to the next level with Jira Service Desk and other Atlassian tools.

Share This