I need to analyse the team's productivity by user.
I would like to see how many tasks each user burned, but I would like to see too, the sum of the work planned by each burned tasks (the "Remaining Work" column when the task was created).
Can anyone tell me how I can do this?
How can I analyze the user productivity in Azure DevOps?
There is a side plan Work details under the view options for Sprints:
If you set sprint capacity correctly, you will find the work details for team and user.
If you want to see how many tasks each user burned, you can add a Query to get the list:
Hope this helps.
Related
I do quite a lot of security reviews on 365 tenants, which I have made an template. This is all written in a WIKI in DevOps. To that I have an Microsoft Planner this is everything taken out in headlines. This I usually go though with IT.
After that I do an report based on this planner.
But would LOVE to automate this process as the report task is so time consuming and a lot of it is copy paste.
I was thinking of changing my Planner and WIKI out with Work Items in DevOps. This way I could document directly in Work Items what IT is reporting and export the Work Items.
It does however (to my knowledge) not scale that good. It seems to me that I would have to create a DevOps site for every IT department/tenant.
Would love to hear from anybody who have experience with this or related to this.
I have tried with Work Items, but could not make it scalable for more than one IT department.
I've been using Azure DevOps Dashboard for a while now and it's working nicely. One gap I have found is in it's Lead Time Chart. This goes from date creation to date completed, which in an Agile world doesn't make sense.
Backlogs can be thought of a placeholder for a conversation, following this initial backlogs can be vague and poorly defined, and more information and clarity will be added as the backlog moves closer to being actionable.
What I would want is a "Estimated to Completion". SCRUM teams estimate when there is enough information that the item could be pulled in to a Sprint, and this is the point where the lead time really makes sense.
Is it possible to add this to the DevOps dashboard, is there a query that will give me what I need?
Thanks,
John
We are using Azure DevOps to track our development work. I can open an individual story and see the history of changes and the chart of the status history. This is useful for an individual story, but doesn't allow me to identify trends and possibly highlight issues in our processes.
I would like to have a chart, or an export that shows the historical changes for all stories (within a date range, or some other filter) so I can discover:
How long does a story stay in each status, on average? (Q: Which statuses take the most time)
How many times is a story set to a status, on average? (Q: When and how often are we moving backward in the flow)
How many times does a story move backward for each team member? (Q: Where should we focus our training efforts)
I have searched within the dashboard, reports, and online for some way to get this information and either haven't used the right keywords, it doesn't exist, or I totally missed it.
Does anyone know if this type of information is available and how I can access it?
There isn't an easy way to accomplish this, unfortunately. Your best bet is going to be composing a Power BI report or Excel, whichever you're most familiar with. Even then, you're going to run into problems with #2 and #3. Microsoft doesn't have an easily accessible way to query the history of each status among all work items.
However, #1 is possible within PowerBI and Excel. Here are a few guides to get you started:
Excel
To import Queries into excel, you have to install a few things follow this guide to get started:
https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/office/track-work?view=azure-devops&tabs=open-excel
Power BI
To get started consuming Analytics views within Power BI, follow this guide:
https://learn.microsoft.com/en-us/azure/devops/report/powerbi/create-quick-report?view=azure-devops
Whether you're using PowerBI or Excel, the fields you'll want to include within your query or Analytics View will look like "[STATUS] Date", "Closed Date" for example. That will make them accessible within PowerBI, or Excel, depending on which you go with.
Once you have your data, you'll want to create reports that compare the status dates to determine how long a story stays within a status.
Azure DevOps Report for User Story Status History
Azure devops is not intended to be a time tracking tool. You could query the work item history with the TFS API and check the timestamps on when the state transitions occurred if you really wanted to.
So, Azure devops doesn't track the time spent on a per day basis. It keeps track of the total time spent. If you want a per person per day value, you'll have to go through the iterations/workitem history and calculate the running difference.
If you really looking for a TimeReporting for the work items of per person, I suggest that you take a look at a third party yool like Timetracker:
Timetracker
New to version 5.0.! Individual, team, and custom reports powered by
version 3 of the REST-based reporting API. 7+ customizable widget
types that let you see data that you need, how you need it. In
addition to the six default reports in Reporting, users can create
custom reports for individuals or teams.
On the other hand, we could develop our scripts via REST API Revisions - List to get the System.State change and System.ChangedDate, then compare the date to get the time in each status.
On Azure DevOps, I have a set of test cases and every test case has a number of related bugs (from 0 to you better not know :p). The link type here is "Tests".
I would like to sort the test cases by number of related bugs, to make an estimation of the most buggy parts of the software.
I've tried but I only found the option "Number of links" ("Nombre de liens associés" in French).
Thanks in advance.
EDIT: we use Azure DevOps Server, not Azure DevOps Service. Thus, unfortunately I can't follow the steps here: https://learn.microsoft.com/en-us/azure/devops/boards/queries/linking-attachments?view=azure-devops#list-items-based-on-linked-dependents
Sort test cases by number of related bugs on Azure DevOps
For this issue , I am afraid it is currently unachievable in azure devops. Currently, there is no feature of sorting by related work items in azure devops.
Running the following query in the azure devops server, you can get all test cases containing related bugs , but you cannot sort these test cases.
Apart from the negative answer, I think what you want is a good idea! So I post a feature request here in DC forum. Anyone interested in this can vote for it and track it. You could vote that suggestion ticket and share your comment there,The product team would provide the updates if they view it.
You can do that only through customization:
Add a new field like Bugs Count or Active Bugs count. Add and manage fields for an inherited process
Create custom app to fill that field with real count of bugs through REST API. Wiql - Query By Wiql, Work Items - Update
Then you can use a column setting to edit the sort order of your query result.
I'm currently using Team Services with multiple teams but am having an issue with displaying tasks on the specific team's backlog.
I have created two teams (Portal & Core) with there own area.
I have created a story and have set it to the root area.
To complete this story requires effort by both teams. I have created a task for the Portal team and set it to their area and another task for the Core team and have set it to their area.
If I look at the teams backlog I cannot see the task for them (I have set Show Parents).
Should I be able to split tasks of a story across multiple teams?
Thanks
No, there isn't any way to achieve this directly. But there is an alternative method for this, refer to the steps below for details:
Go to the "Work\Area" settings of the root project and add a new child area for example "TwoTeams".
Go to the "Work\Area" settings of the child projects(Portal & Core) and add "CrossTeam\TwoTeams" area to them.
Assign the user story to "CrossTeam\TwoTeams" area.
Now you will see the User Story and Tasks on the teams backlog like following:
Whether you should be able to is one thing, which is a broader topic. Whether you can is a different question, one with an exact, factual answer: You can't.
A user story is intended to be a discrete unit of work that is completed by a single cross-functional team. If you have multiple teams working on one user story, chances are good that the user story is too large and should be decomposed further.