TFS 2010 上的 Conchango 与 MS 敏捷模板

发布于 2024-08-19 13:04:58 字数 1436 浏览 4 评论 0原文

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(5

狼性发作 2024-08-26 13:04:58

我刚刚写了一篇博客,为您提供了以下版本之间的并排比较:

  • Scrum for Team System v3
  • MSF Agile v5
  • TFS Scrum v1 (beta)

http ://consultingblogs.emc.com/crispinparker/archive/2010/06/28/scrum-for-team-system-v3-0-msf-agile-v5-0-and-team-foundation-server-scrum-v1 -0-beta.aspx

Crispin。

I have just written a blog that gives you a side by side comparison between:

  • Scrum for Team System v3
  • MSF Agile v5
  • TFS Scrum v1 (beta)

http://consultingblogs.emc.com/crispinparker/archive/2010/06/28/scrum-for-team-system-v3-0-msf-agile-v5-0-and-team-foundation-server-scrum-v1-0-beta.aspx

Crispin.

画中仙 2024-08-26 13:04:58

不确定具体的差异,但我记得 Adam Cogan 的 dnrTV 节目中提到了这些,内容非常丰富。

Not sure on the precise differences, but I remember these were mentioned in dnrTV shows with Adam Cogan which were quite informative.

累赘 2024-08-26 13:04:58

我们正在尝试做出相同的决定并对两者进行测试。目前,我们倾向于团队系统模板 Scurm。这主要是因为我们现在使用 v2.2 并且已经习惯了术语和流程。

此外,SfTS Web 服务还可以自动执行许多任务,例如计算 ROI 和剩余工作。我还没有在 MSF for Agile 中看到任何证据。我知道我们可以自己编写,但 EMC 做得很好,不需要重新发明轮子。

MSF for Agile 模板有一些不错的新报告,但我猜我可以获取 rdls 并使它们适用于 SfTS 模板。

我建议获取

We are trying to make the same decision and testing both. Right now, we are leaning towards the Scurm for Team System Template. This is primarily because we are using v2.2 now and have become accustomed to the terminology and process.

Also, the SfTS web services automate many tasks such as calculating ROI and work remaining. I haven't seen any evidence of that with MSF for Agile. I know that we could write our own, but EMC did a fine job of it and there is no need to re-invent the wheel.

The MSF for Agile template has some nice new reports, but I'm guessing that I can grab the rdls and make them work for SfTS template.

I'd recommend getting one of the Virtual PC images of 2010 beta 2 that MS has made available. It already has a project in there with the MSF Agile template and work items entered. You can add the SfTS template and try both out.

流年里的时光 2024-08-26 13:04:58

我们在 TFS 2008 中使用了 Conchango 的 SfTS 模板;他们的 v3 模板看起来相当不错,但 Microsoft 的 Agile 模板具有一些很棒的报告功能,并且他们的计划电子表格看起来也非常方便 - 我发现使用 SfTS 进行冲刺计划很痛苦。

我认为从一个模板转换到另一个模板将是一项痛苦的工作;请注意,我们已经定制了 SfTS 模板,因此升级也不是一件容易的事。

我已经在带有 MS 模板的虚拟机上运行了 TFS2010,但我还没有尝试过 SfTS v3 模板。但我注意到的一些事情是:

  • MS 的任务(SfTS 中的 Sprint Backlog 项目)比 SfTS 中的简单 - 它们只有两种状态:“活动”和“完成”。关于何时在状态之间移动 SBI,我们进行了各种毫无意义的争论(更糟糕的是,只授予某些用户组在状态之间转换的权限),因此我完全可以看到 Microsoft 的方法令人耳目一新。
  • MS没有SfTS的Sprint工作项(用于定义开始/结束日期和容量);我还没有弄清楚如何在 MS 中执行此操作,虽然我认为这与 Excel 规划工具有关,但我不太喜欢首先设置迭代路径,然后设置 Sprint 工作项等
  • MS报告很棒;在我看来,SfTS 的报告明显不那么重要,而且其中一些报告从未对我们正常工作过。 Conchango 论坛不是最好的,反馈到达的速度可能相当慢。
  • 将测试(自动或其他方式)链接到 MS 中的测试用例的能力真是棒极了,我不知道 SfTS 是否支持它们。如果不是,我怀疑这可能是我团队的动因。

我一两个月前在 Conchango 论坛上问过这个问题,但除了一些模仿的问题外,Conchango 没有任何回应 - 你可能会认为他们想要真正发挥其模板的优势。

We've used Conchango's SfTS template for TFS 2008; their v3 template looks pretty good, but Microsoft's Agile template has some awesome reporting capabilities, and their planning spreadsheets look very handy as well - I found that sprint planning using SfTS was painful.

I would imagine that transitioning from one template to another would be a painful exercise; mind you, we've customised the SfTS template, so the upgrade won't be a walk in the park either.

I've got TFS2010 running on a VM with the MS template, I haven't tried the SfTS v3 template yet. A couple of things I've noticed though are:

  • MS's Tasks (Sprint Backlog Items in SfTS) are simpler than in SfTS - they only have two states, of Active and Done. We've had all sorts of pointless arguments over when to move an SBI between states (even worse, giving only certain user groups permissions to transition between states), so I could quite see Microsoft's approach being a breath of fresh air.
  • MS doesn't have SfTS's Sprint workitem (which is used to define start/end dates and capacity); I haven't figured out yet how to do this in MS, although I think it's related to the Excel planning tools, but I'm not a big fan of having to set up the Iteration Path first, then the Sprint workitem etc
  • The MS reports are awesome; the SfTS reports markedly less so, IMO, and some of them never worked properly for us. The Conchango forum is not the best, feedback can be quite slow in arriving.
  • The ability to link tests (automated or otherwise) to Test Cases in MS is double-plus awesome, I don't know if SfTS supports them or not. If not, I suspect this could be what swings it for my team.

I asked this question on the Conchango forum a month or two ago, but apart from a few me-too questions, there's been no response from Conchango - you'd think that they would want to really push the advantages of their template.

想你的星星会说话 2024-08-26 13:04:58

我们为所有项目选择了 Scrum 模板 - 主要原因:

  1. 它自动总结从任务到用户故事(产品积压项目)的剩余时间等
  2. 它为冲刺燃尽图预先构建了报告
  3. 它保存了有关冲刺和开始结束的信息冲刺的日期作为 TFS 中的工作项 - 不仅在 Excel 中(与敏捷模板一样)
  4. 它还有一个 Scrum 仪表板(到目前为止还处于测试阶段 - 但很有前途)

它有一些缺点:
1. 没有内置的完成时间,这很奇怪 - 但很容易添加自己
2.没有资源规划(敏捷模板Excel中有这个)
3. 工作流、团队冲刺的配置对我们来说太复杂 - 我们宁愿他们能提供

We have chosen the Scrum template for all our projects - main reasons:

  1. It automatically summarize hours remaining etc from tasks to user story (product backlog item)
  2. It has pre-built reports for sprint burndown charts
  3. It saves the information regarding sprints and start-end dates for sprints as workitems in TFS - not only in Excel (as with Agile template)
  4. It has a Scrum Dashboard (very beta so far - but promising)

It has some drawbacks:
1. No built in Completed Hours which is rather strange - it is however easy to add yourself
2. No resource planning (the agile template has this in Excel)
3. The configuration with Workstreams, Team sprints is too complicated for us - we would rather if they could offer

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文