<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:burst="http://xmlns.com/burst/0.1/" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns="http://purl.org/rss/1.0/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:swrc="http://swrc.ontoware.org/ontology#" xmlns:cc="http://web.resource.org/cc/"><channel rdf:about="http://www.bibsonomy.org/bibtex/c57ee9bc093ed76a8ebdf7c645508990"><title>BibSonomy publications for /bibtex/c57ee9bc093ed76a8ebdf7c645508990</title><link>BibSonomyburst/bibtex/c57ee9bc093ed76a8ebdf7c645508990</link><description>BibSonomy RSS feed for /bibtex/c57ee9bc093ed76a8ebdf7c645508990</description><dc:date>2012-02-17T03:59:11+01:00</dc:date><items><rdf:Seq><rdf:li rdf:resource="http://www.bibsonomy.org/bibtex/242329b68e7667a9894629c1dbf843ba4/neilernst"/></rdf:Seq></items></channel><item rdf:about="http://www.bibsonomy.org/bibtex/242329b68e7667a9894629c1dbf843ba4/neilernst"><title>Business Analysis Benchmark: The Impact of Business Requirements on the Success of Technology Projects</title><link>http://www.bibsonomy.org/bibtex/242329b68e7667a9894629c1dbf843ba4/neilernst</link><dc:creator>neilernst</dc:creator><dc:date>2008-02-19T20:37:10+01:00</dc:date><dc:subject>empirical requirements </dc:subject><content:encoded>&lt;span class=&#034;authorEditorList&#034;&gt;&lt;a href=&#034;/author/Ellis&#034;&gt;Keith Ellis&lt;/a&gt; &lt;/span&gt;&lt;em&gt;IAG Consulting, Inc., &lt;/em&gt;(&lt;em&gt;January 2008&lt;/em&gt;)</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="http://www.bibsonomy.org/tag/empirical"/><rdf:li rdf:resource="http://www.bibsonomy.org/tag/requirements"/></rdf:Bag></taxo:topics><burst:publication><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/242329b68e7667a9894629c1dbf843ba4/neilernst"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/242329b68e7667a9894629c1dbf843ba4/neilernst"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#TechnicalReport"/><owl:sameAs rdf:resource="http://www.iag.biz/images/resources/iag%20business%20analysis%20benchmark%20-%20full%20report.pdf"/><swrc:date>Tue Feb 19 20:37:10 CET 2008</swrc:date><swrc:institution><swrc:Organization swrc:name="IAG Consulting, Inc."/></swrc:institution><swrc:month>January</swrc:month><swrc:title>Business Analysis Benchmark: The Impact of Business Requirements on the Success of Technology Projects</swrc:title><swrc:year>2008</swrc:year><swrc:keywords>empirical requirements </swrc:keywords><swrc:abstract>The Business Analysis Benchmark report presents the findings from surveys of over 100 companies
and definitive statistics on the importance and impact of business requirements on enterprise
success with technology projects. The survey focused on larger companies and looked at
development projects in excess of $250,000 where significant new functionality was delivered to
the organization. The average project size was $3 million.
The study has three major sections:
1. Assessing the Impact of Poor Business Requirements on Companies: Quantifying the cost
of poor requirements.
2. Diagnosing Requirements Failure: A benchmark of the current capability of organizations
in doing business requirements and an assessment of the underlying causes of poor
quality requirements
3. Tactics for Tomorrow: Specific steps to make immediate organizational improvement.
In addition to this full text report, these sections and an executive summary have also been
published as stand-alone white papers for ease of use. All can be accessed from www.iag.biz .
The study provides a comprehensive analysis of business requirements quality in the industry and
the levers for making effective change. The following issues are addressed in the report: the
financial impact of poor quality requirements; the information needed to identify underlying
issues critical to success; and, the data necessary to target specific recommendations designed
to yield performance improvement.</swrc:abstract><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Keith Ellis"/></rdf:_1></rdf:Seq></swrc:author></rdf:Description></burst:publication></item></rdf:RDF>
