Eylean Board could be a solution in this situation. Eylean board offers data slicing in visual level and in data level. Arrange by rows, columns, categories, assignments. It supports task grouping into categories which can work as different projects and may be placed into different rows of the task board. Any of these options leaves ability to apply WIP limits across the board. The app itself was built to suite kanban so you should find helpful.
Corey Ladas over at Lean Software Engineering has a few articles on how to design a Kanban board for various workflows. I also highly recommend the kanbandev mailing list - the community is pretty mature, but searching through the archives should prove useful.
For standup meetings, keep in mind that Kanban does not prescribe the standard Scrum-style standup (What did you do yesterday, what did you do today, any blockages?). These can still be useful to do with smaller groups, but with a larger team (you never mention how large - 20? 200?) you can just focus on the blockages. What people are currently working on is visible for all on the board, and the next priority (i.e. What will I do next?) should be in some sort of "Ready" queue, which is pulled from according to your different classes of service.
I believe it is impossible to have a physical or (any other) board that shows projects, teams and development flow simultaneously. Moreover, there is no software that provides good team-level visibility, almost all project management tools built on top of Project concept, and little use Team concept.
I've been thinking about this problem for 2 years and came up with a solution that we are going to implement in TargetProcess, but we are not there yet. The basic idea is to allow to filter and group work flexibly by teams or by projects to provide bird-eye view and zoom in to see details for particular project or particular team. I can't imagine how it can be done on physical kanban board.
In Agile projects, it's a common practice to visualize and share project status using charts or diagrams on boards. While no single document delivers all of the ammunition agile teams need to get the rhythm, this set of visual materials offers an easy framework to help guide software development teams through the various agile cycles.
A variation of the Kanban, an easy way to represent these cards, with some enhancements to this representation and a synchronized use of the concept, ArabiaGIS introduced the Sync Kanban concept.
The Sync Kanban is composed of a board for each project where the team leader or the responsible developer will try to represent the project status and the features progress with pies.
I'm trying to think of a simple (and agile in nature) way to visualize a large department's work and bottlenecks, with the idea of gradually improving the process once we have the necessary data.
Maybe not the expected answer but this is exactly what value stream mapping is for:
发布评论
评论（5）
Eylean Board 可能是这种情况的解决方案。 Eylean board提供视觉层面和数据层面的数据切片。按行、列、类别、作业排列。它支持将任务分组为类别，这些类别可以作为不同的项目工作，并且可以放置在任务板的不同行中。这些选项中的任何一个都可以全面应用 WIP 限制。该应用程序本身是为了适应看板而构建的，因此您应该会发现很有帮助。
Eylean Board could be a solution in this situation. Eylean board offers data slicing in visual level and in data level. Arrange by rows, columns, categories, assignments. It supports task grouping into categories which can work as different projects and may be placed into different rows of the task board. Any of these options leaves ability to apply WIP limits across the board. The app itself was built to suite kanban so you should find helpful.
Corey Ladas 在 精益软件工程 上发表了几篇关于如何为各种工作流程设计看板的文章。我还强烈推荐 kanbandev 邮件列表 - 社区相当成熟，但搜索通过档案应该证明是有用的。
对于站立会议，请记住看板并没有规定标准的 Scrum 风格的站立会议（你昨天做了什么，今天做了什么，有什么障碍吗？）。这些对于较小的团队仍然有用，但对于较大的团队（你从来没有提到有多大 - 20？200？），你可以只关注障碍。人们当前正在做的事情对板上的所有人都是可见的，并且下一个优先级（即我接下来要做什么？）应该位于某种“就绪”队列中，该队列是根据您的不同服务类别提取的。
Corey Ladas over at Lean Software Engineering has a few articles on how to design a Kanban board for various workflows. I also highly recommend the kanbandev mailing list - the community is pretty mature, but searching through the archives should prove useful.
For standup meetings, keep in mind that Kanban does not prescribe the standard Scrum-style standup (What did you do yesterday, what did you do today, any blockages?). These can still be useful to do with smaller groups, but with a larger team (you never mention how large - 20? 200?) you can just focus on the blockages. What people are currently working on is visible for all on the board, and the next priority (i.e. What will I do next?) should be in some sort of "Ready" queue, which is pulled from according to your different classes of service.
我认为不可能有一个物理板或（任何其他）板来同时显示项目、团队和开发流程。而且，没有任何软件能够提供良好的团队级别可视性，几乎所有项目管理工具都建立在Project概念之上，而很少使用Team概念。
我已经思考这个问题两年了，并提出了一个我们将在 TargetProcess 中实现的解决方案，但我们还没有到那一步。基本思想是允许按团队或项目灵活地过滤和分组工作，以提供鸟瞰图并放大以查看特定项目或特定团队的详细信息。我无法想象如何在物理看板上完成它。
以下是一些想法。
I believe it is impossible to have a physical or (any other) board that shows projects, teams and development flow simultaneously. Moreover, there is no software that provides good team-level visibility, almost all project management tools built on top of Project concept, and little use Team concept.
I've been thinking about this problem for 2 years and came up with a solution that we are going to implement in TargetProcess, but we are not there yet. The basic idea is to allow to filter and group work flexibly by teams or by projects to provide bird-eye view and zoom in to see details for particular project or particular team. I can't imagine how it can be done on physical kanban board.
Here are some ideas.
在敏捷项目中，使用板上的图表或图表来可视化和共享项目状态是一种常见的做法。虽然没有一个文档能够提供敏捷团队掌握节奏所需的全部弹药，但这套视觉材料提供了一个简单的框架，可以帮助指导软件开发团队完成各种敏捷周期。
作为看板的一种变体，一种表示这些卡片的简单方法，通过对此表示形式的一些增强以及概念的同步使用，ArabiaGIS 引入了同步看板概念。
同步看板由每个项目的看板组成，团队领导或负责的开发人员将尝试用饼图来表示项目状态和功能进度。
完整说明：http://www.jaftalks.com/主页/展示/同步-看板-敏捷-项目-管理
In Agile projects, it's a common practice to visualize and share project status using charts or diagrams on boards. While no single document delivers all of the ammunition agile teams need to get the rhythm, this set of visual materials offers an easy framework to help guide software development teams through the various agile cycles.
A variation of the Kanban, an easy way to represent these cards, with some enhancements to this representation and a synchronized use of the concept, ArabiaGIS introduced the Sync Kanban concept.
The Sync Kanban is composed of a board for each project where the team leader or the responsible developer will try to represent the project status and the features progress with pies.
for complete description: http://www.jaftalks.com/Home/Show/Sync-Kanban-Agile-Project-Management
也许不是预期的答案，但这正是价值流映射适用于：
（来源：killen.org）
这就是你应该开始的地方。
查看 Mary Poppendieck 关于此主题的材料（例如 此演示文稿，这个，或她的书）。
Maybe not the expected answer but this is exactly what value stream mapping is for:
(source: killen.org)
And this is where you should start.
Have a look at Mary Poppendieck material on this subject (e.g. this presentation, this one, or her books).