My team is building a web application that has the following high-level user story:
As a user, I would like the ability to bulk exclude components from a given country.
The work breaks down into two distinct tasks.
- Create the web application feature that excludes components by country.
- Fetch component - country association data on a daily basis
At first, I started to break this down into two user stories. However, the second task doesn't really fit into a typical user story format. I started writing something like this:
As the system, I will parse country data from the XYZ feed.
On one hand, this task is not user-centric. On the other hand, the ability to fetch component - country data is a well defined, vertically sliced task that is independently verifiable.
What is the proper user story breakdown for this type of scenario? Is it improper to have a system focused user story?