0

我们的团队刚刚搬到 TFS 2015 开始一个新项目，我已经为积压项目设置了看板。

我想问的是，创建一个单独的任务板来为我们的用户故事编写（小黄瓜）规范是否有意义？这是常见的做法吗？

我想跟踪已编写的用户故事规范的编写，并确保每个规范都经过例如 QA 人员的审查。

4

1 回答 1

2

No, I'd say it's not a common practice. Fundamentally, writing the specs is a task that's part of the acceptance criteria of your story.

Some options:

  • Put a column in your backlog for "Spec Review" so that you can ensure that the story passes through spec review as part of moving from "committed" to "done". Have a task (or several tasks) for writing the specs and ensuring they pass. If the task is still open, the spec isn't written.

  • For each user story, make a task for writing the Gherkin specifications. If you're using Git, you can then have your specifications committed to a branch with a branch policy requiring the opening of a pull request to merge the specs into trunk, with a required review prior to the merge being allowed.

于 2015-08-01T01:38:08.823 回答