The agile phrase, if I remember correctly, is a literal translation from “User Story”.
Is the user story, as the name suggests, a legend about the customer? Funny, apparently not.
Maybe it’s some kind of western slang, or because it’s written on a card or a little sticker that makes it easier to tell a story?
Anyway, user stories in Agile development are used to describe user needs in the following format:
As a… Hope to have… So that…
There are three elements to a user story:
1. User: the user or user role of this function
2. Functional requirements
3, to achieve the purpose of the function
I think the most important thing is 3. Functional requirements put forward by users are for certain purposes. Since the user is not professional enough for us, his functional requirements may be incomplete or even unnecessary. We can recommend more appropriate functions to him by grasping his purpose.
Typically, user stories are written by product managers. But in a multi-functional team, it might be everyone.
A multi-functional team is one in which team members can perform multiple functions. For example, developers can be responsible for some testing functions, participate in requirements writing, and so on. Multi-functional, as opposed to multi-skilled, does not mean that developers should have testing expertise, for example. Do not professional work, it is auxiliary nature, aim to participate in, and do not force is the main force.