I use a combination of two methods, one to track the feature requested for project by the "client", one to tracks bugs and tasks.
I used both scumworks and custom excel sheets + white board to track features and their subtasks. Hard to tell which I prefer, I adapt to my team on this. The paper gives more ownership to the team, and excel does the job for the backlog. Scrumworks is a nice a application, nice to manage backlog, display a pretty board that is very intuitive for the team, much faster for the managing stuff (ex: stats), not expensive as well.
I use devtrack, which is a bug tracking system to track everything else. I use this one but many other bugtracking system do the same. Where it becomes interesting is that we use it to track much more than bugs. In one unified system, we track small tasks and bugs, but also art asset integration, audio integration, effects integration, cutscene integration etc. The trick is to have a way to make a custom flow and then a task can travel from one department to another into the predefined order, everything get tracked, nothing is lost, and it is easy for the people because it is centralized. I like devtrack because of the easy user interface, and the control we have over the flow, transition, access, the ability to link tasks into hierarchy. I heard it is quite expensive, but look out for those qualities when choosing a tracking system.
The most important thing is to be able to adapt your tracking method and not get stuck with one when things change. I use a combination of tool, but this change along the project, in the beginning of a project I use almost exclusively agile tracking type, but when closing on to the end, a database with good tracking becomes better for my team. The combination gives us the best of both world, flexibility for what needs it, and strict tracking for everything else.
It sounds like less of project management and more of release management. Personally, I'd suggest Trac or Assembla as they're both centered around the concept of tickets that you can group into Milestones. That way you can keep a handle on the dependencies without having most of the overhead of a standard PM system... and even have tickets that don't relate to any particular milestone.
发布评论
评论（4）
我使用两种方法的组合，一种是跟踪“客户”对项目请求的功能，一种是跟踪错误和任务。
我使用 scumworks 和自定义 Excel 工作表 + 白板来跟踪功能及其子任务。很难说我更喜欢哪一个，我会在这方面适应我的团队。论文赋予团队更多的所有权，而 Excel 则负责积压工作。 Scrumworks 是一个很好的应用程序，很适合管理积压工作，显示一个漂亮的面板，对于团队来说非常直观，管理内容（例如：统计数据）更快，而且也不贵。
我使用 devtrack，这是一个错误跟踪系统来跟踪其他所有内容。我使用这个，但许多其他错误跟踪系统也这样做。有趣的是，我们用它来跟踪的不仅仅是错误。在一个统一的系统中，我们跟踪小任务和错误，还跟踪艺术资产集成、音频集成、效果集成、过场动画集成等。诀窍是有一种方法来创建自定义流程，然后任务可以从一个部门转移到另一个部门。另一个进入预定义的顺序，一切都会被跟踪，不会丢失任何东西，而且对人们来说很容易，因为它是中心化的。我喜欢 devtrack，因为它有简单的用户界面，以及我们对流程、转换、访问的控制，以及将任务链接到层次结构的能力。我听说它相当昂贵，但在选择跟踪系统时要注意这些品质。
最重要的是能够适应您的跟踪方法，并且在情况发生变化时不会陷入困境。我使用了多种工具的组合，但是这种变化随着项目的进行而变化，在项目开始时我几乎完全使用敏捷跟踪类型，但是当接近结束时，具有良好跟踪功能的数据库对我的团队来说变得更好。这种结合为我们提供了两全其美的优势：满足需求的灵活性，以及对其他一切的严格跟踪。
I use a combination of two methods, one to track the feature requested for project by the "client", one to tracks bugs and tasks.
I used both scumworks and custom excel sheets + white board to track features and their subtasks. Hard to tell which I prefer, I adapt to my team on this. The paper gives more ownership to the team, and excel does the job for the backlog. Scrumworks is a nice a application, nice to manage backlog, display a pretty board that is very intuitive for the team, much faster for the managing stuff (ex: stats), not expensive as well.
I use devtrack, which is a bug tracking system to track everything else. I use this one but many other bugtracking system do the same. Where it becomes interesting is that we use it to track much more than bugs. In one unified system, we track small tasks and bugs, but also art asset integration, audio integration, effects integration, cutscene integration etc. The trick is to have a way to make a custom flow and then a task can travel from one department to another into the predefined order, everything get tracked, nothing is lost, and it is easy for the people because it is centralized. I like devtrack because of the easy user interface, and the control we have over the flow, transition, access, the ability to link tasks into hierarchy. I heard it is quite expensive, but look out for those qualities when choosing a tracking system.
The most important thing is to be able to adapt your tracking method and not get stuck with one when things change. I use a combination of tool, but this change along the project, in the beginning of a project I use almost exclusively agile tracking type, but when closing on to the end, a database with good tracking becomes better for my team. The combination gives us the best of both world, flexibility for what needs it, and strict tracking for everything else.
我们在工作场所为开发人员 PM 使用 trac，它对我们很有用。
我们还为 trac 设置了 agilo 插件。
We use trac at our workplace for developer PM, and its worked good for us.
We also set-upped the agilo plugin for trac.
听起来项目管理更少，发布管理更多。就我个人而言，我建议 Trac 或 Assembla，因为它们都以票证的概念为中心，您可以将票证分组为里程碑。这样，您就可以控制依赖关系，而无需承担标准 PM 系统的大部分开销……甚至可以拥有与任何特定里程碑无关的票证。
It sounds like less of project management and more of release management. Personally, I'd suggest Trac or Assembla as they're both centered around the concept of tickets that you can group into Milestones. That way you can keep a handle on the dependencies without having most of the overhead of a standard PM system... and even have tickets that don't relate to any particular milestone.
我们使用Redmine。我们之前使用过Trac，但发现Redmine更加直观、灵活和用户友好。
它支持轻松创建新项目，无需执行任何命令行任务，并且比 Trac 具有更稳定的更新流。
至于您与Redmine相关的问题的确切答案：
来自Redmine主页的小总结：
哦，我有没有提到将您的系统从 Trac 迁移到 Redmine 是非常简单< /a>?
We use Redmine. We have previously used Trac, but have found Redmine to be much more intuitive, flexible and user-friendly.
It supports easy creation of new projects without the need to perform any command-line tasks and has a much more steady flow of updates than Trac.
As for the exact answer to your questions related to Redmine:
A small summary from the Redmine home page:
Oh, and did I mention migrating your system from Trac to Redmine is incredibly easy?