If you had to do without one or the other in a software project, which would you pick? I’ve had plenty of projects in which the client or PM thought they could get away without one or the other. We always paid the price.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If you had to do without one or the other in a software project, which would you pick? I’ve had plenty of projects in which the client or PM thought they could get away without one or the other. We always paid the price.
I’d say you could go without Testing rather than Requirements. If you don’t have requirements, how do you know what you’re developing?
If the programmers are good enough, they should be able to catch most of the egregious errors that testing would find.