I am discovering the Azure Delivery Plan but I don't understand why I don't see all my Features in there.
This is what I am talking about:
https://learn.microsoft.com/en-us/azure/devops/boards/plans/review-team-plans?view=azure-devops&tabs=plans-preview
I have looked at the Tags, owners, start/end dates, and so on but can not find any criteria which indicate why I see certain Features and not others.
I am also a member of the projects that I do not see.
Can anyone shed some light for me on this one?
In my test, if the dates of two iterations overlap, the features under the iteration will not be displayed.
For example:
If the date does not overlap, the features under the iteration will be displayed normally.
You can check if this is your case.
This one is actually on me and was kind of logical.
The features were on the backlog and didn't have any iteration assigned, hence, there were not showing below any iteration.
Thank you for the suggestions and feedback! Case closed!
Related
I am a PO leading a small development team for enhancements to our PeopleSoft Campus Solutions application for a Medical School.
We are using the Sprint functionality in ADO to assign stories from our backlog to the Sprint, create the relevant tasks for each story (mainly development, testing, deployment) and assign the tasks to resources who, in turn, provide effort values (original estimate, remaining, completed). We also make sure our capacity is properly set, with resources OOO time and school holidays configured to get an accurate team and resource capacity. The team updates their effort numbers daily to ensure we are tracking burndown.
While we always start the Sprint with the remaining work hours under team capacity (and the same at the resource level), we have historically left alot of remaining work on the table at the end of the Sprint.
My leadership wants to answer the question "Why was the work left on the table?". Of course, there could be MANY reasons, we underestimated the effort, we were blocked on a task (for example, we can't start the testing task until the development is done), the resource didn't actually have the calculated capacity due to being pulled into other meetings or initiatives, or (and I don't think this is the case) people were just plain lazy.
What reports/analytics can I leverage to help answer this question? Even just seeing a list of remaining tasks per resource with remaining task effort and with a total amount of work remaining per resource overall would be helpful, but I can't seem to find anything.
Any suggestions or guidance is appreciated!
You can use Queries to find the remaining tasks(add column option->Remaining Work) and save the query into Shared Queries.
There is a query results widget in dashboard to display the query in Shared Queries. Do not forget to add Remaining Working in widget.
Remaining Work:
You could refer to the document: Adjust work to fit sprint capacity
My organization is trying to find an out of the box way with Azure DevOps to see which features were 'committed to' at the start of the release, and which are delivered. The Velocity report would be perfect, except Features are assigned to areas that are configured to run off of sprints that are child-iterations of larger release-iterations, and we want the data at the release-iteration level.
We're able to build queries that can mostly deliver this, but that method doesn't track changes, just shows you a current point in time view of how things are.
The goal is to have data we can use to evaluate if we're making commitments we can keep.
How have other organizations tackled this sort of problem? How do you tie committed vs. actuals at the Feature level?
I could understand your requirements. But based on my test, Velocity Report has some limitations:
For example:
If the Iteration Path has Child Iteration, it will show the child Iteration on Velocity Report. As you said , release-iteration will not show in the Report.
So it cannot meet all your needs.
I tested some related extensions and existing charts, and it seems that there is no tool that can improve or replace the Velocity Report .
For a workaround:
For Child Iteration, you still could use the Velocity Report to record the process.
For the Parent Iteration, you could create different queries to show the process(Planned
, Completed,Completed Late and so on). You can use query to get the work item list of the corresponding state.
Here are examples:
Planned :
Completed:
...
Then you could add them to the Dashboards(Query Title Widget):
On the other hand, this requirement is valuable.
You could add your request for this feature on our UserVoice site, which is our main forum for product suggestions.
I would like to be able to easily see the sum of remaining work (on a Feature) for each activity.
In this example-picture I have a Feature "Keys 0.1" that I would like to add to my sprint. Say I have 60hrs free in the sprint.
At first glance it looks like I can comfortably add the entire feature without any problems. BUT!
Lets say the sprint has room for 20h frontend work and 40h backend work. If that's the case then I cant really add this Feature since it's too much frontend and not enough backend. Our current sollution is to pretty much add stuff, checking if we're fine and removing if we're not.
Is it possible to somehow get "Sum of remaining work Frontend" and "Sum of remaining work Backend" as columns?
One thing I tried was to add 2 new custom fields: "Remaining work Frontend" and "Remaining work Backend". This works fine for the backlog, but when I added tasks to my sprint it didn't use those fields to calculate capacity/remaining time. Does anyone have any ideas of how to get a better overview of how much time something will take grouped by activity?
Get "Sum of remaining work Frontend" and "Sum of remaining work Backend" as columns
Steps:
Open process->select work item type->add new field Create a field Remaining work Frontend and Remaining work Backend(Type: Decimal).
Open Backlog page->Column Options->Add a rollup column->Configure custom rollup->select Roll up as Total and configure the sum column.
In addition, we cannot use these fields to calculate capacity/remaining time.
I hope it can help you.
Update1
We found a similar suggestion ticket. You can add comments in the ticket to describe the feature. To receive the notification about it in time, you can vote and follow this suggestion ticket.
I hope this can help you.
Our teams are using Azure DevOps. We're using the Agile framework and an enterprise release management approach (essentially, SAFe). Our increments are based on the quarters of the year -- for us, this equals 6 sprints.
My goal is to be able to view work scheduled within the current increment as the sprints move along.
I currently have a query that displays current sprint plus the future 5, to give me 3 month's worth of work (see below).
The trouble with this is it has to be edited after each sprint so it only displays the current increment's work. (I have to change it to include the previous sprint and reduce the number of future sprints otherwise it doesn't display completed work in this increment, as well as showing upcoming work from the next increment.)
Increment Planning Query
Sorry for any inconvenience.
I am afraid there is no such increment planning query, that because the value of CurrentIteration will be different due to the change of the current date.
If you want use the #CurrentIteration macros, you have to modify this query after each sprint.
As workaround, you could specify the each Iteration value in the query, like:
With this workaround, we do not need modify the query after each sprint, just need update it after each quarter.
If above workaround not work for you, you could add your request for this feature on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps:
Hope this helps.
I was looking on VSTS, but I didn't found how to estimate our Tasks/users story in hours instead of Story point.
Is this possible?
I know the pro(and cons) of story points, buf for now our team want to move progressively with agile, and we don't want to start to estimate in story points.
Thank you!
Edit as requested, I currently use the agile template(but open to change)
Declare "One story point is equal to one hour" and use the existing field as-is.
TL;DR
Use the built-in scrum template
If you use the built-in Scrum template Tasks have Remaining Work and PBI's have Effort. Nothing says Remaing Work = hours or Effort = story points.
If you want to estimate your tasks in number of 4 hour work blocks it will take to complete you can do that, if you want to do it in hours you can do that. Same goes for effort you can put any number in there you want as long as you make sure everyone in your team understands what 1 or 5 or 10 means.
So if possible switch to the scrum template, your question is exactly the reason why these fields have a more generic name than Story Points or Remaining Hours in the scrum template. Added bonus is that your team can switch definition if they feel like some other number or unit suits your estimation process better.
This blog post makes a good comparison between the built-in different templates:
https://nkdagility.com/choosing-a-process-template-for-your-team-project/
If you are an administrator in VSTS select the VSTS button at the top left of the screen. Then select then select the cog.
This will take you to a page where you can edit a number of settings. Select Process.
In the process window choose the process your project uses. You can see which one your project is using by the numbers on the right hand side of the process. Once you’ve found your process select it by clicking.
Then choose the work item type you wish to change. So in this instance user story.
Once in the task you want to change select add group and name the group want to add and select it's placement on the card.
When the group has been added select it and choose the ellipses (...). Then select Add Field. Customise the field to be either a new one of your choosing or choose a predefined one.
Once you have added this step repeat the process on this page to customise and style the task how you like. Once done navigate back to your project in VSTS and the changes will be applied