Portfolio Plans (Beta) roadmapping tool in ADO is not a full-featured tool and lacks significant features that are needed to effectively create and manage product roadmaps. Are there any alternative extensions?
I am afraid that there is no such full-featured tool could meet your requirements.
For alternative tool, I suggest that you could try to use the Azure DevOps New Build-in feature: Delivery Plans 2.0.
This tool don't need to install any extensions. And the Azure DevOps Team will also update this tool regularly according to the needs of users.
If you have any further requirements, I suggest that you could submit the feature feedback in the following site: Feature feedback.
On the other hand, there are some similar extensions in the marketplace.
For example: Planner Extension , Portfolio++
But they still don't have full features.
I would use Portfolio++. It provides cross-project roadmaps, Epic/Feature Timeline - as well as Boards work-item quality assurance (Epic status), and the Pro version offers dependencies, milestones, and the ability to sort the order of the epics in the Roadmap.
Related
We have a scenario where we need to migrate more than a 100 projects that are in one ADO organization to another ADO organization.
Is there way how to do perform this migration org to org?
We have tried using the Azure migration devops tool by installing it in DEV test lab in A tenant and installed the tool.
Started with workitem migration but couldn't due to the errors.
So is there a way out to directly migrate org to org in two different ADO's?
There is no built-in way to migrate projects from one Azure DevOps organization to another. However, there are a few ways to accomplish this:
Use the Azure DevOps Migration Tools.
Use a third-party tool, such as OpsHub Integration Manager.
Manually export and import the data using the Azure DevOps REST API.
Currently, there is no supported method to move an organization directly to another inside azure devops, and you could follow this user voice ticket for the upcoming feature. make it possible to move a Team Project between Team Project Collections
As already shared in previous answers, there is no direct way supported by Azure currently, to migrate an org from one ADO to another ADO. There are a few third-party migrations tools that support this use case. When selecting migration approach, here are a few factors that should be considered, as these are often over-looked and cause trouble during the migration process:
What data can the migration solution migrate?
As there is no direct (Lift and shift) way supported by Azure to migrate, all third-party tools use ADO APIs to move data. As a result, there will never be zero data loss, e.g., no tool will be able to retain work item ID across ADO orgs. You need to list your must–have requirements (e.g., history, mentions, inline images, source code, work items, test management etc.) and then choose a tool that can meet most of them.
Can users continue to use source ADO, while the migration is going
on?
Downtime adds operational costs and impacts development operations as teams cannot use ADO during ongoing migration. Anticipate downtime required for scenarios which may cause further business disruption.
Time and monitoring required to migrate data?
If the migration tool is migrating projects one by one, it can take a lot of effort and time to migrate the data spread across 100+ projects. Understand how many projects can be migrated in parallel to have a speedy migration and minimize disruption.
What level of skills will be required to use migration tool?
Some tools are a collection of unsupported beta versions of scripts, requiring a very high degree of sophistication. These can be again highly time-consuming, error-prone, and can hinder operations. Analyze what part of migration may require script and involvement from your side.
As captured in the previous answer, OpsHub provides a Migration tool, OpsHub Azure DevOps Migrator (OADOM), which helps you migrate projects from one organization to another ADO organization. It provides rich data migration, including history, attachments, inline images, user mentions, etc., for a wide variety of data sets, including source code, test assets, work items, Area, Iteration, etc.
Please reach out to OpsHub’s Migration Experts to discuss how to migrate the projects from one ADO organization to another.
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
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
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.
We are currently using Trello to manage our workflow, however some of the developers want to change to VSTS and others want to stay with trello.
Can one give any insight as to what product is best?
It is based on your requirement, if current system meet your requirement and you don’t have the time to learn and transform to other product, you can use current product, otherwise I recommend you to learn VSTS and check with your requirement.
Regarding VSTS, there are many features, such as code manage (Git and TFVC) that can track changes, review code etc...; build and release system that you can verify project and deploy if needed; Package Management that you can manage the packages like Nuget.org. Also there are Scrum, Agile and CMMI process templates that can meet to different management workflow.