Agilefant is an open-source tool that "brings together the perspectives of long-term product and release planning and project portfolio management", and is being actively developed. I would try the 2.0-alpha release (accessible via the Downloads page) for improved visualization tools, but you can also try the live demo to get the idea of what Agilefant can do.
A classic consultant's technique... I would start by plotting them on a 2x2 graph. Make the vertical axis the ROI, with high at the top, make the horizontal axis two partitions of incremental improvement on the left and new initiative on the right - and I bet there are some projects which are a bit of both, so maybe you have a continuum. Plot each project on those axes as a circle and make the area of the circle represent the number of man days.
Stuff in the top right is high return, new initiatives, stuff in the bottom left is low return maintenance/incremental improvements. If you do one chart for current resource deployment and another for planned resource deployment you'll get a strong feel for how you are spending your manpower.
There are many variations on this and you can choose what you want to plot where to best show your story. It is simple and powerful as a visual aid and you can get 90 circles on your chart without losing the woods for the trees.
As I understand this question the solution is highly dependent on final goal which actually is unclear in most of similar cases.
Before doing some 'kanban-like diagrams' for this case especially having in mind declared goal (I suggest it is only mean, not a goal) to re-balance work force I'd recommend to think about next points:
Every single developer's efficiency highly depends on many factors individual to current projects. There are 'refactoring-aware' people / 'support-likers' / e.t.c. So being placed in another environment ... this could change anything.
Well, doing efforts re-balance. What happens to existing team structure? Good aligned teams with proper roles of every person are VERY RARE. Does it worth to break good team for some estimation (in the sky)?
So I'd recommend (instead or in addition to project efficiency tracking) to track developers efficiency / satisfaction / team efficiency / satisfaction and try to solve how to re-balance efforts not only because of ROI but to get most from people (at least unless projects are profitable not to put ROI estimations over all). Don't ruin successful (not so but yes) project just because someone needs one developer in other bright project.
OK, this is just my general opinion but it greatly helped me during last year. Hope it will help someone too.
请阅读 Johanna Rothman 的优秀著作“管理您的项目组合”通过提供一种评估多个项目以确定优先级的方法来解决这个问题。
编辑：我忘了说我自己正在多个工作流 atm 中应用该技术。
华泰
G'day,
Have a read of Johanna Rothman's excellent book "Manage Your Project Portfolio" that addresses this very issue by providing an approach to evaluate multiple projects to determine a priority.
Edit: I forgot to say that I'm applying the technique myself across multiple work streams atm.
发布评论
评论（4）
Agilefant 是一款开源工具，“汇集了长期产品和发布规划以及项目组合的观点管理”，并正在积极发展。我会尝试 2.0-alpha 版本（可通过 下载 页面访问）改进的可视化工具，但您也可以尝试现场演示以了解 Agilefant 的功能。
Agilefant is an open-source tool that "brings together the perspectives of long-term product and release planning and project portfolio management", and is being actively developed. I would try the 2.0-alpha release (accessible via the Downloads page) for improved visualization tools, but you can also try the live demo to get the idea of what Agilefant can do.
经典顾问的技术...我首先将它们绘制在 2x2 图表上。将纵轴设为投资回报率，顶部为高，将横轴设为左侧的增量改进和右侧的新举措两个分区 - 我敢打赌有些项目两者兼而有之，所以也许您有一个连续体。将这些轴上的每个项目绘制为一个圆圈，并使圆圈的面积代表工日数。
右上角的东西是高回报、新举措，左下角的东西是低回报维护/增量改进。如果您为当前资源部署绘制一张图表，为计划的资源部署绘制另一张图表，您将对如何花费人力有一个强烈的感觉。
这有很多变化，您可以选择您想要绘制的内容，以最好地展示您的故事。它作为一种视觉辅助工具简单而强大，您可以在图表上画出 90 个圆圈，而不会只见树木。
HTH，祝你好运。
A classic consultant's technique... I would start by plotting them on a 2x2 graph. Make the vertical axis the ROI, with high at the top, make the horizontal axis two partitions of incremental improvement on the left and new initiative on the right - and I bet there are some projects which are a bit of both, so maybe you have a continuum. Plot each project on those axes as a circle and make the area of the circle represent the number of man days.
Stuff in the top right is high return, new initiatives, stuff in the bottom left is low return maintenance/incremental improvements. If you do one chart for current resource deployment and another for planned resource deployment you'll get a strong feel for how you are spending your manpower.
There are many variations on this and you can choose what you want to plot where to best show your story. It is simple and powerful as a visual aid and you can get 90 circles on your chart without losing the woods for the trees.
HTH and good luck.
据我了解，这个问题的解决方案高度依赖于最终目标，而在大多数类似情况下，最终目标实际上是不清楚的。
在为这种情况做一些“类似看板的图表”之前，特别是考虑到重新平衡劳动力的声明目标（我建议这只是平均，而不是目标），我建议考虑以下几点：
因此，我建议（而不是或除了项目效率跟踪之外）跟踪开发人员效率/满意度/团队效率/满意度，并尝试解决如何重新平衡工作的问题，不仅是因为投资回报率，而且是从人们那里获得最大收益（至少除非项目有利可图，否则不要对投资回报率进行总体估算）。不要仅仅因为有人在其他出色的项目中需要一名开发人员而毁掉成功的（不是这样，但是的）项目。
好吧，这只是我的一般意见，但它在去年给了我很大帮助。希望它也能帮助别人。
As I understand this question the solution is highly dependent on final goal which actually is unclear in most of similar cases.
Before doing some 'kanban-like diagrams' for this case especially having in mind declared goal (I suggest it is only mean, not a goal) to re-balance work force I'd recommend to think about next points:
So I'd recommend (instead or in addition to project efficiency tracking) to track developers efficiency / satisfaction / team efficiency / satisfaction and try to solve how to re-balance efforts not only because of ROI but to get most from people (at least unless projects are profitable not to put ROI estimations over all). Don't ruin successful (not so but yes) project just because someone needs one developer in other bright project.
OK, this is just my general opinion but it greatly helped me during last year. Hope it will help someone too.
您好，
请阅读 Johanna Rothman 的优秀著作“管理您的项目组合”通过提供一种评估多个项目以确定优先级的方法来解决这个问题。
编辑：我忘了说我自己正在多个工作流 atm 中应用该技术。
华泰
G'day,
Have a read of Johanna Rothman's excellent book "Manage Your Project Portfolio" that addresses this very issue by providing an approach to evaluate multiple projects to determine a priority.
Edit: I forgot to say that I'm applying the technique myself across multiple work streams atm.
HTH