For your business to succeed, you probably need to use a number of different platforms. Companies might need platforms for collaboration, productivity, task tracking, and more. Two platforms that successful companies use to help solve product issues and achieve more are Jira and Profit.co. While Jira uses epics to track product issues and client requests, Profit.co is an OKR-focused management software to help teams achieve their goals. These two software play an important role in the success of a company– where is the overlap between Jira and Profit.co?
Sound strategy starts with having the right goal.
Epics as a larger story help break user stories with a distinct beginning and the end, into smaller tasks based on the demands and needs of the end users or the customers. Also, these tasks can be added or removed from the epic story as per the customer’s demand. All the epics and the objects within an epic not only contain stories and tasks but also manage issues and bugs and all of these get managed within Jira. So the main objective of the Jira epic is to help users organize and prioritize their work in order to create a structural hierarchy. This is because epic has the agility to organize more complex tasks into simple, smaller tasks.
In Jira, an epic breaks down into tasks. However, in Profit.co, epics can be used as key results. In Profit.co, users define their aspirational objective and use key results to help quantify and measure the success of this objective. The standard rule of them is that an objective should have between 3-5 key results.
When using Jira alongside Profit.co, this means that each Objective can have between 3-5 epics as key results. Teams with OKRs focused on delivery will have epics as their key results. Meanwhile, higher-level teams won’t get their key results directly from Jira. Instead, alignment between higher level teams and delivery-focused teams happens in one of two ways:
- Lower level objectives will get aligned up as key results or,
- Higher level key results will get cascaded down to the next level as objectives or key results or sub key results.
Take a look at the image above. This shows the relationship between Profit.co and Jira. In Profit.co, the company objective and the key results have been cascaded at multiple levels towards the teams/department’s OKRs. Whereas in Jira, the Epic story further breaks down into story, issue, and task. The blue line represents where these two worlds are bridged by an integration.
Click here to learn how to install, configure and model epic story points as key results by integrating Profit.co with Jira software.
Listed below are steps that guide you through linking Profit.co department OKRs that are cascaded towards company objectives by integrating the key results with that of the epics created from Jira.
Once you select the Project you can create issues under the epic that you want to link as key results with the Objective in Profit.co. Click on Issue from the left navigation panel and then, select the epic from the list.
Now click on the Profit.co OKRs to link the epic with Profit.co.
Now click on the Click to view all linked OKRs button.
Now select the department from the list of All My OKRs list. Here the Customer service department is selected. You can link any number of created epics with the Profit.co OKRs.
Click on the Plus icon next to the objective name, Now select Task % and click on the Select button.
Once you click on the Select button, click Add from the pop-up menu to add the epic details and the issue details. Now the percentage of the task will be visible to you.
Login to your Profit.co account with the same credentials that you used in Jira, Select the Department name and you will find the list of epics linked as key results to the objective of Profit.co. Based on the status of the tasks in the epics, the percentage of the key result will get updated.
This is one of the ways to integrate Profit.co OKR with Jira, you can also link both Profit.co and Jira in various creative ways and some of them are listed below. On top of this, there may be other execution systems feeding KRs to Profit.co — either Task/Project based (asana, etc) or KPI based (Salesforce, etc).
- OKRs for Jira : Modelling epic story points % as a key result.
- OKRs for Jira: Modelling epic progress based on the issues as a key result.
- OKRs for Jira : Modelling epic progress based on the issues % as a key result.
- OKRs for Jira : Modelling task hours as a key result.
- OKRs for Jira : Modelling task hours % as a key result.
- OKRs for Jira : Modelling task as a key result.