Hi Mike,

Are you looking for a Business Case that justifies why you should be developing business cases?  :)  I don't have any stats handy for you that measure Enterprise Analysis efficacy as such (perhaps because the outcome depends on how well an organization actually does it), but can give you some ways you might measure the need for it within your organization.  Analyses of project success rates consistently show low rates of fully successful projects - such as the Standish report findings that only about 35% of projects are successful, while about 20% fail completely and about 45% are 'challenged' (don't fail, but don't fully deliver either).  While projects fail for a variety of reasons, Enterprise Analysis is targeted as some of the common failure points.

Symptoms of the need for Enterprise Analysis include:

• Do your projects typically encounter issues with stakeholder engagement? (Stakeholders do not buy-in, or don't have time to meet conflicting priorities, demands from concurrent projects, etc.)
• What is the typical lifespan of application systems?  Are applications typically retired because they're no longer needed, or are they more often replaced or re-engineered because they just don't meet "evolving" business needs?  It's rare for businesses to radically change their business model - most often, if a system doesn't meet business needs it's because those needs weren't fully understood or addressed to begin with.
• Do people in your organization complain that their application systems aren't 'flexible' enough to adapt to business growth and change?  See above....
• How much time / effort / money is invested in enhancements to new application systems within the first 2 years after implementation (not requirements that were postponed, but additions or changes not identified until after the system went into production.)
• How are projects currently initiated in your organization?  Are the business needs documented at the start of new projects?   If so and if you have access to previous project documents, then it might be interesting to read through them and see how often the same / similar needs keep cropping up - because they were not truly understood or not not fully addressed by those projects.

These are the types of business problems that Enterprise Analysis is intended to solve.  Its justification is based on reducing the occurrence and organizational cost associated with these problems.  It's intended to make sure the business needs are fully understood and priotizied, that stakeholders are committed (at all levels of management), that projects are adequately resourced, that the right solution is found / delivered to solve the defined problem(s), etc. 

Hope this helps.

Sandy