Remember that Tracker is a story-based planning tool, not a task-based planning tool. From the standpoint of the customer, it doesn't matter if the story impacts the photo viewer, the notification service or both. The customer has some stories (high-level requirements) they would like to have implemented, they have estimates about the cost of the stories, and they have the ability to prioritize the stories. Breaking things into components is a task-level problem.
More importantly, breaking stories for the same product into multiple tracker projects would make it difficult for the customer to communicate how they prioritize the stories, or get a good estimate as to when stories might be completed.
We use Tracker to track our stories, and we have our own board were we track tasks. I personally think it would be useful to track both stories and tasks in Tracker, but the tool doesn't support it.
最好有一个项目来包含您的所有故事。 这样，整个团队就可以在一个地方查看项目的进展情况以及当前的优先事项。 如果你的故事足够细分，可以成为 Rein 流程中的特色，那么你就处于最佳状态了！ 归根结底，拥有一个按优先顺序排列的功能列表是任何开发团队真正需要的。 使用Tracker中的标签进行过滤。 他们工作得很好。 在我看来，将单个产品分解为多个相互依赖的项目实际上会掩盖信息，并使了解项目的真实状态变得更加困难。
It is probably best to have a single project to contain all your stories. That way, you have a single place for the entire team to see what is going on with the project and what the current priority items are. If you have your stories broken down enough that they can be the features in Rein's process, you're in great shape! At the end of the day, having a prioritized list of features is all any development team truly needs. Use the tags in Tracker for filtering. They work well. In my opinion, breaking a single product down into multiple, dependent projects actually obscures information and makes it harder to get visibility on the true state of the project.
发布评论
评论（2）
请记住，Tracker 是一个基于故事的计划工具，而不是一个基于任务的计划工具。 从客户的角度来看，故事是否影响照片查看器、通知服务或两者都无关紧要。 客户有一些他们想要实现的故事（高级需求），他们对故事的成本有估计，并且他们有能力确定故事的优先级。 将事物分解为组件是一个任务级问题。
更重要的是，将同一产品的故事分解为多个跟踪器项目将使客户难以传达他们如何对故事进行优先级排序，或者很难准确估计故事何时可以完成。
我们使用 Tracker 来跟踪我们的故事，并且我们有自己的板来跟踪任务。 我个人认为在 Tracker 中跟踪故事和任务会很有用，但该工具不支持它。
Remember that Tracker is a story-based planning tool, not a task-based planning tool. From the standpoint of the customer, it doesn't matter if the story impacts the photo viewer, the notification service or both. The customer has some stories (high-level requirements) they would like to have implemented, they have estimates about the cost of the stories, and they have the ability to prioritize the stories. Breaking things into components is a task-level problem.
More importantly, breaking stories for the same product into multiple tracker projects would make it difficult for the customer to communicate how they prioritize the stories, or get a good estimate as to when stories might be completed.
We use Tracker to track our stories, and we have our own board were we track tasks. I personally think it would be useful to track both stories and tasks in Tracker, but the tool doesn't support it.
最好有一个项目来包含您的所有故事。 这样，整个团队就可以在一个地方查看项目的进展情况以及当前的优先事项。 如果你的故事足够细分，可以成为 Rein 流程中的特色，那么你就处于最佳状态了！ 归根结底，拥有一个按优先顺序排列的功能列表是任何开发团队真正需要的。 使用Tracker中的标签进行过滤。 他们工作得很好。 在我看来，将单个产品分解为多个相互依赖的项目实际上会掩盖信息，并使了解项目的真实状态变得更加困难。
It is probably best to have a single project to contain all your stories. That way, you have a single place for the entire team to see what is going on with the project and what the current priority items are. If you have your stories broken down enough that they can be the features in Rein's process, you're in great shape! At the end of the day, having a prioritized list of features is all any development team truly needs. Use the tags in Tracker for filtering. They work well. In my opinion, breaking a single product down into multiple, dependent projects actually obscures information and makes it harder to get visibility on the true state of the project.