nus-se-bot
commented
3 years ago Team's Response
According to the CS2103T website which describes the bug severity levels, the severity assigned by the tester is highly inaccurate. It is NOT a flaw that affects most users and caused major problems for users. It does NOT make the almost unusable for most users as it does not hinder the functionality, usability, or ease of comprehension in any way at all. Thus our team has changed the severity level to the correct severity which is very low according to the provided descriptions of the severity labels. Kindly refer to the picture below which explains the respective severity labels:
Secondly, it is indeed recommended to come up with around 30 user stories for the product during the initial brainstorming session but that was purely for planning purposes and it is not a compulsory requirement to include 30 user stories in the final DG. Our team came up with 35 user stories in the initial brainstorming sessions. In the following weeks after the initial brainstorming session, there were instructions to reduce the 35 user stories to 5 important user stories which was what our team did as per the requirement. Furthermore, there is no instructions on the minimum or maximum number of user stories required to be included in the DG. The CS2103T website mentioned that our DG should follow the AB3 DG which only included 6 user stories as shown below:
Thirdly, the user stories which the tester said are missing such as "As a NUS student, I want to calculate my remaining progress quickly, so that I can plan out my modules and studies better" and "As a NUS student, I want to be able to set goals about my CAP, so that I can stay motivated and plan my studies better" are already encapsulated in one of our user stories as shown below:
Our user story states that the user wants to view his current progress which implies that he must have already set a goal in order to see his progress towards his goal. Tracking his progress clearly indicates that goal-setting is desired since the user must set a goal to track his progress towards it. Setting goals is clearly implied through viewing his progress. Thus, we have already included the user stories which the tester claims to be missing.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Thank you for your response.
Secondly, it is indeed recommended to come up with around 30 user stories for the product during the initial brainstorming session but that was purely for planning purposes and it is not a compulsory requirement to include 30 user stories in the final DG. Our team came up with 35 user stories in the initial brainstorming sessions. In the following weeks after the initial brainstorming session, there were instructions to reduce the 35 user stories to 5 important user stories which was what our team did as per the requirement. Furthermore, there is no instructions on the minimum or maximum number of user stories required to be included in the DG. The CS2103T website mentioned that our DG should follow the AB3 DG which only included 6 user stories as shown below:
Where did you find the instructions to reduce the 35 user stories to 5 important user stories? I think there are no such instructions from the teaching team to reduce user stories.
Thirdly, the user stories which the tester said are missing such as “As a NUS student, I want to calculate my remaining progress quickly, so that I can plan out my modules and studies better” and “As a NUS student, I want to be able to set goals about my CAP, so that I can stay motivated and plan my studies better” are already encapsulated in one of our user stories as shown below:
The user stories I said are missing are not encapsulated in the user stories you've shown. Firstly, the shown user story only calculates the current progress and not the remaining progress. Secondly, it is not necessary to set a goal in order to calculate your current CAP as your current CAP is only based on the results you have so far. Therefore, the user stories I mentioned are indeed missing and this is a valid bug.
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.High]
- [x] I disagree
Reason for disagreement: > According to the CS2103T website which describes the bug severity levels, the severity assigned by the tester is highly inaccurate. It is NOT a flaw that affects most users and caused major problems for users. It does NOT make the almost unusable for most users as it does not hinder the functionality, usability, or ease of comprehension in any way at all. Thus our team has changed the severity level to the correct severity which is very low according to the provided descriptions of the severity labels. Kindly refer to the picture below which explains the respective severity labels:
Yes, I apologize that I have assigned a highly inaccurate severity level. However, I think the correct severity level should be severity.Low instead of severity.VeryLow. According to the module website, user stories capture user requirements in a way that is convenient for scoping, estimation, and scheduling. Therefore, missing and incomplete user stories would make future developers hard to grasp user requirements and hence make the development team hard to schedule, scope, and estimate features. This will cause minor inconveniences for future MyMods developers.
According to the brainstorming session we have done on the early weeks of
CS2103T, it is recommended to come up with around 30 user stories for the product. However, you only stated5user stories, which is much smaller than30. Furthermore, some important user stories according to implemented features are missing, such as: