Microsoft Planner or Azure DevOps
We need to keep a track of tasks assigned to DevOps teammates.
I checked Azure Devops.
Azure DevOps gives you tasks and issue so that you can assign it to the members.
Not sure what MS Planner offers and should we chose that over Azure DevOps
Microsoft Planner is a task planning tool integrated in Office 365.
The level of capability from low to higher is corresponding task management to project portfolio management.
For a detail tutorial you could take a look at this link: Microsoft Planner - Step-by-step guide for users
Azure DevOps is a cloud-side source code management system also offering project management features as part of Microsoft's application life cycle management solutions. More project management features are accessible.
In Azure DevOps, you could also track work with Kanban boards, backlogs, team dashboards, and custom reporting.
Combine drag-and-drop sprint planning and flexible work item tracking with comprehensive traceability to have the perfect home for all your ideas–big and small.
You could also use the visualization options provided by Delivery Plans to review the schedule of stories or features your teams plan to deliver. Delivery Plans show the scheduled work items by sprint (iteration path) of selected teams against a calendar view.
Delivery plans is also interactive. You can change the assigned sprint of a work item by dragging it to a new sprint as shown in the above image.
I couldn't directly give you an accurate answer which one is better, it's all based on you and your team's requirement. They are totally two different products. Please kindly select the one suitable for your sides.
Related
I want to create another board to my backlog items, but i cannot figure out how to do this without creating another team with a separate backlog.
I don't want to create another project but want to remain in the same project.
I just want two ways to visualize the same data
I cant find any information when i google this
There are two different ways of displaying information about the backlog. A Board is an interactive way of looking at the backlog, so there's no way of creating two for the same backlog.
Azure Boards provides software development teams with the interactive and customizable tools they need to manage their software projects. It provides a rich set of capabilities including native support for Agile, Scrum, and Kanban processes, calendar views, configurable dashboards, and integrated reporting.
You might be looking for Dashboards.
Configurable dashboards and Power BI reports
With dashboards, teams can create customized views to gain visibility into their status, view progress, and analyze trends. Dashboards provide flexibility to share information and improve workflow processes. Each team can tailor their dashboards to share information and monitor their progress.
Also, you can use Power BI to create custom, complex reports based on custom queries of the Analytics service. The Analytics service is the reporting platform for Azure DevOps. It is optimized for fast read-access and server-based aggregations. Use it to answer quantitative questions about the past or present state of your projects.
There is a roadmap feature in JIRA, through which we can create Epics, user stories and assign start and end date to them itself by simply dragging the horizontal bar in table.
With help of this feature we can perform month-wise/day-wise or quarter-wise planning for any project. Additionally, we can export and share with client too. I require this kind of user friendly feature in Azure DevOps too. I tried integrating a Epics and Features Roadmap Plugin, but its not giving precise results as JIRA Roadmap is giving. Its user interface is very confusing, giving some occasional error message. Plus, it configuration is also very tedious and time-consuming. Can I get better user friendly GUI in Azure DevOps for Roadmap creation?
Please Help. Attached screenshots for reference of both platforms feature. Thanks in advance.
DevOps provides Delivery Plans to review the schedule of stories or features your teams plan to deliver. Delivery Plans show the scheduled work items by sprint (iteration path) of selected teams against a calendar view.
If it doesn't meet your requirement, you could check the existing extensions to see whether there are extensions useful:
https://marketplace.visualstudio.com/search?term=roadmap&target=AzureDevOps&category=All%20categories&sortBy=Relevance
When using Kanban boards in Azure DevOps, if the story is split into tasks, is there any support for working with tasks?
In the below image we can see the tasks with yellow under the stories but that is not easy for the developers to use. The task board can only be used if also working with sprints.
I haven't been able to find any documentation related to this. Are tasks supposed to be used at all when using a Kanban board?
Are tasks supposed to be used at all when using a Kanban board?
No, I'm afraid there's no such feature supported in azure devops boards now.
Because this is by designed based on the concept of Agile process.
See this Agile process workflow:
For Epic, Feature and Stories, they are all belong to Portfolio backlogs, while tasks is iteration backlog.
For our Azure devops Kanban Boards, it used to display the Portfolio backlogs for management team. You could add additional customized portfolio backlogs level by modifying the process your project is using.
But you could not change the tasks from iteration backlog to Portfolio backlogs. Because this does not match the basic concept of Agile process.
For Azure DevOps Boards, the Boards view visualizes the Requirement Backlog which is typically a User Story or Product Backlog Item, but it is not meant for moving Task states. For moving a Task between states, the Sprints view is used:
In my experience, for a team using an iterative methodology like Scrum or the Agile template, the Sprints view is likely more heavily used than Boards and the opposite is likely normal for a team using Kanban since Boards visualizes the requirements nicely for flow. Hybrid methodologies like ScrumBan could use both. Whatever works best for the team.
See this table and more information here:
I want to setup Azure DevOps organization wide. For that, we have decided that we will set up a single Azure DevOps organization and every team will work underneath this organization as separate project. The only challenge which I am getting is to determine the cost incurred by each project. Azure DevOps generates bill at organization level however we want to know how much a specific project incurred cost so that we can charge that team accordingly. I am not so much aware about azure devops billing prospects. Any insight would be very useful to me.
Currently there is no way to determine the cost incurred by each project, As you know the paid services(eg, paid basic access for users, paid ci/cd, paid test plan, etc) in azure devops are billed at organization level.
You can submit a suggest for such feature to be developed. Hopefully the development team will consider it and develop this feature.
You may have to manually calculate the paid resources(paid users, ci/cd(I found the build usage extension can be used to analyze ci/cd cost), paid test plans) that used by each project, and calculate a rough cost until the cost view for each project is developed.
You should be able to set unique custom tags, using the same per each specific project. Then from there you should be able to have cost propects based on tags specified by grouping on tags [1].
[1] https://learn.microsoft.com/en-us/azure/cost-management/quick-acm-cost-analysis
With the ability to configure how the bugs should manage, I'm confuse what to select as a process when I create a team project in VSTS 2017.
In the Microsoft guidance they say Agile
works great if you want to track user stories and (optionally) bugs on the Kanban board, or track bugs and tasks on the task board.
But even I select Scrum as the process, the bugs can be configure not to manage on the Kanban board.
and further
Choose Agile when your team uses Agile planning methods, including Scrum, and tracks development and test activities separately.
Isn't this same even I select Scrum as the process? I couldn't see any differences from the interfaces.
Of cause by choosing, Agile I can track original estimation and the completed work alone with the reaming work.
So what are the other differences, which I go for a one over the other? May be some reports like Stories Overview Report
Regarding Bug tracking, the workflows are different: Workflow states, transitions, and reasons.
For Agile process, the forecasting is based on Story Points and for Scrum process, it is based on Effort.
Regarding report, the link you provide is used for on-premises TFS. You can show report that you want in the custom widget or hub extension, so no difference.
Write your first extension for Visual Studio Team Services