Open pzl111 opened 10 months ago
Thank you for your response. However, the decision to limit the input to 15 characters was to ensure the UI displays properly. The decision for limiting to 15 characters was also done as we modelled other popular financial tracking applications that also used Category
such as Seedly. In these applications, Category
is often a single word and none would exceed more than 10 characters. It is expected that Category
would be short and sweet - (household expenses
could be converted to simply household
) as it is already considered an expense. Though there could be possible arguments of longer words, we decided to not factor in such corner cases as we modelled how other popular applications did, hence why this is a Low severity, not Medium. Therefore, we would consider this as out of scope for our application. However, we can consider this for future iterations, thus why it is NotInScope.
Team chose [response.NotInScope
]
Reason for disagreement: Classifying it as not in scope is not reasonable, with reference to the textbook:
Not limiting the category length would provide much more value than just 15 characters. Furthermore, fixing the UI displaying properly is an easy fix by allowing text wrapping. The low effort required compared with the much greater value proposition makes it unjustifiable to be "not in scope" but rather a flaw in the group's effort to provide value.
I find it to be a hindrance to having only 15 characters for the category. For example, a natural category would be
household expenses
, but I cannot do that since its more than 15 characters. It causes a natural and not uncommon inconvenience, where users have to resort to naming things differently.