Kanban vs. Story - visual task boards

[Connie5]

Is there a way to view project tasks, catalog items, and stories on a kanban view board?

do you need to set up your assignment groups in a way so that you have this ability?

Any best practices/suggestions to share on what your company did?

[Rahamath]

We created separate board  for Incident , Problems and  stories ..  All this boards are guided boards ..  Each team can build their own VTB and   share with the other as well. 

Thanks

Rahamath

[chrisyork]

Hello Connie,

I totally feel your pain here. I have been struggling with this myself. Many teams have a regular 'stand up' meeting to go through each team members work. Often this work involves several types of ServiceNow tasks. For example, project tasks, catalog tasks (you mentioned catalog items in your description so I am assuming this is what you mean), and stories or scrum tasks (depending on the level of detail your scrum process is using).

The short answer is yes, you can create a Visual Task Board (kanban board) for displaying all of these tasks. Each one is extended from the Task table and therefore you can create a Data-Driven VTB to show all of these tasks. You will need to create a filter to show only those Task types that you wish to see.

The challenge with this board is going to be the State values. Assuming that you set up the board so the lanes are defined by the States, you will notice that when the board is first created, you will see a lane for every possible state on all task table extensions. you will have a lot of columns shown. You can hide the columns that are irrelevant, but you may have columns that appear redundant based on the value for each column. For example, you may see a Testing column and a Testing/QA column. Your challenge is going to be trying to find common state values across the various task types that you are showing.

-Chris

[chrisyork]

I was reviewing the London release notes and found this gem:

ServiceNow® Agile Development — Unified Backlog is a new application in the London release.

Agile Development — Unified Backlog helps to maintain a centralized backlog containing records of different task types, such as defects, problems, incident tasks, and stories https://docs.servicenow.com/bundle/london-release-notes/page/release-notes/business-management/agiledevelopment-unifiedbacklog.html

[John W5]

Yes Chris, you are correct . . . but if you read the content more closely, it "almost" appears that the Triage Board (plugin) that you create for each of the different entity types (e.g. incident, defect, problem, and story) is going to show you "ALL" entries whether they belong to you and your team or not(?)    I am in the process of checking this out in my London developer instance to confirm this.   BUT currently, that is what I am seeing . . . all other entries for other components / modules that have nothing to do with Agile Development 2.0 module work.