Submission + - What Bosses should know: software requirements
Esther Schindler writes: "CIO.com asked developers to name the ONE thing that they wished the CIO understood about software requirements. The summary is several pages long, but it pulls no punches: from the role of requirements, to defining who creates the requirements (and in how much detail), to the need to shake the boss to get him to understand that requirements change, to paying attention to the process. It's all here, in Five Things CIOs Should Know About Software Requirements, with a few dozen developer's voices loud and clear. For instance, one developer comments, "The CIO has to realize that if there is no bad news, there is something very wrong. Smiling people nodding 'Yes' in meetings is not a sign of great intelligence at work.""