Atlassian’s JIRA was originally created as a tool to give software developers everything they need to build great software through strong teamwork, from project management to issue tracking. And Atlassian did a fabulous job with this! If you talk to developers, you quickly find that those who use Atlassian’s tools are extremely enthusiastic about them.
Although Atlassian initially focused exclusively on meeting the needs of software developers, today they are moving into the space that used to be owned by SAP’s enterprise resource planning software: business process automation. In fact, Atlassian’s JIRA Core was specifically designed for business teams. JIRA Core is a stripped-down version of JIRA that’s meant for tracking business processes and work flows, all in a non-software-centric way.
The case for using JIRA core for business process automation
While Atlassian is certainly not the only company trying to move into the business process automation space (another notable entrant is Salesforce, which has moved from being “CRM in the Cloud” to also being used to run a variety of front-end systems), Atlassian does offer business teams some significant benefits. Here’s what I’m seeing…
Of course, because Atlassian offers little in the way of off-the-shelf solutions for specific use cases, this extreme flexibility can be perceived as a positive or a negative. As with most software, whether or not JIRA Core is the best choice for your group depends on your needs.
Use cases for JIRA Core include tracking Human Resources service requests, processing job applicants, managing Marketing campaigns or financial processes, handling vendor management, tracking legal cases, and much more.
JIRA Core is also well-suited for business processes that are completely digital, such as automating the entire e-commerce sales process, from taking the order to scheduling the drop shipment from the vendor.
Where business teams often get tripped up
Unfortunately, JIRA Core’s flexibility—and associated need for fine-tuning—can often be a stumbling block for non-IT teams. To automate a business process you need to be crystal clear about the components of that business process. Someone needs to be able to answer the important “big picture” questions, including:
What I’ve seen is that the first five questions on this list are easier for the average business team member to answer than the last question is. Creating a detailed flow chart is a very process-minded activity that those who don’t think like systems analysts often find very difficult to do.
To make JIRA Core work you need to be able to think in those process-oriented terms. Having the ability to figure out how all the little pieces fit together is a unique advantage for the gear head! This is where it is often a good idea to bring in experienced consultants, such as Coyote Creek. Consultants can bridge the gap, helping your end users to define processes well enough so that they can be successfully automated.
Selling business teams on the value of JIRA Core
Another stumbling block for implementing JIRA Core as a tool for business process automation is selling it to the members of the C-suite, many of whom are not familiar with any of the Atlassian tools.
Also playing into this issue is that there are two different cultures that exist within the C-suite; the CEO and CFO have different cultural backgrounds than the CIO or CTO. For example, those who are not involved with technology usually see themselves as being engaged with technology, not as being moved through processes via technology.
To help these people understand the value of using JIRA Core to automate business processes you should focus on the end results. What will things look like once this is in place? How will this change processing times and costs? What will it enable that is not possible without automation?
I have one last thought on this topic, and that is this: With the increasing digitization of everything, including the advance of the Internet of Things (IoT), many businesses are essentially becoming software companies. They must live in a digital world and must embrace a collaborative mentality. Atlassian speaks to this beautifully, as “teamwork” is built into Atlassian’s DNA. Atlassian has always been about connecting people and helping them build something greater than they can do individually. Which, of course, is what businesses are trying to accomplish every day.
Reproduced from my guest blog posting on Coyote Creek Atlassian Solution Partner's site: Coyote Creek blog site
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events