Requirements Quality Assurance – Why?
RQA | Why the correct requirements really matter.
Why do so many software projects fail…
A recent study shows that up to 70% of software projects fail at some level due to poor/changed/misunderstood requirements. Poor requirements are to blame for under budgeting and over spending on projects around the world. The poor communication of requirements has become accepted as a common pitfall in the software world.
I read a really interesting article recently which addresses this exact issue and comes to the table with formal methodology by which, Requirements are validated for the inaccuracies and ambiguities that typically add significant costs in development, testing, and resource allocation to projects.
Please see below for an out take of the article and follow the link to read more:
Requirements Quality Assurance (RQA) improves project outcomes by fostering a deep, accurate and shared understanding of a project or program’s needs to enable communication between all parties; customer, users, contractors and suppliers, technical engineering, management, etc. It is well accepted in the software world that the later an issue that is related to understanding of needs is founds, the more expensive that issue is to resolve (most models show the cost increases exponentially). RQA is, conservatively, about 30% more effective at finding and resolving the types of ambiguity and incompleteness issues that cause major project challenges than is the currently accepted industry best-practice. RQA has been applied on over a dozen large, complex, nationally critical defence and aerospace programs to provide significant risk mitigation and cost-saving. Access Testing is now providing the RQA service to its clients through Dr Dan Powell, the recognized authority on the method and its application.
Requirements Quality Assurance – Why?
• On average, large IT projects deliver 56% of expected value [McKinsey and Co, 2012]
• On the average large technology project, requirements documents accurately define only 54% of intent [Powell, 2012]
• On the average large IT project you get what you ask for!!!
The failure of current requirements processes to deliver an accurate understanding of intent, shared by all parties – technical and non-technical, frequently results in significant project budget and schedule blowouts and under-delivery against expectations.
Requirements Quality Assurance (RQA) improves project outcomes by fostering a deep, accurate and shared understanding of a project or program’s needs to enable communication between all parties; customers, operations, contractors and suppliers, developers, testers, management, etc.
RQA is a systematic methodology that delivers requirements with about 5x fewer major issues than does the currently accepted industry best-practice. These are issues that typically escape even the most mature review and inspection processes, resulting in variation from expectation and that add significant costs to projects. This significantly improves the chances of a project delivering its expected benefit to stakeholders.
Requirements are developed and elaborated, communicated and agreed using RQA, on average, in about 2/3 the time typically budgeted for requirements definition on most projects.
RQA is a lean process that reduces risk and cost on projects regardless of whether the requirements are defined up-front or defined and elaborated just-in-time in an iterative process.
RQA has been applied on over a dozen large, complex, nationally critical defence and aerospace and large government IT programs to provide significant risk mitigation and cost-savings. It has also been successfully applied to smaller projects where clients have limited budget, and capacity for absorbing overruns.
“Requirements Quality Appraisal (RQA) Whitepaper” Read more http://lnkd.in/b3Y7mth