With Calculated Fields, assign values to each item item in your backlog to determine the relative priority, making it easier to decide what to focus on next with data driven decisions.
Calculated fields allows integer and picklist fields in an item to be calculated for addition, multiplication and the average. You can use relationship counts (number of upstream and/or downstream relationships) as a factor in a calculation to evaluate the “social weight,” the number of connected users and comments to provide a weight based on people impacted.
These calculations will allow for negative numbers and up to four decimal places.
Prioritize Items in Your Backlog
When planning work, product teams need to measure the impact that the development of a specific feature will have on your customer experience versus the impact it will have on your development team’s output. If your team works within the Agile SAFe Framework, and you’re familiar with WSJF (“Weighted Shortest Job First”), which helps teams plan work in a continuous flow, then these calculated fields can help with this prioritization.
You can set up calculated fields to determine:
Level of Effort + Customer Impact = Priority
An item with critical severity and a low level of effort would receive the highest priority value in the backlog.
1. Assign Level of Effort
First, assign the level of development team effort to the proposed feature at the item level. Here we’ve assigned a numeric value to three levels of effort: Low, Medium, and High.
2. Assign Customer Impact
Next assign a level of customer impact — however you define this in your organization — and a value. Here we’ve given values from “not important” to “critical,” with a wide range between “high” and “critical” in order to ensure that true must-have features are given top priority.
In this model, a critical item with low level of effort receives a score of 15, while an item with high level of effort and low priority receives a score of 2.