We could have used a “standard” kanban board, but ours conveys more information!
The visual representation of your architecture allows more people to be engaged in discovering the tasks that need to be done to deliver the feature.
And it allows everyone, often including non-programmers, to see and understand the scope and impact of what is to be done.
As you finish each task (whatever “finish” means for your team), either remove the task’s sticky note or mark it with a big green tick. For our house doctor board, we’ve decided that removing the stickies is best. But for software teams, I generally recommend adding big green ticks to completed tasks. This allows anyone to see how much progress you have made through the current feature, and which areas still need more work.
Sometimes the distribution of ticked and un-ticked stickies will suggest opportunities for splitting the feature and releasing a subset earlier than planned.
Hold stand-up meetings around the diagram as often as you need, and certainly whenever anything significant changes. (Some of the teams I coach have been known to hold informal stand-ups 4-5 times each day.) The architecture diagram helps facilitate and focus these discussions, and makes it much easier for everyone to contribute.
Evolving the Kanban Board
“I've been doing a lot of abstract painting lately.
Extremely abstract. No brush, no paint,
no canvas, I just think about it.”