Follow

Useful reports

Useful reports

 

 

 

Team impediments

Problem:

As a scrum master I want to find items that are currently in a blocked status so that I can help my team clear out Problems.

Query string:

Statuscompletion= Blocked AND Itemtype= "Backlog item" AND Assignedto:Resource()

Instructions:

This report would typically exist in the project schedule.

In the box “Assigned to” you should select the team members or groups you want to see blocked items for. If you want to see all blocked items in a project you can delete that box.

I would group the report the report by “Assigned to” so that the blocked items are grouped by person that owns it currently.

 

What are we blocking?

Problem:

As a scrum master I want to find items that are currently blocking some other item in the project so that we can focus our efforts on those things.

Query string:

Assignedto:Resource() AND Linkedtoitem=>Text(Blocked)

Instructions:

This report would typically exist in the project schedule, but it could also exist in the QA section to list bugs that are currently blocking development progress.

For this report to work the team must use the “Linked to item” in combination with blocked status to signal a dependency between items.

In the box “Assigned to” you should select the team members or groups that you are interested in seeing if they have any blocking items. If you want to see all blocking items in a project you can delete that box.

I see two options for grouping, either you group by person that owns it to find out who to talk to or you would group them by “Linked to item” to see all items that blocking a specific item.

 

Team's ToDo list

Problem:

As a scum master I want to see the todo-list of all my team members. I want them to grouped by person and ordered by sprint priority. I don't want to see completed work.

Query string:

GeneralconditionOngoingwork = true AND Assignedto:Resource() AND !Statuscompletion= Completed

Instructions:

This report would exist in the project schedule.

In the box “Assigned to” you should select the team members or groups you want to see the todo-list for. If you want to see all todo lists in a project you can delete that box.

The report should first be grouped by “Assigned to”, then by "Commited to sprint" and sorted by sprint priority.

 

Team's schedule task list

Problem:

As a project manager in a scheduling project I want to see the todo-list of all my team members. I don't want to see completed work.

Query string:

(Statuscompletion= "Not done" OR Statuscompletion= "In progress" OR Statuscompletion= Blocked) AND Assignedto:Resource() AND Itemtype= "Scheduled task"

Instructions:

This report would exist in the project schedule.

In the box “Assigned to” you should select the team members or groups you want to see the todo-list for. If you want to see all todo lists in a project you can delete that box.

The report should first be grouped by “Assigned to" and sorted by "Start".

 

Release status

Problem:

As a product owner, I would like to know the status of a work package tagged to a specific release and get an overview of what user stories/functionality risk falling out of the release so that I can make corrective actions as early as possible.

Query string

Releasetag:Item(420637)

Instructions:

This report is created in the product backlog. Prerequisites for the backlog set-up is that all user stories meant for the release/milestone carry the relevant release/milestone and that their backlog priority is defined.

For this report, you will only have to create one find criteria. The find criteria should search for "release/milestone tag" and you need to specify the relevant release/milestone. You then group the report by status and sort the results by product backlog priority.

 

Incomplete planning

Problem:

As a project manager I want to find all work that haven't been assigned to anyone or has no work remaining set so that we can tidy up after the sprint planning.

Query string:

Assignedto=Resource() AND !Statuscompletion= Completed OR Workremaining < 0.00 AND !Statuscompletion= Completed

Instructions:

This report would exist in the project schedule.

Typically you wouldn't sort or group this report.

 

Find user stories targeted towards a certain user role

Problem:

As a product owner I would like to see all the user stories in the backlog that contains a certain user role that are not completed.

Query string:

Userstory:Text([i]user role[/i]) AND !Statuscompletion= Completed

Instructions:

If you are working very heavily with user roles this report can be helpful to find the remaining of all the user stories for a certain user role.

If you include completed items it might be a good idea to group the output according to status.

 

Remaining workload

Problem:

As a product owner I want to see the remaining workload in the ongoing sprints so that I can get a feeling if the sprints will be successful or not.

Query string:

GeneralconditionOngoingwork = true AND !Statuscompletion= Completed

Instructions:

This report would exist in the project schedule and you would group the output by person. Since the only thing we are interested in is work remaining it might be an idea to select work remaining as the only visible column.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments