Chapter 5. Optimizing Customer Involvement
There is a tendency in many projects purposely to exclude the user from the decision-making process. The usual reason is that the software developer feels that if the user does become involved, he will never make up his mind; his requirements will be constantly changing. There is a small degree of validity in this concern, but in practice the advantages of user involvement far outweigh this potential disadvantage.
—Glenford J. Myers, Software Reliability
“I’ll go find out what they need, and the rest of you start coding.” This cartoon caption is uncomfortably close to the way some software organizations still treat the requirements engineering process. Unfortunately, the stated specifications and the ...
Get Creating a Software Engineering Culture now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
