10. May 2021 |

Requirements

Lately I have found my self thinking how could a customer – when buying software development services – determine in “requirements” part that the end result should not be ugly. I belive there is no standard for describing this.

For me it has been common sense that I simply do not deliver (preferrably don’t even build in the first pace) ugly things. And there is no need to specify it in the requirements that “users should not get lost” or “users should not hurt themselves”.

From my experience I see it does not seem to be very common in the industry.

Extreme programming believes in
‘it is better to do a simple thing today and pay a little more tomorrow to change it’ than ‘to do a more complicated thing today that may never be used anyway’. But simple here by in no way means mean broken, malfunctioning or ugly.

TBC

Leave a Reply

Your email address will not be published.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.