Methods of validating requirements
The best option that project managers have is to use notoriously inaccurate estimates of cost of work for this purpose.In a 1998 article, Fleming and Koppelman  assert that "The single most important benefit of employing earned value is the cost efficiency readings it provides".The result is a simple set of metrics providing early warnings of performance issues, allowing for timely and appropriate adjustments.In addition, EVM improves the definition of project scope, and provides valuable metrics for communicating progress to stakeholders.So yes, requirements matter for many, many reasons…but when it comes to reviews, consider separating how you document your requirements and how you communicate your requirements for the sake of getting meaningful, targeted feedback that will make your software projects more successful.Measuring Integrated Progress on Agile Software Development Projects Tamara Sulaiman, PMP, CST, Solutions IQ, Hubert Smits, CST, Rally Software, Summary Earned Value Management (EVM) is a well known project management technique which measures the integration of technical performance, cost and schedule against planned performance within a given project.And I’d contend these objectives can be met using multiple different business analyst techniques. Do your stakeholders know how to read requirements? It’s easy to lay blame when these individuals don’t provide the feedback we’re looking for.
Before exploring some alternative approaches, let’s take a step back and think about what problem we’re trying to solve with requirements reviews. Factor these into your approach to requirements reviews. Many of your most important stakeholders won’t give a lick about your beloved requirements and it’s self-centered of us to think they can and should.
Here are just a few ideas for communicating scope across your organization: None of this above should be read to say that requirements don’t matter or that the deliverables are unnecessary.
I’ve analyzed many a problem by writing a use case that no one ever saw except the developer–the content of the use case was fully validated while the “use case” itself was not.
Using this information, metrics assessing cost efficiency and schedule efficiency are calculated.
Metrics forecasting the expected cost to complete a project and total expected cost of a project based on past project performance are derived. Agile (or lightweight) Software Development Methods have been developing over the last 15 years.