In agile dev, how do you organize user stories?

Question

How are you going to organize user stories?

I did this for a web application:

Created a title for a web page, such as "index", and then listed all the stores that the user can do on this page.

I continued to work for all pages.

Is this the most effective way?

Answer 1

I personally like the stories and tasks of BDD style users. Typically, under BDD / Agile, you will create user stories in a planning meeting in the following lines:

As a [role] I need [capability] so that [desired outcome].

, , ( Agile, ). , , //:

:
: -
: ​​
:
:

, "" BDD, , , , . ( , xUnit.NET, . .)

, . , " - " xyz ". a, b c". - -. : " , , , , ". , ( , ... , ):

:
:
. - ,
. , , ,
: - , ,

. , .. , , .

:
: ,
: StoreResultDetail
:
: StoreResultDetail
: StoreResultDetail
: StoreResultDetail URL- -
: StoreResultDetail URL- -

, .

, , , ( BDD) QA , .

Answer 2

"-" - , . "" - , , " persona" .

Answer 3

Use Cases. :

Create New Customer Account
Assign User Rights
Receive Order
Accept Payment

. - , - . . , .. , . , , (, , ).

-.

Use Case:

Answer 4

, . . - .

. , , , , , .

, , , " ". , , - .

Answer 5

We group them by function - or better - Minimum Market Function (MMF) to add value to the product. Indeed, for example, there is no way to show something that cannot be created, or to create something that cannot yet be seen. Therefore, we group the creation / mapping so that they are delivered together. Updates and deletions may appear later, YMMV.