I'm having trouble keeping my user stories for basic operations from sounding ... basic. For example, suppose I'm building a CRM to keep track of clients:
- C: As a user, I want to create a client, so I can ... keep track of my clients?
- R: As a user, I want to view my clients and their properties, so I can ... know what's going on?
- U: As a user, I want to change my clients' information, so I can ... not use outdated information?
- D: As a user, I want to delete a client, so I can ... not have old clients lying around?
It seems like there are lots of reasons to want to perform CRUD operations on your objects, the primary reason being a kind of obvious "just because" reason. I suppose I could just pick one reason. For example:
- As a user, I want view my clients and their properties, so I can sound knowledgeable when they call.
But there are many, many more reasons why I want to view my clients. It would be tedious to enumerate out every reason why I would want to look up a client, and even if I tried, I probably still wouldn't be able to think of every reason.
How do you write user stories for basic operations?