如何管理 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 存储库中.您可以向工作项(包括 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 Docs 来跟踪您的规格，或使用 现代要求.

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屋！