i run a digital agency and we are using Kanban to work with our clients. We are offering different services (so we have different departments) like SEO, PPC, Conversion Rate Optmization.
In the past we used one kanban board per project/service for each client.
That means 1 client might had 4-5 different boards.
We cut it down and put the whole team into one kanban board and shared it with the client (much better).
Anyhow, my problem is now to understand the workload/planning. Like that’s still an issue for me and when i think about us as an agency i think effective and speed is one key element for our success.
SO (finally) i have something i would like to do and apply in asana. Only thing is…i don’t know if it’s as clever as i think it is or maybe garbage so i would love to gather some feedback from you.
1. I open one Kanban Board for each Team in the company
Conversion Rate Optimization/UX gets one Kanban Board, SEO Team one, Campaign Management one, Creative Production gets one etc.
Those have the columns: Backlog, WiP (work in progress), Review (internal), Review (client) Done
2. I create a shared Kanban Board for each Client
Those Boards are shared between the client and us and has two columns: Requests (from client) and Backlog (the work we’ve planned)
3. When planning happens we move tickets across those boards
With the priorities in mind and all the projects/tickets we start pushing tickets to the Team Boards from point 1, into the backlog what we want to do. Then we move the stuff with what we start to the WiP (work in progress) column. When the backlog in the team board gets empty we go to the shared client boards and pull tickets from there again.
I thought that’s actually a nice, easy and fast way to running agile and seeing the actual workload of a team.
What do you think?
- Is this practical?
- What do i miss or might not see which can bring me issues?
- Should i add a strategy board per client to define the bigger picture?
- If i have this system running, how often are meetings needed?