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.
Related
I'm thinking to move to Azure DevOps. But I'm at the stage where it's hard to decide which option will be useful.
My Requirements:
Single dashboard for the current sprint to have transparency to
everyone in the team. No context switching.
Single backlog for all projects.
User stories & bug will be easily identified by project.
Reports by projects, teams, etc.
Service hooks - Microsoft teams, etc.
Source control - GIT.
Artifacts.
Test plans under one board.
I'm thinking of going with single project(multiple repositories)
But before going down this road I just want to know what are the pros and cons of both options.
In general, we recommend that you use a single project to support your organization or enterprise. A single project minimizes the maintenance of administrative tasks and supports the most optimized / full-flexibility cross-link object experience.
Even if you have many teams working on hundreds of different applications and software projects, you can most easily manage them within a single project. A project serves to isolate data stored within it. You can't easily move data from one project to another. When you move data from one project to another, you typically lose the history associated with that data.
So according to your situation, it is recommended to use a single project with multiple repos and multiple teams. For details you can refer to this official document.
Reasons to add another project
You may want to add another project in following instances:
To prohibit or manage access to the information contained within a
project to select groups
To support custom work tracking processes for specific business units
within your organization
To support entirely separate business units that have their own
administrative policies and administrators
To support testing customization activities or adding extensions
before rolling out changes to the working project
To support an Open Source Software (OSS) project
I am about to start a project for which we will use Azure Boards to track progress of our work items in Kanban-style. Would like to ask a high level question as I am a beginner in Azure boards and have to make a decision on how to set up 11 Kanban boards.
We have decided it makes sense to have 11 boards, one for each category of product in our company. A few pointers:
There will be a single team working through the work items in the eleven boards
There will be moments where the team will be working simultaneously with more than one board
The eleven boards should contain the same team members / columns, as the workflow is exactly the same across those 11 boards
My question: should we create 11 different projects OR 11 teams within a project to get our eleven boards? What kind of rationale would make me want to create different projects as opposed to different teams?
Thank you
When to add another project
In general, we recommend that you use a single project to support your organization or enterprise. A single project minimizes the maintenance of administrative tasks and supports the most optimized / full-flexibility cross-link object experience.
Even if you have many teams working on hundreds of different applications and software projects, you can most easily manage them within a single project. A project serves to isolate data stored within it. You can't easily move data from one project to another. When you move data from one project to another, you typically lose the history associated with that data.
Reasons to add another project:
You may want to add another project in following instances:
To prohibit or manage access to the information contained within a
project to select groups
To support custom work tracking processes for specific business units
within your organization
To support entirely separate business units that have their own
administrative policies and administrators
To support testing customization activities or adding extensions
before rolling out changes to the working project
To support an Open Source Software (OSS) project
If the above conditions are not met, we generally recommend that you create multiple teams in a project. Here is the official document you can refer to.
Yes I can see what is currently in the sprint, but how can I tell what was originally planned in a sprint?
I would like to be able to query this for a chart on my dashboard. Additionally, I want to be able to pass this information over to Power Bi via Analytics View.
Usually, we create product backlog to correspond to your project plan, the roadmap for what your team plans to deliver. You create your product backlog by adding Issues (Basic process), User Stories (Agile), Product Backlog Items (Scrum), Requirements (CMMI).
Your backlog consists of a list of work items. You use work items to share information, assign work to team members, track dependencies, organize work, and more.
If you want to track your project plan, you should query your product backlog.
https://learn.microsoft.com/en-us/azure/devops/report/powerbi/create-quick-report?view=azure-devops
I'd like to avoid for the stakeholders to view the name of developers working on tasks (Assigned To columns).
Is there a way to hide it?
Unfortunately, there isn't a permission model for fields in a Process Template, so it isn't possible to hide the field only for certain users.
There are a few places in the user-interface where you can customize the view. For example, you can customize the settings for the Kanban Board to pick and choose which fields are displayed:
And while you can remove Columns from lists, this is only a band-aid workaround as the information is still available and columns can easily be added back in for personal views.
In an agile world, we want our stakeholders to have visibility. Microsoft's view of DevOps is "people and process working with tools to deliver value to customers". Stakeholders have a role in your project, but their contributions aren't the same as those that are doing the work. The classic example is Ham and Eggs
If your concerns are truly about privacy - don't give Stakeholders access! Consider finding an alternate method of keeping them in the loop. For example, Azure DevOps allows you to query their system via an Excel Plugin.
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.