A Longstanding Absurdity

Is the bad-software problem really caused by bad requirements definition, which we could fix by doing a better job up front, if only we were more diligent and more professional in our work?

We have made this our primary excuse for bad software for decades. If this was really the problem, and if processes focusing on early lockdown of requirements provided the needed solution, wouldn’t we have solved this by now?

A process that requires us to lock down decisions early will maximize our risk, not manage it.

Cem Kaner

Leave a Reply

Your email address will not be published. Required fields are marked *