稍后注意：如果您选择 Scrum For Team System 模板，那么我强烈建议您阅读流程指南。 在我们坐下来阅读之前，我们必须通过艰难的方式弄清楚一些事情。 特别是关于如何处理缺陷（即何时是错误以及何时是返回“进行中”的 Sprint Back 日志项）
We use Scrum For Team System and love it. It really does a good job of merging the TFS and Scrum processes.
We also got the task board (the part you have to pay for) and really like that too.
Even with Scrum for Team System, TFS via visual studio is not good for planning meetings (though it is ok for standups) The task board helps a lot in visualizing the work remaining and in moving it around.
Before we got the Task Board, we would use post it notes for our planning meetings and then enter them in to TFS after. And even though the Task Board is nice, if you don't have at least 2 people working on it in a planning meeting then it is not enough. We have 3 laptops going for a team of 5 + 1 (scrum master) and that works great. If you don't have that then I would still think about doing post it notes.
The task board allows you to refresh and see what the other are entering in. We have one computer hooked up to a projector so that the others can see what is happening. We all then brainstorm like we would on post it notes, but the people on laptops enter the data into TFS.
For us, it works great!
Later Note: If you do choose the Scrum For Team System template then I STRONGLY recommend that you read the Process Guidance. We had to figure out a few thing the hard way before we sat down and read it. Especially on how to handle defects (i.e. when is it a Bug and when it is a Sprint Back Log Item that goes back to "In Progress")
The templates are free. It is only the Task Board Application that cost a modest fee. You can use the templates without the Task Board although I highly recommend using it as wll. I think the biggest advantage for my team has been that the ScrumForTeamSystem tempaltes integrate into VS and provide a seamless feel with the rest of the development environment.
We love the ability to attach the PBI's to check-ins and have them show up on the Daily Build report.
If you are are missing something you need, you can fire up the VS template editortweak the templates to your liking. For us, we added a "Requested By" field and a "Testing Status" field to the PBI template.
The 2 shortcommings that annoyed us were that the "State" of the PBI's were not the same as SBI's (No Ready For Test on the PBI). We do testing/validation at the feature level and not the task level and wanted to track the PBIs status so we had to add our own custom field. The second issue was that there is no report out-of-the-box for a PBI burndown/up at the Sprint level. So you can't see how you are doing at delivering stories, only tasks. You have to make your own.
We don't really use the "Bug" template much (we ship flawless code:) ). No really, there is no such thing as a bug against work in a sprint; so the only time we record a bug is if a client finds an issue in the production code where it didn't work as advertised.
As Vaccano said, it isn't nearly as fast as a whiteboard or post-its in a meeting environment but if you get a couple people really good at using the tool and a couple of laptops you can make it work.
I evaluated several products and the simplicity and price of ScrumForTeamSystem can't be beat.
Like others have said, beware that the Conchango template handles bugs very differently. The idea that unreleased Backlog Items are bug-free is not just a suggestion; there is literally no way to track bugs affecting the current sprint's work. I found that this disadvantage outweighed the advantages.
If you are searching for an online Whiteboard you can have a look at the Scrum tool Agilo. It was build especially for distributed teams which do not have the chance to work on a "real" whiteboard. For a quick information you can have a look at this video.
VS 2010 的 3.0 版模板改变了该工具对 Scrum 进行建模的方式，以非常有效地支持多团队项目以及大型项目中的典型交互。
无论版本如何，它都是我目前在 Microsoft 环境中对 Scrum 项目的默认答案。 如前所述，任务板和（新的）ScrumMaster 工作台也非常有价值！
The 3.0 version of the template for VS 2010 changes how the tool models Scrum in ways to very effectively support multi-team projects and the typical interactions one will find in larger projects.
Regardless of version, it is currently my default answer for Scrum projects in Microsoft environments. As mentioned, the task board and the (new) ScrumMaster's workbench are incredibly valuable as well!
We build Urban Turtle that extend the Microsoft ALM platform with an intuitive Web interface and simplify your agile project management. By providing a Task Board and a planning board directly in web access you don't have to synchronize anything. The installation is a simple process. 2 minutes to install on the web access server. Nothing to setup on the client desktop.
Don't take my word for cash have a look at what Brian Harry from Microsoft said about the product :
发布评论
评论（6）
我们使用 Scrum For Team System 并且喜欢它。 它确实很好地融合了 TFS 和 Scrum 流程。
我们还得到了任务板（你必须付费的部分）并且也非常喜欢它。
即使使用 Scrum for Team System，通过 Visual Studio 进行的 TFS 也不适合规划会议（尽管对于站立会议来说还可以）。任务板在可视化剩余工作和移动工作方面有很大帮助。
在获得任务板之前，我们会在计划会议中使用便利贴，然后将其输入到 TFS 中。 尽管任务板很好，但如果在计划会议中没有至少 2 人参与其中，那么这还不够。 我们有 3 台笔记本电脑，可供 5 + 1 人（scrum master）组成的团队使用，效果很好。 如果你没有，那么我仍然会考虑做便利贴。
任务板允许您刷新并查看其他人正在输入的内容。我们将一台计算机连接到投影仪，以便其他人可以看到正在发生的事情。 然后，我们就像在便利贴上一样进行集体讨论，但人们在笔记本电脑上将数据输入到 TFS 中。
对于我们来说，效果非常好！
稍后注意：如果您选择 Scrum For Team System 模板，那么我强烈建议您阅读流程指南。 在我们坐下来阅读之前，我们必须通过艰难的方式弄清楚一些事情。 特别是关于如何处理缺陷（即何时是错误以及何时是返回“进行中”的 Sprint Back 日志项）
We use Scrum For Team System and love it. It really does a good job of merging the TFS and Scrum processes.
We also got the task board (the part you have to pay for) and really like that too.
Even with Scrum for Team System, TFS via visual studio is not good for planning meetings (though it is ok for standups) The task board helps a lot in visualizing the work remaining and in moving it around.
Before we got the Task Board, we would use post it notes for our planning meetings and then enter them in to TFS after. And even though the Task Board is nice, if you don't have at least 2 people working on it in a planning meeting then it is not enough. We have 3 laptops going for a team of 5 + 1 (scrum master) and that works great. If you don't have that then I would still think about doing post it notes.
The task board allows you to refresh and see what the other are entering in. We have one computer hooked up to a projector so that the others can see what is happening. We all then brainstorm like we would on post it notes, but the people on laptops enter the data into TFS.
For us, it works great!
Later Note: If you do choose the Scrum For Team System template then I STRONGLY recommend that you read the Process Guidance. We had to figure out a few thing the hard way before we sat down and read it. Especially on how to handle defects (i.e. when is it a Bug and when it is a Sprint Back Log Item that goes back to "In Progress")
模板是免费的。 只有任务板应用程序需要支付少量费用。 您可以在没有任务板的情况下使用模板，尽管我强烈建议将其用作 wll。 我认为对我的团队来说最大的优势是 ScrumForTeamSystem 模板集成到 VS 中并提供与开发环境的其余部分的无缝感觉。
我们喜欢将 PBI 附加到签入并让它们显示在每日构建报告中的功能。
如果您缺少所需的内容，您可以启动 VS 模板编辑器根据您的喜好调整模板。 对于我们来说，我们在 PBI 模板中添加了“请求者”字段和“测试状态”字段。
令我们烦恼的两个缺点是 PBI 的“状态”与 SBI 的“状态”不同（PBI 上没有准备好测试）。 我们在功能级别而不是任务级别进行测试/验证，并且想要跟踪 PBI 状态，因此我们必须添加自己的自定义字段。 第二个问题是，没有现成的关于 Sprint 级别的 PBI 燃尽/上升的报告。 因此，您无法看到自己在交付故事方面的表现，只能看到任务。 你必须自己做。
我们实际上并没有太多使用“Bug”模板（我们提供完美的代码:)）。 不，真的，在冲刺中不存在妨碍工作的错误。 因此，我们记录错误的唯一时间是客户在生产代码中发现问题，导致代码无法按照广告宣传的那样工作。
正如 Vaccano 所说，它的速度不如会议环境中的白板或便利贴那么快，但如果你有几个真正擅长使用该工具的人和几台笔记本电脑，你就可以让它发挥作用。
我评估了几种产品，ScrumForTeamSystem 的简单性和价格是无与伦比的。
The templates are free. It is only the Task Board Application that cost a modest fee. You can use the templates without the Task Board although I highly recommend using it as wll. I think the biggest advantage for my team has been that the ScrumForTeamSystem tempaltes integrate into VS and provide a seamless feel with the rest of the development environment.
We love the ability to attach the PBI's to check-ins and have them show up on the Daily Build report.
If you are are missing something you need, you can fire up the VS template editortweak the templates to your liking. For us, we added a "Requested By" field and a "Testing Status" field to the PBI template.
The 2 shortcommings that annoyed us were that the "State" of the PBI's were not the same as SBI's (No Ready For Test on the PBI). We do testing/validation at the feature level and not the task level and wanted to track the PBIs status so we had to add our own custom field. The second issue was that there is no report out-of-the-box for a PBI burndown/up at the Sprint level. So you can't see how you are doing at delivering stories, only tasks. You have to make your own.
We don't really use the "Bug" template much (we ship flawless code:) ). No really, there is no such thing as a bug against work in a sprint; so the only time we record a bug is if a client finds an issue in the production code where it didn't work as advertised.
As Vaccano said, it isn't nearly as fast as a whiteboard or post-its in a meeting environment but if you get a couple people really good at using the tool and a couple of laptops you can make it work.
I evaluated several products and the simplicity and price of ScrumForTeamSystem can't be beat.
正如其他人所说，请注意 Conchango 模板处理错误的方式非常不同。 未发布的待办事项列表项目没有错误的想法不仅仅是一个建议；而是一个建议。 实际上没有办法来跟踪影响当前冲刺工作的错误。 我发现这个缺点超过了优点。
Like others have said, beware that the Conchango template handles bugs very differently. The idea that unreleased Backlog Items are bug-free is not just a suggestion; there is literally no way to track bugs affecting the current sprint's work. I found that this disadvantage outweighed the advantages.
如果您正在寻找在线白板，您可以查看 Scrum 工具 Agilo。 它是专门为没有机会在“真正的”白板上工作的分布式团队而构建的。
如需快速了解信息，您可以观看此视频。
If you are searching for an online Whiteboard you can have a look at the Scrum tool Agilo. It was build especially for distributed teams which do not have the chance to work on a "real" whiteboard.
For a quick information you can have a look at this video.
VS 2010 的 3.0 版模板改变了该工具对 Scrum 进行建模的方式，以非常有效地支持多团队项目以及大型项目中的典型交互。
无论版本如何，它都是我目前在 Microsoft 环境中对 Scrum 项目的默认答案。 如前所述，任务板和（新的）ScrumMaster 工作台也非常有价值！
The 3.0 version of the template for VS 2010 changes how the tool models Scrum in ways to very effectively support multi-team projects and the typical interactions one will find in larger projects.
Regardless of version, it is currently my default answer for Scrum projects in Microsoft environments. As mentioned, the task board and the (new) ScrumMaster's workbench are incredibly valuable as well!
我们构建的 Urban Turtle 通过直观的 Web 界面扩展了 Microsoft ALM 平台，并简化了您的敏捷项目管理。 通过直接在 Web 访问中提供任务板和计划板，您无需同步任何内容。 安装过程非常简单。 在 Web 访问服务器上安装需要 2 分钟。 客户端桌面上无需设置任何内容。
不要相信我的话，看看 Microsoft 的 Brian Harry 对该产品的评价：
http://blogs.msdn.com/b/bharry/archive/2010/10/21/urban-turtle-3-5-released.aspx
查看该网站并向我发送您的反馈
urbanturtle.com
Dominic Danis
产品拥有者。
We build Urban Turtle that extend the Microsoft ALM platform with an intuitive Web interface and simplify your agile project management. By providing a Task Board and a planning board directly in web access you don't have to synchronize anything. The installation is a simple process. 2 minutes to install on the web access server. Nothing to setup on the client desktop.
Don't take my word for cash have a look at what Brian Harry from Microsoft said about the product :
http://blogs.msdn.com/b/bharry/archive/2010/10/21/urban-turtle-3-5-released.aspx
Have a look at the website and send me your feedback
urbanturtle.com
Dominic Danis
Product Owner.