Required: Fixing the Requirements Mess ; The requirements process, literally, deciding what should be included in software, is destroying projects in ways that arent evident until its too late. Some CIOs are stepping in to rewrite the rules

Requirements, as every CIO knows, are a problem, but CIOs may not be aware of just how catastrophic the problem has become. Analysts report that as many as 71% of software projects that fail do so because of poor requirements management, making it the single biggest reason for project failure - bigg...

Full description

Saved in:
Bibliographic Details
Published inCIO Vol. 19; no. 4; p. 1
Main Author Lindquist, Christopher
Format Trade Publication Article
LanguageEnglish
Published Framingham Foundry 15.11.2005
Subjects
Call centers
Certification
Chief information officers
Information management
Project management
Quality control
Roles
Skills
Software
Systems development
Technological planning
United States > US
Online AccessGet full text

Cover

More Information
Summary:Requirements, as every CIO knows, are a problem, but CIOs may not be aware of just how catastrophic the problem has become. Analysts report that as many as 71% of software projects that fail do so because of poor requirements management, making it the single biggest reason for project failure - bigger than bad technology, missed deadlines or change management fiascoes. Though CIOs are rarely directly responsible for requirements management, they are accountable for poor outcomes, which, when requirements go bad, can include: project delays, software that doesn't do what it's supposed to and, worst of all, software that may not work correctly when rolled out, putting the business and the CIO's job at risk.
ISSN:0894-9301