nus-pe-bot
commented
2 years ago Team's Response
We decided to put "activity" because the favourites could modify telegram, github or change their group status. It was intentionally left vague to be more encompassing.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I disagree with the dev teams response.
You can write user stories at various levels. High-level user stories, called epics (or themes) cover bigger functionality. You can then break down these epics to multiple user stories of normal size. (From Textbook)
As I understand, user stories are not supposed to be vague (even though it might seem encompassing as the dev team suggests). It should have rather had a different format, like an epic as mentioned above.
User stories differ from traditional requirements specifications mainly in the level of detail. User stories should only provide enough details to make a reasonably low risk estimate of how long the user story will take to implement. When the time comes to implement the user story, the developers will meet with the customer face-to-face to work out a more detailed description of the requirements. (From Textbook)
"activity" because the favourites could modify telegram, github or change their group status. (Dev Team Response)
When the dev team says "activity", there are a lot of things being tracked, and hence splitting them into respective user stories/features would be better.
Bug Description: The App is not tracking the activity of any User. The use of the phraseeasily keep track of my favourites’ activityis very vague and maybe that functionality has not been implemented.