I'm working on a team with 1 week sprints. We have a feature that provides a status indicator for a long running job processing up to thousands of files. There will be some development work to obtain the status of each file.
The product owner wants a graphical spinner showing progress of each file as it is processed.
The entire story was estimated to take almost all of one developer's time for the sprint.
Some people want the entire story to be one card and to eliminate the graphical spinner mid-sprint if it becomes too time-consuming to finish by the end of the week. Other people want two cards. One card covers the gathering of the status. The second card covers the graphical spinner.
I've always thought it made sense to keep cards as small as possible in order to avoid changing requirements mid-sprint.
Is it appropriate to split this story into two cards or is it better to keep it as one?