nus-se-bot
commented
5 months ago Team's Response
We have defined that FinCliq is a desktop app for financial advisors in the UG.
In addition, we have included that the users are supposed to be financial advisors in the DG.
Furthermore, adding "as a user" would be redundant, as the "as a..." column would be assumed to be filled in with the role of the user anyway, and it would not add value to the table.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Hi! I agree that there were mentions of the target users being Financial Advisors (FA), but based on this screenshot, I thought that target user profile is supposed to be very specific. Hence, I used it to evaluate against the user stories that your team had. This was also why I suggested a possibility of changing the user profile, as your team can make it more specific, saying that target user profile must be a FA.
Additionally, based on lecture notes on the steps taken to brainstorm user stories, target user profile is the second step that we need to consider. Hence, I thought that it must be important to define it clearly since it sets the foundation for later steps.
Furthermore, I thought that it might at the very least be considered NotInScope since lecture also mentioned that missing user stories can potentially affect the end result of the product.
Thank you! :)
Based on the target user profile, i can be a business person wanting to use this app. However, the user stories only cater to financial advisors. Might be better to change the target user profile, or add user stories for 'as a user' instead of 'as a FA'