nus-pe-bot
commented
1 year ago Team's Response
Hi, thanks for your bug report!
However, we feel this is not a bug. Our rationale is as follows:
The number of stars allocated to any user story is meant to help us (developers) prioritize work - which tasks to complete first and which can be left to later iterations. This is exactly what we did: higher the number of stars, the more crucial it was to implement it early on.
If we were to assign stars based on just the value proposition, almost all the user stories can be considered essential since they add value to the users in some way. But that defeats the main purpose of categorising user stories, which is to allow developers to prioritize features. (Recall that we had to choose which user stories to implement in v1.2 and it is not feasible to implement all essential features of an application in 2 weeks if we decided to do everything. So, we built an MVP (Minimum Viable Product) that allows creating, deleting, listing of tasks, teams, etc. as they are more important and urgently needed features. In terms of dependencies, you need to be able to create tasks before you can assign and delegate them.
Perhaps since you're only thinking in terms of the final product and the relative importance of the user stories in that product, you aren't considering the context in which these user stories were designed and categorized in the first place, and the purpose of the user stories.
Hence, we feel that although delegating tasks is an important feature (as part of our final product and value proposition), it should not be labelled 3 stars.
Have a nice reading week ahead!
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: 
Hello!
While your reasoning makes sense and I understand that such a feature would be difficult to implement early on, at the top of your user stories table you defined 3 stars (***) as "must have" features and not features that should be completed first, as can be seen in the screenshot above.
In light of what you have said, perhaps I should rephrase my issue as saying the table is misleading in its definition of what the stars mean for each user story, since I would consider "Assign tasks to team members" as a must-have, given that it is explicitly mentioned in the value proposition as can be seen below.
As the abilty to delegate tasks is a part of the product's value proposition, it should be classified as essential (3 stars).