How to write user stories for technical implementation details?

I try to work in a more organized way and started using user stories.

I think I have a misunderstanding of how to use custom stories for technical materials.

Let's say I'm encoding an application that gives me the ranking of my site for a specific keyword on Google.

User history is as follows:

As an Internet marketer,
I want to find out where my site is ranked for.
Therefore, I will know if my job search efforts are working.

Now this is pretty straight forward and user oriented ... However, what happens if I need to introduce Proxies into a loop.

On the one hand, Proxies are technical implementation details, on the other hand, a proxy server is part of the Internet Marketer domain.

How do I create such a story?

As an Internet marketer,
I want to use Proxies when I search on Google.
This way we can check many keywords without blocking Google.

The above script is not suitable for me ... Perhaps I can rewrite it as something like:

As an Internet marketer,
I want to be able to check many keywords at the same time. So this will save me time.

This sounds plausible, however, what acceptance criteria can I give him? try cleaning Google 100 times per minute? Isn't that a waste of time?

. , , , , 30 ? , ...

, , - Role. , Internet Marketer, , Google Scraper. , Internet Marketer Google Scraper.

, :

Google
-
Google

, ? ...

+4
2

. INVEST.

- , . - . , .

, " , ", : " , ". , , -? , -? -. , .

. : " ".

3 C: Card, Conversation, Confirmation. , ?

INVEST? "" , .

+9

. Sprint Planing Delivery Team, . . , . 60-75% () , . , , . " " , "/" . (IDE). , , (Jira, Team Foundation Server, On-Time)

+1

All Articles