…product owners tend to second-guess each other. I've recently introduced Cucumber and it's been an incredibly useful framework for collaborating between developers and product owners. I'd recommend "Writing Great Specifications" by Kamil Nicieja.
……也需要良好的培训。如果你期望全公司的人都采用这个流程，就必须降低门槛，让他们容易上手。我推荐一本我自己目前正在读的书，叫《Writing Great Specifications》，作者是 Nicieja
…also need good training. If you expect people across the company to use the process, you have to make it accessible and easy for them to learn. A book I would recommend that I am working through now is Writing Great Specifications by Bicieja
要调教好 Gherkin 可不容易。我试着把《Writing Great Specifications》当作指南来用。把 specs（规范）尽量精简到 Given、When 和 Then 各一个，似乎能减少 UI 步骤。如果团队从 web app 迁移到比如 React Native，拥有与实现细节无关（agnostic）的 specs 会很方便：应该……
It can be difficult to wrangle Gherkin. I've tried to use "Writing Great Specifications" as a kind of guide. Reducing specs to (mostly) one each of Given, When, and Then seems to reduce UI steps. Having agnostic specs is nice if the team moves from web app to, say, React Native: should…
……product owner 之间往往会互相猜疑。我最近引入了 Cucumber，在开发者和 product owner 之间的协作上，它被证明是个超级好用的框架。我推荐 Kamil Nicieja 写的《Writing Great Specifications》。
…product owners tend to second-guess each other. I've recently introduced Cucumber and it's been an incredibly useful framework for collaborating between developers and product owners. I'd recommend "Writing Great Specifications" by Kamil Nicieja.
……也需要良好的培训。如果你期望全公司的人都采用这个流程，就必须降低门槛，让他们容易上手。我推荐一本我自己目前正在读的书，叫《Writing Great Specifications》，作者是 Nicieja
…also need good training. If you expect people across the company to use the process, you have to make it accessible and easy for them to learn. A book I would recommend that I am working through now is Writing Great Specifications by Bicieja
要调教好 Gherkin 可不容易。我试着把《Writing Great Specifications》当作指南来用。把 specs（规范）尽量精简到 Given、When 和 Then 各一个，似乎能减少 UI 步骤。如果团队从 web app 迁移到比如 React Native，拥有与实现细节无关（agnostic）的 specs 会很方便：应该……
It can be difficult to wrangle Gherkin. I've tried to use "Writing Great Specifications" as a kind of guide. Reducing specs to (mostly) one each of Given, When, and Then seems to reduce UI steps. Having agnostic specs is nice if the team moves from web app to, say, React Native: should…