How to Automate and Monitor your OKR Progress from Azure DevOps?

Now Profit.co will automatically update your OKR in real-time, now the effort points are directly linked to a key result. Monitor your OKR progress and address the areas that need your attention to improve project delivery performance.

Why this feature ?

OKRs are usually implemented to track the success of DevOps initiatives, communicate the objectives in a consequential way to your organization. Using OKRs can help drive progress in your DevOps department which makes a huge impact on focus and productivity.

Follow the below steps to create your Jira epic as a key result under a Profit.co OKR.

Step 1

Once Profit.co OKR software app from Azure DevOps is installed and configured, you will be able to see Profit.co OKRs on your Azure DevOps page. And your Work items can be to your OKRs.

Step 2

Now click on the work item epic which you wish to link with your key result in Profit.co.

Click on Profit.co OKRs to see your individual OKRs in Profit.co.

Click on the drop-down to view your Corporate, Department, and Team level OKRs.

Step 3

Now, Click on the + icon against any OKR to create your Azure DevOps epic “Improve on-boarding experience” as a key result under that OKR.

Step 4

Now add the details of

1. Count of work
2. Sum of effort
3. Work items

Once you link them all, the key results will be highlighted.

Step 5

Now, your epic is created as a key result under the objective “Improve Customer Satisfaction”

Step 6

Click on “Go to linked OKRs” to see the progress of the linked key result.

Whenever you complete a point under the Azure DevOps epic/issue, your key result in Profit.co will automatically be updated based on points assigned to it.

Step 7

Your actions of adding and removing stories will also be synched in the key result.

You can see, the key result “Improve on-boarding experience” is created under the objective “Improve Customer Satisfaction” with a KPI “Count of Work Items”.

Note: You can rename your key result in Profit.co. It won’t create an impact on your Azure DevOps epic name.

Related blogs: 10 Great DevOps OKR Examples