In the recent past, organisations facing startlingly high project failure rates. Research identified the failures of project that less than 30 percent of software projects are completed on time and on budget—and 50 percent end up meeting their proposed functionality. Wrong defining requirements are the stepping step to failure of software projects to properly and accurately at the very beginning of the project lifecycle points to lack of business analysis competency. So, the role of the Business Analyst has to act as a translator or liaison between the different stakeholders.
Competency #1: Eliciting Requirements – The major responsibility of an effective Business Analyst is to elicit and document and classify into different requirements. Requirements can be conditions, functionality of the system or application, products or services. Business Analysts spend time in gathering requirements the most effective way to help organizations understand the challenges being faced at hand before trying to propose the solution. The techniques necessary for capturing requirements are often referred to as elicitation.
Competency #2: Creating the Business Requirements Document – BRD is an exhaustive written study of all facets of different requirements like regulatory, business, user, functional or non-functional requirements, which provide sights of the business area. The BRD is a detailed profile of primary and secondary user communities and should come directly from the requirements the business analyst has already gathered. Once the document is completed, the business analyst and the client or user should meet for a formal review to approve the BRD.
Competency #3: Testing – Testing aspects need to be known by all the resources involved in a software project and applies to several different levels of work. So, is the responsibility of a Business Analysts needed to test the developed products / services to validate whether the requirements have been me the expectations of business stakeholders.
Competency #4: End-User Support – It’s a common misconception among project stakeholders that the project ends with transition of application to the business stakeholders. Business analysts should be competent enough to have aware about end-user support after the product is delivered is a vital part of the process.
Competency #5: IT Fluency – Does BA need knowledge about IT? A junior business analyst would need to have a clear understanding of the IT products and tools necessary for the business to function. An intermediate business analyst understands interconnectivity and relationships between the tools and system architecture and information architecture. A senior business analyst will demonstrate his or her IT fluency across an industry vertical. He or she may also have a very clear understanding of how different IT products are related, interface with and connect to each other, as well as the positive or negative effect they may have in a given situation.
Competency #6: Business Process Re-Engineering – BPR is a competency to be proficient by all levels of employees; especially business analysts must be highly skilled. Business Analysts at junior level has responsibility to identify, using various modelling techniques and best possible areas of improvement. Business Analysts at intermediate level should know the job of walking with the client and / or user through each step of the process of examining where individual tasks that could potentially be improved. The senior Business Analysts’ work begins at making suggestions for improvements.