如何编写用户案例以获得技术实施细节？ [英] How to write User Stories for technical implementation details?
问题描述
我正在尝试以一种更有条理的方式工作，并开始采用用户故事。
I'm trying to work in a more organised way and started adopting user stories.
我认为我对如何将用户故事用于技术性东西有误解。
I think I have misunderstanding of how should I use user stories for technical stuff.
比方说，我正在编写一个应用程序，该应用程序可以为我提供针对某个Google关键字的网站排名。
Let's say I'm coding an app that gives me the ranking of my site for a certain Keyword in Google.
用户故事是这样的：
作为互联网营销商
，我想找出哪里我的网站为关键字排名
所以我会知道我的SEO工作是否有效
As an Internet Marketer
I want to find out where my website ranks for a keyword
So I'll know whether my SEO efforts work
现在这很漂亮直率和以用户为中心...但是，如果我需要将Proxies引入循环，会发生什么情况。
Now this is pretty straight forward and user centric... However, what happens if I need to introduce Proxies into the loop.
一方面，Proxies是技术实现的详细信息，代理是Internet Marketer域名的一部分。
On one hand, Proxies are technical implementation detail on the other hand, proxies is part of the Internet Marketer's domain.
我应该如何制作这样的故事？
How should I craft such story?
作为互联网营销商
我想在G中搜索时使用代理oogle
因此，我们将能够在没有Google阻止我们的情况下检查很多关键字
As an Internet Marketer
I want to use Proxies when searching in Google
So we'll be able to check a lot of keywords without Google blocking us
上述情况听起来不适合我...也许我可以将其重写为：
The above scenario doesn't sound right for me... Maybe I can rewrite it to be something like:
作为互联网营销商
我希望能够一次检查很多关键字
这样可以节省我的时间
As an Internet Marketer
I want to be able to check a lot of Keywords at a time
So it'll save me time
这听起来更正确，但是我可以给出什么接受标准？尝试在一分钟内抓取Google 100次？
This sounds more right, however what acceptance criteria can I give it? try scraping google 100 times in a min? Isn't it waste of time?
这是另一种情况。当我要实现的功能是可以在30秒内使用一次代理时，应该如何设计用户故事？我不知道如何从以用户为中心的角度解决这个问题...
Here's another scenario. How should I craft a user story when the feature I want to implement is that a proxy can be used once in 30 seconds? I don't have any idea of how to approach this problem from a user centric perspective...
我想做的另一件事是提出另一个角色。我可以说我们没有扮演 Google Scraper 角色，而不是围绕 Internet Marketer 。我可以说 Internet Marketer 与 Google Scraper 有关。
Another thing I thought of doing is to present another Role. Instead of being centered around Internet Marketer, I can say we have a role called Google Scraper. I can say that Internet Marketer is in relation with Google Scraper.
现在，我可以写一个用户故事，例如：
Now I can write a user story like:
作为Google Scraper
我想更改代理每次搜索
所以Google不会禁止我
As Google Scraper
I want to change proxies every Search
So Google won't ban me
您如何看待上述技术实施细节？它还可以帮助将系统分解为模块...
What would you say about approaching technical implementation details like above? It can also help breaking the system down into modules...
推荐答案
您不会写技术故事。用户故事应符合投资标准。
You don't write technical stories. User stories should meet the INVEST criteria.
代理听起来确实像是一个实现细节，应避免使用。您不应在故事中提及代理服务器。即使它们是域的一部分，也可能存在其他方法来实现相同的效果。
Proxies do sound like an implementation detail and should be avoided. You should not be mentioning proxy servers in your story. Even if they are part of the domain, there are potentially other ways to achieve the same effect.
与其写我想使用代理服务器，这样我就不会被阻止，而应该写：我想掩饰我的身份，以便我不会被封锁。如果我是您的客户，我不知道您为什么想要代理？它是转发，开放还是反向代理？有用于代理服务器的负载。您应该选择要利用的功能。
Instead of writing "I want to use a Proxy, so that I don't get blocked", you should write, "I want to disguise my identity, so that I don't get blocked". If I was your customer, I wouldn't know why you wanted a proxy? Is it a forward, open or reverse proxy? There are loads of uses for a proxy server. You should pick the feature that you want to exploit.
但是，您不应该过多地关注完美的故事。敏捷宣言说：流程和工具上的个人和交互。
However, you shouldn't get too hung up on perfect stories. The agile manifesto says, "Individuals and interactions over processes and tools".
编写用户故事时，还应考虑3 C：卡片，对话，确认。客户和您是否都了解故事的含义？
When writing a user story, you should also consider the 3 C's: Card, Conversation, Confirmation. Do both the customer and you understand the meaning of the story?
卡是否符合INVEST标准？如果您对这两个问题的回答都是是，那么这个故事就很好了。
Does the card meet INVEST criteria? If you answered yes to both those questions then the story is fine.
这篇关于如何编写用户案例以获得技术实施细节？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
