Multiple teams wanting Kanban board visibility

[Heather_Kulbacki]

We started using Kanban boards in Workfront earlier this year for our creative teams. There was some learning curves involved but overall things are running relatively smoothly now, not perfect, but making progress. But now we have other teams wanting their own Kanban boards and some want visibility throughout the entire process whether their team is the one actively working on the item or not. And we're struggling to provide that overall visibility. For example, we have one team who submits tactics to our creative team, but once the creative is complete, the files go back to the original team to actually launch. That same team also launches tactics that come through our creative team from another division. In both situations there is planning that this team should be involved with prior to any creative work. Future state we plan on issues being created prior to or in sync with the planning that should happening. But this team wants all those issues on their Kanban board so they can see everything that will come to them for launch eventually. But the other division also wants the issues that they submit on their own Kanban board along with all their other tactics that do NOT involve this team so they can see all of their stuff in one place. To top it all off, when those issues come to our creative team, some of those issues get assigned to a project manager team rather than an individual project manager (depending on the size of the campaign the tactic is a part of). But I can only assign each issue to 1 team at a time - so I can't add 1 issue to both this team's board and the other divisions board at the same time, and if it needs to go to a project manager team, both of those other sets of people will lose it off their board. For our creative team's board, the issues are converted to a project and there is a task assigned to the appropriate creative team and that task moves across the creative board. Anyone else struggling with Kanban board visibility among multiple teams?

[DarrenHa]

When you're talking about handing things off to different groups of people, I think maybe the best thing to do is to create an ad hoc team that is specific to certain types of projects. You would create a kanban board that allows for people of all parts of those projects to be involved rather than your normal silos. That way, you could actually build a kanban workflow that includes all the teams in one area rather than jumping around to different team boards. For example, we have a "team" called Process Improvement. There's no employee here that has the job title for that. It's a mishmash of different people from different groups that work together for a specific type of project. Once we all agreed upon a process for Process Improvement requests, we added everyone involved into one custom workflow, then also made a report that emailed monthly to each person in case they forgot they were also on Process Improvement. Works pretty well. Darren Harper Arvest Bank Group Inc