I am new to Azure DevOps and I am trying to create tasks and issues in the backlog first without appearing on the kanban board, and when tasks are ready they should appear on the kanban board. However every new task or issue I create they all appear on the kanban board. How can I prevent the tasks from automatically appearing on the Kanban board?
You can not do that because the Kanban board is equal to your Backlog. You may consider:
Using tags to mark ready work items.
Add your custom state for issues then use it on the board: https://learn.microsoft.com/en-us/azure/devops/organizations/settings/work/manage-process?view=azure-devops
Use another more complex process that contains all the needed states. As an example, Scrum:
Additionally, you can hide the New column:
Related
We have a shared work item where two teams work together.
is it possible to create a common PBI which can be visible on both the boards ?
This work item type is dependency.
Google
and
self-exploration.
To work with PBIs, a team should be an owner of these PBIs. In your case, you may just copy the current PBI and add a team-specific description. Then each team adds its own estimate and child tasks.
If you what to use one shared PBIs, that may be not so a manageable structure... Let's say the first team will be an owner and adds tasks for the second team. In this case, the first team sees the full structure in the backlog:
and only its tasks in the sprint:
The second team can find only its task in the sprint as unparented:
It depends on how the sprint/area path configuration of the teams is defined. If both team share their area path, then the PBI will show up on both boards.
Is it possible to create a Definition of Ready (DOR) board and a separate Development / Sprint Board for Defintion of Done (DOD) AND be able to transition a work item from the DOR board to the DOD board i.e. One workflow visually representing the preparation of a story(DOR) and the build of a story(DOD) but on separate boards.
DOR board columns might be: Backlog, Business Review, Technical review, Product Backlog refinement (PBR), PBR Done, Prioritised, ready for Sprint
DOD board columns might be: Sprint Backlog, Development, Code Review, Testing, Testing Done, Completed
This is very doable in Jira (Atlassian) and although lots of you tube videos that describe how to setup a project, a board, work items, epics/features/stories and how to assign to a Sprint, this all speaks to the build/delivery of work. How is the preparation of a story visualised on devops boards separate from the teams sprint boards.
I have researched a lot of articles and looked at youtube videos which don't discuss this issue
How can I add the same work item to two different sprints/sprint boards?
My scenario is given below.
I have a big team that is following a longer sprint length (1-month sprint cadence for example)) and a sub-team that is trying 1-week sprints. I have done the project and team configuration (using area paths and iterations pats etc.) such that the sub-team sees only their backlog view and the big team sees the whole backlog. I can drag the work items from either one of the backlog for either one of the teams to corresponding 1-month sprint board (for the big team) or 1-week sprint board (for the sub-team).
My question is as follows:
The bigger team wants to see all the stories as part of the month-long sprint. In other words when they have standups they want to see the sub-team's 1-week sprint stories also in their sprint board for the month-long sprint. I tried to add the same story into both month-long sprint for the big team and 1-week sprint for the sub-team. But Azure DevOps cannot keep the work item in both the sprints at the same time. It you add it to month-long sprint board, it is removed from the 1-week sprint board.
How I can have the work item be added to both the sprints? Any help is appreciated
You can set up sub-teams and sub-sprints using Azure DevOps logic, then the work items will be automatically synchronized on the backlogs of both teams.
As shown below:
"Team 2" is a sub-team of "Case0103 Team". And "Week 1" sprint is a sub-sprint of "Iteration 1".
Then in Sprints, "Case0103 Team" can view work items of "Iteration 1".
"Team 2" can only view work items of "Week 1".
Here are the detailed steps:
Create a sub-team. You can click Configure a hierarchy of teams for detailed steps.
Create sub sprints. You need to go to Project Settings -> Boards/Project configuration, then choose your sprint and click "New child".
Set iteration paths. Go to Project Settings -> Boards/Team configuration -> Iterations. Select different teams by navigation bar at the top and select or remove sprints. Team members can only see sprints shown here.
I've done something that has added Task to my project Sprint and Backlog menus.Also, Tasks appear in the Backlog, along with the User Stories to which they belong (i.e., they appear effectively twice in the Backlog). This is almost certainly down to my playing around with Tuleap in the early days of using it, but now I cannot find what I've done. I don't think it's tracker hierachy because that is the same as in another project, which doesn't have the same problem.
What have I done?
Agile Dashboard / Administration / Sprint Planning: Edit and change the multiselection against "This planning allows assignment of".
We plan to use Kanban in our DevOps project. It however looks like I still need to create Iterations (e.g. 14 days) and map the Kanban widget to show the WIP over the 14 day cycle.
So, in essence I still need to create Iterations. And a follow up understanding accordingly is that I will need to do sprint planning for the iterations. Is that the correct understanding or am I missing something?
Thanks
Two things here:
First, Kanban is mainly used to visualize the state or flow of your work. It is interactive in that you can change the state of the workitems as it progresses from one state to another. Kanban boards are not really dependent on sprint as such, but provide a cumulative flow chart for monitoring progress. It is the Taskboard that is tied to tracking the sprint tasks.
Second, the WIP limits are used to limit the number of workitems in progress, and can help identify process bottlenecks and improve the Team's efficiency. These numbers are set per stage and act as the soft constraint that can be revisited later.
And yes, you have to create the iterations and iteration dates, although they can be as per your pace, and map your Team's work flow to Kanban columns!
Additional references:
Kanban Basics
Kanban quickstart
What is Kanban?
If you want to re-evaluate your process model, give this doc a prior reading.
Hope this clarifies!
Well, Kanban cares about Flow. That requires some understanding of Queuing Theory. One aspect is for example Little´s Law. Which requires Delivery Rate. So I find it valid to ask for that metric (without iterations!) when Kanban is supposed to be supported.
Second, Kanban cares about Balance. eg between work arrival rate and work departure rate. Again it would be nice, if these metrics would be available out of the box.
(I teach Kanban courses BTW)
Something similar is required by DORA metrics: deployment frequency.
Which I assumed to be available out of the box in a product with "DevOps" in its name.