I'm currently working on a project that has already defined and approved design, and my task is to write user stories based on that design. There's one situation I keep facing and can't figure out the best approach.
Here's what I struggle with: we have screens with, let's say, several features in them - for example, there's a screen "Home" which contains two sections in it, my activity with some statistics and the list of recent deals. They aren't divided into tabs or something, activity on the top of the screen, and a list of deals below it.
The question is, should I separate them into different stories? Something like a separate user story for viewing my activity, a separate story for viewing the recent deals. Maybe it should be one user story for viewing the "Home" screen and view my activity/view recent deals as acceptance criteria?
If I had no design, I would separate them (since I've no idea how they will be grouped in the end and they seem to me as different features). However, I do have a design and I can't kind of view my activity without viewing the list of deals - they are on the same screen.
We have no Scrum Master, and nobody actually cares about "separate/not separate." Maybe I'm overcomplicating things and it really doesn't matter as long as the client is satisfied with the actual results? Any suggestions would be appreciated!