From the course: Azure DevOps for Beginners

Kanban board basics

- [Instructor] Kanban boards have a long history. They started this paper notes and there are many teams that still use paper to plan the work on a physical board. The simple note represents the task, it can be easily moved to a column. Some teams use color as an additional signal for example, orange notes might indicate bugs. Most Kanban applications mimic the look of the physical board and cars. And it's no different for Ash reports. Here you can see each of the work items represented as a card, one of the benefits of a card is only a subset of information that's in the task. It's only the information you think is important. So if I want to, I can just show a few items on here and you can set what's shown in the card by going to settings cards fields, and then for the product backlog I can specify which fields are shown. So if I don't want to show the tags in the effort I can turn this off, and then those are taken off the card. So you can make them as simple as or complicated as you'd like. Let's go back and put those back in. So I'll go ahead and show effort, show tags and I'll also add an additional field here. So add a new field, come on State. Now the state value is shown here on the card. The second thing that you see that mimics the physical board is the columns. And you'll notice that some of these have headers on them. So like the develop header has two columns. So we're doing something in the development section and then to notify my testers, that it's ready to test I can take this card and drag it over to the Done. That means it's done with the development phase. And then when the tester is ready, the test will take it and drag it over to the Doing where they start testing and when they're done testing then it moves to the Done column. This is essentially our Backlog here. And of course we can view this as backlog by clicking on this link. And that takes us to the traditional Azure boards backlog view other details on the card itself that are useful when you're planning is how much effort it's going to take. So that's what this number is here. I go to open this task and like at the Effort, if this is considered hours this is with assume this is going to take one hour. You can quickly change that here by clicking on this dropdown and changing it to two hours or back to one like this, it's easy to add new items you noticed at the top here in the new section, there is a new item. So I pick one, I'm adding a bug or a product backlog and then I just give it a title. Call this new item 22. As soon as I enter it you'll see that it fills us more details. It's on a sign. It's a priority two which is the default is pick a default area path and has picked the state of new. Let's say we approve this. Now it goes into Doing. Set this back to new and automatically goes to the new column. I put it done you noticed it moves over to the Done column. Let's take a look at one of our other teams go to the Mobile Team. The Mobile Team hasn't set up any work items yet. So this is one way to quickly add work items. Quickly add them. And then I can go in and start filling out more details. So that's the basics of the Kanban board. There's more to learn. We can customize the way the board itself looks.

Contents