Some requirements of a system are for the system itself, or for the developers, how do I write user stories for this?
For example, there are requirements for a system to:
- provide APIs so that partner apps can interactive with it, and
- the APIs should be flexible and rich enough for various apps.
I can write user story for the first one as below:
As an Partner, I want to call the APIs provided by the system so that I can build additional functionality on it.
But for the second one, I don't know how to write. It seems like more benefit to developers so that they don't need to develop a new API for a new partner.
Sorry that the example I provided is not good user stories. They are too broad or vague as many pointed out. But please pay attention to my point that how to write stories for an system internal requirement.
Two opinions I see so far from answers:
- Non user facing one need not a user story. User story is about a user.
- Non-functional requirements or system constraints can be captured as user story. The user is relevant stakeholder like system developers.
What do you think?