Hello, Khabrovites. For future students of the course “System Analyst. Advanced ” prepared a translation of the article.
We also invite everyone to participate in the open webinar on the topic "How to design a REST API and not die?" ... Participants, together with an expert in the lesson, will consider the following points:
• The main advantages and features of the REST API;
• Correct division of resources in the REST API;
• Resource inheritance and abstract resources.
User stories are probably the most popular agile (agile) technique for describing product functionality: user stories are very easy to work with. But “telling” effective stories can be tricky. The following ten tips will help you create good user stories.
Audio version of the article is here.
You can download the audio version here.
1. Users first of all
, , ; . , , . , ( ).
, , - . , , . , , .
2. ,
— ( — persona). , . ; , ; . — , , , .
: : , ( « ». romanpichler.com/tools/persona-template.
3.
, . , . . : Product Owner . , .
, , , ().
4.
, . . , . , , . , , . , (user role) , .
<>
<?>,
<?>.
, , , . , , .
5.
(Epic) — , , . , . .
, . : , , .
, . , , , .
6. ,
7.
, (Acceptance Criteria). : , , . , , . , .
8.
, (story cards) . : . . -, . -, : . -, , , . , .
9.
. , . , , . , , , . Product Canvas, , , .
10.
(user experience, UX) , . , . , (story maps), , (storyboards), .
, . , , , — — - , UML.
, , , , . , . : ; , .