Reports for Effort by role | Targetprocess - Visual management software

Reports for Effort by role

In Targetprocess it is possible to estimate Effort per Role. Say you may enter 8 h for Developer and 2 h for QA Engineer. Most predefined reports just summarize these values. However you can build advanced reports showing distribution of effort by roles as well.

Improperly configured calculations and reports may be not accurate enough. Verify the reports before using them for billing and invoicing purposes. Use non-verified reports on your own risk.

Use Case

Let's create a basic sample dataset for our future reports. We'll create two user stories and specify effort per role.

EntityDeveloper EffortQA Engineer Effort
User Story 116h4h
User Story 28h2h

us1 us2
Both user stories are displayed in the board view. Using Customize Cards it is possible to display total Effort on them.

Use Case

There is no unit for role effort available by default. However, it is possible to create a report showing Role Effort distribution per User Story. The report can be exported.

List of User Stories with Effort by role specified

Visual report

Create a new Visual Report based on Assigned Efforts data source.

Visual report

Reports for Effort by role. Image 5

Put Assignable field to horizontal axis and Effort to vertical one. Put Role field to Color encoding selector.  Select Bar as chart mode.

us-effort-report

Make sure that Effort and not SUM(Effort) formula is used for vertical axis. It helps to avoid duplication when your work items have multiple users assigned under the same role.

As a result, the chart shows role effort per each user story. Roles are encoded by color.

Reports for Effort by role. Image 7

Report with all data and displayed fields can be exported to the CSV file. Here is how it looks in tabular form:

Reports for Effort by role. Image 8

More details of assignments or assignables

You can include more details into your report by Assigned Efforts. Label may serve this need: add the property you're interested in (such as Assigned User, Release, Sprint, Project etc.) into Label field to make it visible in the report and exported file.

Let's distribute user stories from our dataset by two releases.

More details of assignments or assignables

And we'll put Assigned Release field into Label encoding.

Reports for Effort by role. Image 10

Every bar becomes annotated with name of Release a user story is assigned to.

Exported CSV file also contains Release as a column:

Reports for Effort by role. Image 11

Report for Release / Iteration with total Effort summary per role

A report showing total Role Effort per Release or Iteration is also supported. Let's distribute user stories from our dataset by two releases.

More details of assignments or assignables

We'll now build a report showing summary of Role Effort per Release.

Visual report

Create a new Visual Report based on Assigned Efforts data source.

Visual report

Reports for Effort by role. Image 5

Put Assignable Release field to horizontal axis and SUM(Effort) to vertical one. Put Role field to Color encoding selector.  Select Bar as chart mode.

Other fields such as Assignable Project, Assignable Iteration, Assignable TeamAssignable Team Iteration are supported as well and can be used for grouping of your work items.

Reports for Effort by role. Image 15

As a result, the chart shows total role effort per each Release. Roles are encoded by color.

Reports for Effort by role. Image 16

Report with all data and displayed fields can be exported to the CSV file. Here is how it looks in tabular form:

Reports for Effort by role. Image 17

This report may provide you with incorrect totals when multiple users are assigned to a work item under the same role. To make the report more accurate, split assignments as described in the article: Effort is duplicated in reports based on assignments.

Still have a question?

We're here to help! Just contact our friendly support team

Find out more about our APIs, Plugins, Mashups and custom extensions. Join our community of passionate users and even discuss directly with our developers.