You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Query charts are a great way to visualize status and trends. Also, by adding several charts to a dashboard, you can quickly review all the important data you want to monitor for your team or project. With that in mind, consider addressing the following questions with your team:
20
+
-*What are the most useful query charts for teams to create and monitor?*
21
+
-*What charts will help us maintain backlog hygiene?*
22
+
-*When creating trend charts, what time frame should I consider?*
19
23
20
-
What are some useful query charts for teams to create and monitor?
21
-
22
-
How to view total work done
23
-
How to view remaining work -
24
+
Not all teams have the same goals or tracking needs. However, teams that adopt Agile methods tend to routinely perform the following tasks. So consider the status and trend charts that will help your team perform these tasks.
25
+
-[Triage incoming work](../sprints/best-practices-scrum.md#tips-for-successful-triage-meetings), ensure new work is well defined
26
+
- Refine the backlog as described in [Backlog management ](../backlogs/best-practices-product-backlog.md)
27
+
- Plan sprints and set sprint goals as described in [Scrum and best practices](../sprints/best-practices-scrum.md)
Query charts and Query widgets for dashboards, customizing widget tile.
30
30
31
31
<!---TIPS
32
32
consider the time frame you want to monitor
@@ -39,6 +39,16 @@ Hi priority bugs
39
39
Triage bugs
40
40
Active bug trends
41
41
42
+
43
+
How to view total work done
44
+
How to view remaining work -
45
+
46
+
Create tasks and estimate work
47
+
How to view all work items
48
+
How to view work items I'm following
49
+
50
+
Query charts and Query widgets for dashboards, customizing widget tile.
51
+
42
52
## What status or trends should your team monitor?
43
53
44
54
Questions to answer
@@ -48,22 +58,29 @@ Questions to answer
48
58
- What team, product, or organization goals need to be monitored
49
59
- What recurring activities need to be done to maintain backlog hygiene?
50
60
51
-
<!--- What articles should link to this article?
61
+
What articles should link to this article?
52
62
- Does a change in Stack Rank count toward the Changed Date?
53
63
64
+
Tips: Pie charts versus Query count; can quickly see the types of work items
54
65
-->
55
66
56
67
57
68
## Maintain backlog hygiene
58
69
59
-
Here are a few tasks to review periodically, usually at the beginning or end of a sprint. Review this list for what makes sense for your team and organization goals.
70
+
The following queries can help your team maintain a healthy backlog by ensuring that work is assigned Here are a few tasks to review periodically, usually at the beginning or end of a sprint. Review this list for what makes sense for your team and organization goals.
60
71
61
-
- Unassigned work items
62
-
- Active work items not assigned to the current sprint
63
-
- Incomplete work assigned to a past sprint
64
-
- Stale work items, no changes made in the last 2 to 3 months (query by Changed Date)
65
-
- Ill-defined work items such as no Story Points or Effort defined
66
-
- Unparented work
72
+
| Query focus | Query clause |
73
+
|-------|--------------|
74
+
|Work assigned to a sprint but not assigned to a team member| :::image type="content" source="media/example-queries/query-no-assigned-to.png" alt-text="Screenshot of Query Editor, Assigned To field is blank for current iteration.":::
75
+
|Active work items not assigned to the current sprint | :::image type="content" source="media/example-queries/query-active-but-not-current-iteration.png" alt-text="Screenshot of Query Editor, Active but not assigned to current iteration.":::
76
+
- Active work items assigned to a past sprint | :::image type="content" source="media/example-queries/query-active-past-iteration.png" alt-text="Screenshot of Query Editor, Active but assigned to a past iteration."::: |
77
+
|Stale work items, no changes made in the last 2 to 3 months (query by Changed Date) | :::image type="content" source="media/example-queries/query-stale-work.png " alt-text="Screenshot of Query Editor, Active work not changed for past 3 months."::: |
78
+
|Ill-defined work items, for example, ones with no Description, Acceptance Criteria, Story Points, or Effort defined| :::image type="content" source="media/example-queries/query-ill-defined-work.png " alt-text="Screenshot of Query Editor, Work with empty required fields."::: |
79
+
80
+
In the following image, all five query charts appear on a team dashboard. To add query charts to a dashboard, see [Add charts to a dashboard](../../report/dashboards/add-charts-to-dashboard.md#add-a-work-item-query-or-chart)
81
+
82
+
83
+
:::image type="content" source="media/example-queries/dashboard-backlog-hygiene-query-charts.png " alt-text="Screenshot of Dashboard with five query charts added.":::
67
84
68
85
69
86
## Example status charts
@@ -72,17 +89,16 @@ Here are a few tasks to review periodically, usually at the beginning or end of
72
89
-**Active bugs**: Agile teams monitor their bug or technical debt and set goals to maintain the total number under a specific number.
73
90
-**Active bugs by assignment**: Monitor bugs assignments across a team to support load balancing.
74
91
- Active bugs by state
75
-
-**Tagged work items**: Monitor tagged work to ensure the team is meeingt specific goals, milestones, or categories of work.
92
+
-**Tagged work items**: Monitor tagged work to ensure the team is meeting specific goals, milestones, or categories of work.
76
93
-**Blocked work**: How much work is currently blocked? You can query blocked work using a tag or custom field.
0 commit comments