Here is a practical approach to defining, recognizing and improving the competencies all business analysts need, starting with eliciting requirements, creating the business requirements document, and the art of modeling.
This is an excerpt from ESI’s white paper, “Eight Things Your Business Analysts Need to Know: A Practical Approach to Recognizing and Improving Competencies.” To download the entire paper, visit www.esi-intl.com/eightthings.
A Standish CHAOS Chronicles report states that only 28 percent of software projects were expected to finish on time and on budget. Only 52 percent of completed projects met their proposed functionality. Based on a study of more than 13,000 U.S. projects, the Standish Group reported that successful projects made up “just over a third or 34 percent of all projects….” Estimates of the lost value for these projects in 2002 was $38 billion, with another $17 billion in cost overruns, for a total project waste of $55 billion against $255 billion total in project spending.
Unfortunately, poor project performance has become a way of life. Failure statistics like those above have ceased to even shock us. Most organizations have come to accept project failure — along with a loss of money, time and functionality—as a given. With constantly improving