riccqi / pe

1 stars 0 forks source link

Confusing/duplicate user stories for updating supplies #17

Open riccqi opened 1 year ago

riccqi commented 1 year ago

Refer to the first and third items in the screenshot, I think they are trying to say the same user story of wanting to update their supplies. They can thus be merged into a single user story of: "increment or decrement the supplies" so that I can "keep track of the supplies I have"

Having them as separate stories with different wording can potentially confuse readers as to whether they are referring to the same feature.

Screenshot 2022-11-11 at 5.34.22 PM.png

nus-pe-bot commented 1 year ago

Team's Response

Creating user stories are for brainstorming purposes. There are many ways to brainstorm for example, what you have said to consolidate into just one user story "increment or decrement the supplies" so that I can "keep track of the supplies I have". This are called epics or themes inside the CS2103T textbook as shown.

image.png

However, this is not the only way to create user stories, as shown in the text book you can breakdown these use stories into smaller user stories. Furthermore, breaking them down into smaller will not confuse users instead it will make it clearer.

As you have stated "I think they are trying to say the same user story of wanting to update their supplies." updating supplies can be done in many ways. Increment till it is updated, decrement till it is updated and just stating the updated amount. Hence I feel, splitting the user stories makes it clearer to the user. And there are no one correct way to brainstorm for ideas as long it is clear.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: I don't agree that merging them will make it an 'epic', as they are clearly the same low level functionality. The example you gave is considered an epic since its a high level feature. This isn't quite like that. I would definitely consider the incrementing and decrementing of inventory to be a single functionality, because the end goal of both is just to update the inventory number. I do not see that splitting incrementing and decrementing will make it any clearer to the reader, and instead just makes the DG more disorganised.