search

tanboonkhong / pe

0 stars 0 forks source link

DG - Planned Enhancement 5: Multiple Enhancement in One #6

Open tanboonkhong opened 12 months ago

tanboonkhong commented 12 months ago

Description: This planned enhancement is combining multiple enhancement into a single enhancement. "increasing the connection of applicant and interview" and "handling duplication of phone number and email" seems like two different enhancement to the implementation.

image.png

These two enhancement should be separated as it raised confusion to the reader of the guide.

Severity: Medium - Each planned enhancement in the Developer Guide should be responsible for one enhancement only, and this is the policy of the course as FeatureFlaw type of bug cannot be reported for Planned Enhancement.

Type: DocumentationBug

nus-pe-script commented 12 months ago

Team's Response

Two enhancements in one is a cosmetic issue that should be seperated with different labeling. No confusion can be faced by the user (unless you can justify properly), hence this is a purely cosmetic issue as the enhancements are still stated very clearly in seperate sentences.

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Medium]

Reason for disagreement: The team classified this issue as a "purely cosmetic issue". However, I believe this issue is not merely cosmetic but contravenes the course's guidelines for documenting planned enhancements, warranting a higher severity.

Course Policy Compliance: The course policy clearly states that each planned enhancement in the DG should be distinct. Combining multiple enhancements into one entry potentially violates this guideline, as it may obscure the specific feature flaws each enhancement intends to address.

Potential Misinterpretation and Clarity: While the enhancements may be stated in separate sentences, combining them into one entry can lead to misinterpretation or confusion about the scope and focus of each enhancement. This lack of clarity can affect the reader's understanding of the development roadmap and priorities. Especially when the PE depends on this section to report feature flaw.

Undermining Severity: The combination of different enhancements under a single enhancement might be perceived as an attempt to simplify or minimize the number of known issues. This approach could potentially mislead stakeholders about the extent of planned work and the application's current limitations, thus justifying a higher severity than a mere cosmetic issue. I think this bug should be higher than a verylow severity.