search

gavin331 / pe

0 stars 0 forks source link

User stories are quite general #8

Open gavin331 opened 2 months ago

gavin331 commented 2 months ago

image.png

The user stories are quite general and can be broken down into more specific parts. For example, there is the Group function in the app but it is not mentioned in the user stories.

nus-se-bot commented 2 months ago

Team's Response

The user story does not need to include all the features. We only include the most essential (must-have) features of our application.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: The team responded by saying that "We only include the most essential (must-have) features of our application.". This is wrong because under their user stories header, high (must have) priority is labeled using "*". However, in their actual user stories, none of them have this priority high label (They are all labeled as "").

image.png

Now, to address why I think that their user stories are too general, user stories are meant to capture user requirements in a way that is convenient for scoping, estimation and scheduling.

Scoping: which features to include in the product Estimation: how much effort each feature will take Scheduling: when to deliver each feature

Since their user stories are so general, it will not help much in these 3 aspects.

image.png

Instead, I think what they should have done is to create epic user stories and then break down from there.

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [x] I disagree **Reason for disagreement:** This is not purely a cosmetic issue because it can affect the usage since it reduces the convenience for scoping, estimation and scheduling.