Kanban & architecture

Just paused for a minute with a fresh cup of coffee and wandered off towards architecture in my mind.


Can Kanban be used by an architecture team? I tend to believe so even though I haven’t had a chance to prove the theory in practice (would be interesting though to hear anyone who has). Working with architecture has a very service-oriented side to it and tends to be somewhat interrupt driven. Additionally in large organizations it is easy to swamp the architecture team with work and as the stack in the inbox gets higher the focus and completion rate decline. Additionally other tasks, part of the normal process, are chunked in so big pieces that it is very easy to lose track of the target.

With Kanban you could get a tool to prioritize between the “service jobs” and “normal tasks”. Additionally you would have to create more tangible chunks of work which give you a sense of progress.

And if you still fail and are just drenched in work the Kanban-board would be a good visualization of just how much you and your team are trying to do… or maybe you are doing things you shouldn't?

Would be interesting to try at some point.