Azure Devops allows to see PBIs and their associated tasks on sprint taskboard. But what if I want to see the associated Feature or Epic of each PBI?
Is there any way to add a column for Epic or Feature?
Not a direct answer, but I believe what you're looking for is the Boards section.
Sprint taskboard is useful for detailed viewing of specific tasks (e.g. on a daily stand-up).
Boards taskboard is useful for higher level, basically anything above tasks/bugs. Including epics, features, PBIs, etc.
The trick is to use both of these taskboards in parallel. Sprints for details, Boards for bigger picture.
Related
Azure Boards works very well for teams doing scrum. With scrum, iterations work well at task board level.
For kanban, however, the task board's need for iterations makes for kludgy setup of fake iterations.
Does any official guidance exist explaining how to do kanban with Azure Boards?
If you want to use Kanban with Azure Boards, it makes more sense to use the Backlog board instead if the task boards. The Backlog board is was more customizable and it focusses in the level that is important (assuming your backlog has the items of value). You can decompose the PBI/User story on the cards themselves by adding tasks is tests.
That way you don't need any iterations at all at the sprint level.
We're using an inherited Scrum process in MS DevOps Service and recently created a new team that combines two old teams to provide a 'one-stop-shop' experience. However, when we go to look at the Sprint Backlog or Taskboard, we don't see all the work items because we are over the 1000 item limit.
Is there a way for us or Microsoft to increase this limit?
Each backlog can display up to 10,000 work items. If your backlog exceeds this limit, then you may want to consider adding a team and moving some of the work items to the other team's backlog.
For Taskboard , you can have up to 1,000 tasks on a task board. Like backlog, you can consider adding a team and moving some work items to the other team's task board.
Currently, the work item limits are as designed . I am afraid that these limits cannot be changed. You could add your request for this feature on our UserVoice site, which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps.
For detailed limits ,please refer to this document.
I'm trying to organize the work for my team in Azure Devops and have started to break down my work into the work item types provided: Epics, Features and Backlog Items. My understanding is that the Features are a collection of related stories that don't necessarily fit into a single sprint, that is they are a portfolio management thing (a folder).
When I create a Plan I can choose to display Features, but I can only have a feature assigned to a single sprint at any one time. How can I get features showing in a Plan across multiple sprints?
I'm not sure there's a "right" way to do this, but I personally would assign Features to the last sprint in which all User Stories will be delivered. Likewise I would do the same between Epics and Features.
Features and Epics are expected to be completed over multiple sprints, so the notion of using a sprint assignment to show when they're going to be "worked on" (like a User Story) is really replaced by when all components of that feature will be delivered. That's how I'm using them anyway.
If you set the start and end dates of the feature, it will span across multiple sprints.
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:
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.