Worth repeating: a column on your Kanban board is not "the column where [devs|testers|analysts|..] work", but "the column where people collaborate to discover information to answer questions that move the work forward".
It's about visualizing what happens to the work, not what the the workers are doing. So, design the columns of your board to represent the journey of an individual work item: what needs to happen to it as it transitions from promise to delivery.
First corollary: don't assume, for example, that a column called "Code Construction" is "the column where coding happens", and therefore "if we're coding, the ticket is in the Code Construction column". These days, we do other activities (like Validation or even Analysis, for example) by writing code. Coding can happen in any column as needed, done by the people best qualified for that.
Corollary 2: don't assume that because knowledge discovery is visualized as a sequence, this necessarily implies a "waterfall process". The board above doesn't say anything about how work is batched, how big the work items are, or how tight/loose the transition policies are. Work will move more or less sequentially through the board, and people will "move around" where they are needed.
Corollary 3: Don't assume this board is for one team. Most intellectual work needs to weave through multiple teams, groups, and departments to go from "vague" to "done". Think about the system and end-to-end services.
Commentaires