我们使用 JIRA 进行错误跟踪和发布管理，并且我们已经开始使用 greenhopper 在 JIRA 内部进行项目管理，但它缺少的一件事是用户故事与用户故事中的任务的概念。 有没有人推荐其他任务板，例如敏捷项目管理工具，完全支持用户故事和任务，并且对用户来说快速且简单。 我开始研究 targetprocess，所以如果有人对此有具体的反馈，那就太好了。
We user JIRA for bug tracking and release management and we have started using greenhopper for project management inside of JIRA but one thing that it lacks is the idea of user stories versus tasks in those users stories. Does anyone recommend other task board like agile project management tools that fully support users stories and tasks as well as being fast and simple to user. I started looking at targetprocess so if anyone has feedback on that specifically it would be great as well.
发布评论
评论（10）
TargetProcess 是我使用过的侵入性最小的项目管理工具。
TargetProcess is the least intrusive project mgmt tool I've used.
Scrum 和 XP 团队的一个常见反模式是将故事分解为任务，跟踪这些任务，并在迭代结束时注意到所有任务都已完成，但用户故事尚未完成（因为它们不仅仅是他们的任务的总和）。
我强烈建议根本不要跟踪任务。 如果你愿意的话，可以集思广益，进行估算，但一定要估算并跟踪整个故事。 如果一个故事太大，请将其分解为较小的故事 - 有时需要一些创造力，但这几乎总是可能的。
您可以使用 Jira 中的子问题将故事聚合成更大的故事，但据我所知，greenhopper 并没有很好地支持这一点。 如果您的团队位于同一地点，无论如何，我非常强烈推荐白板上的索引卡 - 如果需要的话，甚至除了 Jira 之外（这就是我们目前的工作方式）。
A common anti-pattern for Scrum and XP teams is to break stories down into tasks, track those tasks, and at the end of the iteration notice that all tasks are done, but the user stories aren't (because they are more than just the sum of their tasks).
I highly recommend not tracking tasks at all. Brainstorm them for estimation, if you like, but always estimate and track whole stories. If a story is to big, break it down into smaller stories - that sometimes takes some creativity, but it's almost always possible.
You can use sub-issues in Jira to aggregate stories into bigger stories, although this isn't very well supported by greenhopper, as far as I remember. If your team is colocated, I would very highly recommend index cards on a white board, anyway - even additionally to Jira, if you have to (that's how we currently work).
白板和便签或记事卡。
我知道您需要软件，但根据您的环境，可能很难超越公开可见的任务图表的沟通价值。
但如果您必须拥有软件，还有 Rally 和 版本一。
Whiteboard and sticky notes or note cards.
I know you asked for software, but depending on your environment it might be hard to beat the communication value of a publicly visible task chart.
But if you must have software there's also Rally and VersionOne.
我的公司已经使用 TargetProcess 一段时间了，我们对该产品非常满意。 每当我们遇到问题或错误时，我们都会向他们报告，问题或错误很快就会得到解决。 它是一个与 SCRUM 配合良好的出色工具。 我真的推荐它。
My company have been using TargetProcess for a while and we are very pleased with the product. Whenever we have experienced problems or bugs, we have reported it to them and the problem or bug is solved really fast. It's a great tool that worked well with SCRUM. I really recommend it.
Acunote 是我迄今为止发现的最好的一个。 使用起来非常简单、快捷。
Acunote is the best one I've found to-date. Really easy, simple and quick to use.
我们将 Jira 与 GreenHopper 一起使用没有任何问题。 如果您可以控制 Jira 实例的配置，则可以轻松创建允许具有子任务的故事问题类型。 在规划阶段，我们将故事放到下一个版本中，并将它们分成子任务，以更精确的时间进行估计并分配给团队成员。 如果这些任务是独立的，您还可以将它们转换为特定故事的子任务。
We use Jira with GreenHopper with no problems. If you have control over the configuration of your Jira instance, you can easily create a story issue type that allows having sub-tasks. During the planning phase, we drop the stories onto the next version, and split them into sub-tasks, estimated in more precise time and assigned to team members. If those tasks are separate you can also convert them into sub-tasks of a specific story.
Thoughtworks 很乐意向您出售Mingle
Thoughtworks would be happy to sell you Mingle
看看 http://AgileZen.com/
Take a look at http://AgileZen.com/
看看爵士乐： http://www.theserverside.com/news/ thread.tss?thread_id=44577, http://jazz.net/pub/index. jsp
take a look at jazz: http://www.theserverside.com/news/thread.tss?thread_id=44577, http://jazz.net/pub/index.jsp
我们刚刚发布了一个名为 Crew 的全新工具，它可能适合您。 它非常灵活，允许您设置适合您流程的项目结构和工作流程。
http://www.devmynd.com/crew
We've just released a brand-new tool called Crew which might work for you. It's very flexible and allows you to set up a project structure and workflow that fits your process.
http://www.devmynd.com/crew