如何管理Visual Studio Team Services(TFS)上的要求(规范)? [英] How to manage requirements (specifications) on Visual Studio Team Services (TFS)?

问题描述

我正在使用本地TFS，并计划迁移到Visual Studio Team Services.但是我还有一个问题-如何正确管理(存储，编辑，跟踪)VSTS或TFS中软件项目的要求(规范)?

I'm using on-premise TFS and plan to migrate to Visual Studio Team Services. But I still have one question - How to properly manage (store, edit, track) requirements (specifications) for software project in VSTS or TFS?

什么是最佳解决方案?你用什么?

What is the best solution? What do you use?

现在，我们使用OneNote.com并将指向OneNote页面的链接添加到TFS中的PBI.但这不是很方便.

Now we use OneNote.com and add links to OneNote pages to PBI in TFS. But it's not very convenient.

推荐答案

需求管理是一个非常广泛的主题，但是当查看Team Services和TFS的功能时，您会发现它支持的重量非常轻Scrum和敏捷模板中的需求管理.如果需要进行正式的需求跟踪，那么PBI和用户故事不是捕获它们的理想方法.主要原因是，尽管这些项目在开发的时间点上是正确的，但由于其他PBI和故事引入了互补/矛盾的行为，它们变得陈旧/过时/不正确.

Requirements Management is a very broad subject, but when looking at the features of Team Services and TFS, then what you'll find is that it support very light weight requirements management in the Scrum and Agile templates. If you're required to do formal requirements tracking then PBIs and User Stories are not the ideal way to capture them. primary reason being that while these items are true at the point in time they're developed, they become stale/obsolete/incorrect as other PBIs and Stories introduce complementary/contradictory behavior.

CMMI模板更适合于正式规范，使用需求"工作项类型并进行正式变更跟踪.它仍然打算以敏捷的方式使用，但是由于它希望您跟踪和指定的所有其他功能，它往往会驱使真正的敏捷团队离开.

The CMMI template is better geared towards formal specification, using a Requirement work item type and doing formal change tracking. It's still meant to be used in an agile fashion, but it tends to drive true agile teams away due to all the extra's it wants you to track and specify.

在产品本身中，您可以使用Markdown支持并将需求存储在具有完全变更控制权的其他源代码控制存储库或Git Repo中.您可以在工作项(包括Powerpoint故事板)中添加附件，但是任何构成厚文档的内容都不属于产品的一部分.

In the product itself you could use the Markdown support and store requirements in an additional source control repository or Git Repo with full change control. You can add attachments to work items (including Powerpoint storyboards), but anything that amounts to a thick document is not part of the product.

您当然可以链接到o365，OneNote.com或Google文档来跟踪您的规范，或使用第三方产品，例如

You can of course link to o365, OneNote.com or Google Docs to track your specifications, or make use of 3rd party products such as ModernRequirements.

请记住，在敏捷开发中，我们尝试将规格保持在所需的最低限度，并且该规格主要用于确定要做什么(计划和跟踪工作).如果需要获取正式的规范，则需要另一个地方来存储它们.

Keep in mind that in Agile, we try to keep specifications to the minimum required and that it's primarily used to figure out what to do (plan and track work). If you need to capture formal specifications, you need another place to store them.

这篇关于如何管理Visual Studio Team Services(TFS)上的要求(规范)?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！