Business Alignment Report
Last updated
Last updated
The Business Alignment Report helps you visualize where your teams are investing the majority of their effort and assist them in prioritizing their time effectively. This report displays your team's effort distribution across the categories defined in the associated Business Alignment Profile.
The report shows the metric value for each category as a percentage value along with an assigned target label (Ideal, Poor, Acceptable) on the Pie Chart.
The Trend Chart displays the detailed breakdown of the score in the Stacked Bar Chart format. It displays the trend of effort investment over time, based on predefined category allocations in the associated Business Alignment profile.
The Bar Chart breaks down the metric value into time intervals as configured in the widget settings.
Effort Allocation: This is the calculated percentage of effort allocated to a specific contributor and investment category within the chosen effort unit. It indicates how the effort is distributed.
Users may choose the desired effort unit at the widget level, such as Ticket Count, Story Points, or Ticket Time Spent. These units represent different ways of quantifying workload:
Ticket count: Represents the total number of tickets worked on.
Story points: Refers to the sum of all assigned story points.
Ticket time spent: Indicates the amount of time spent on tickets while they remain in the In Progress status category.
This report supports two types of drill-down views:
Drill down by Contributors
Drill down by Tickets
By selecting a category from the Stacked Bar Chart, users can access the drill-down report displaying data on the total completed effort, including the distribution of effort among individual contributors across all categories or just the selected one.
It also displays the drill down for tickets. When viewing the selected category on the Bar Chart, the widget will show data for all the relevant tickets included in this category. Alternatively, when choosing an interval from the bar chart, the widget will present data for items across all categories during the specified period.
The data is represented in tabular format. Additionally, both drill-down options offer search functionality, enabling users to look up specific contributors or tickets directly.
Please note that the Drilldown by Contributor option is available only if the widget is configured with FTE (By Engineer) settings for calculating effort.
Go to the Insight where you want to add the widget. Make sure you are in the correct project.
Select Settings, and then select Add Widget.
Select the Business Alignment Report widget.
Define the Issue Resolved In as either a relative or absolute time frame. You can also enable the Use Insight Time option to consider the data as per the active date configured on the Insight.
You can add more conditions to specify what data feeds into the widget by creating inclusive and exclusive filters (For example: Project etc)
If you include multiple filters, they are inherently combined with an AND operator.
Select the Business Alignment Profile that you want to use in the metric calculation for the widget.
Select the Effort Attribution as either Only use current assignee or Use current and previous assignee
Only use current assignee: This option considers only the current assignee of a ticket when calculating effort.
Use current and previous assignee: This option considers both the current and previous assignees of a ticket when calculating effort.
Select the Effort Unit as either Ticket count, Story points or Ticket time spent. This essentially defines how you want to calculate the effort for your alignment metric calculations.
Ticket count: The effort is calculated based on the number of tickets worked on.
Story points: The effort is calculated based on the sum of story points assigned to the tickets.
Ticket time spent: The effort is calculated based on the amount of time spent on tickets while they were in the In Progress status category.
Select the Effort Calculation as either Absolute (By ticket) or FTE (By engineer).
Absolute (By Ticket): This considers the total number of tickets assigned within a specific category.
FTE (By Engineer): This option considers the relative effort invested by the engineer across all the tickets that belong to different categories.
NOTE
If the engineer has worked on 5 tickets, belonging to 3 different categories, their effort is distributed across the 3 categories based on the Effort Unit and Effort Attribution selected.
Select the interval for the widget to display the data. This option allows you to choose the time interval for which the widget should display the data, such as Weekly, Bi-weekly, Monthly or Quarterly.
Complete the widget settings and select Next: Place Widget, place the widget on Insight and then select Save Layout.
In this example, we have a User X who is part of a team responsible for completing tasks in two different categories: Category A and Category B. These categories represent different types of work or projects within the team's scope.
Category A: Tasks encompassing significant effort, potentially critical features, or complex technical issues. These tasks demand substantial resources and attention from the team.
Category B: Tasks requiring comparatively lower effort, such as routine maintenance or minor enhancements. They may have a lower priority compared to Category A tasks.
In this scenario, we're analyzing the contributions of 3 contributors within two categories, Category A and Category B, based on the effort metric of Ticket Counts. The Ticket Counts represent the number of tasks assigned to each developer.
For Category A:
Total effort by User X: 3 (Ticket Counts)
Total effort by User Y: 2 (Ticket Counts)
Total effort by User Z: 1 (Ticket Counts)
Total effort for Category A =
The total number of tasks assigned to all team members in Category A provides an understanding of the workload distribution.
For Category B:
Total effort by User X: 2 (Ticket Counts)
Total effort by User Y: 2 (Ticket Counts)
Total effort by User Z: 1 (Ticket Counts)
This calculation offers insights into the distribution of tasks in Category B among team members.
FTE effort allows for a standardized assessment of individual contributions by considering the proportion of each developer's workload.
For Category A:
Total FTE effort by User X: 0.6
Total FTE effort by User Y: 0.5
Total FTE effort by User Z: 0.5
For Category B:
Total FTE effort by User X: 0.4
Total FTE effort by User Y: 0.5
Total FTE effort by User Z: 0.5
Here we convert the Absolute Effort (Ticket Counts) into FTE effort by considering the proportion of each developer's workload. This helps in understanding the relative contribution of each developer in terms of full-time work.
User contribution represents the percentage of tasks handled by each contributor within specific categories, aiding in assessing their involvement and impact.
For Category A:
User X's total effort in Category A = 3 (Ticket Counts)
For Category B:
User X's total effort in Category B = 2 (Ticket Counts)
To summarize the effort calculation for User X:
User X's contribution to Category A: 60%
User X's contribution to Category B: 40%
User X's contribution percentage is determined by dividing their total effort (Ticket Counts) within each category by the total effort by User X across all categories. This percentage showcases User X's share of tasks within the total workload of each category.
These insights help in understanding User X's workload distribution and their impact on different categories based on the chosen effort metric (Ticket Counts).
