Business Analyst (BA) Training Material

Business Analyst (BA) Job Description

Description	The business analyst is the individual who has the primary responsibility to elicit, analyze, validate, specify, verify, and manage the real needs of the project stakeholders, including customers and end users. The business analyst is also known as a requirements analyst, requirements engineer, requirements manager, system analyst, or simply analyst. The business analyst serves as the conduit between the customer community and the software development team through which requirements flow. A business analyst is involved at some level throughout the entire system or software development life cycle. Upon establishment of the requirements baseline, the focus is shifted towards the management of the requirements specification and verifying the fulfillment of all requirements. The business analysis function is a project role, not necessarily a job title. The role may be performed by a dedicated BA or split among multiple team members who have other primary job functions, such as a project manager, product manager, or developer. The BA is responsible for seeing that the tasks are performed properly.
Skills Needed	·         Interviewing skills, to talk with individuals and groups about their needs and ask the right questions to surface essential requirements information ·         Listening skills, to understand what people say and to detect what they might be hesitant to say ·         Analytical skills, to critically evaluate the information gathered from multiple sources, reconcile conflicts, decompose high-level information into details, abstract up from low-level information to a more general understanding, distinguish presented user requests from the underlying true needs, and distinguish solution ideas from requirements ·         Facilitation skills, to lead requirements elicitation workshops ·         Observational skills, to validate data obtained via other techniques and expose new areas for elicitation ·         Writing skills, to communicate information effectively to customers, marketing, managers, and technical staff ·         Organizational skills, to work with the vast array of information gathered during elicitation and analysis and to cope with rapidly changing information ·         Interpersonal skills, to help negotiate priorities and to resolve conflicts among project stakeholders (such as customers, product management, and engineering) ·         Modeling skills, to represent requirements information in graphical forms that augment textual representations in natural language, including using modeling languages already established in the development organization
Knowledge Needed	·         An understanding of contemporary requirements elicitation, analysis, specification, verification, and management practices and the ability to apply them in practice; familiarity with requirements engineering books and resources ·         An understanding of how to practice requirements engineering according to several software development life cycles in a team environment ·         Knowledge of product management concepts and how enterprise software products are positioned and developed ·         Application domain knowledge is a plus, to have credibility with user representatives and be able to work effectively with them
Responsibilities	·         Work with the product manager or project sponsor to document the product’s vision and the project’s scope. ·         Identify project stakeholders and user classes. Document user class characteristics. Identify appropriate representatives for each user class and negotiate their responsibilities. ·         Elicit requirements using interviews, document analysis, requirements workshops, storyboards, surveys, site visits, business process descriptions, use cases, scenarios, event lists, business analysis, competitive product analysis, task and workflow analysis, and/or viewpoints. ·         Write requirements specifications according to standard templates, using natural language simply, clearly, unambiguously, and concisely. ·         Decompose high-level business and user requirements into functional requirements and quality, specified in an appropriate level of detail suitable for use by those must base their work on the requirements. ·         Define quality attributes, external interfaces, constraints, and other nonfunctional requirements. ·         Represent requirements using alternative views, such as analysis models (diagrams), prototypes, or scenarios, where appropriate. ·         Lead requirements analysis and verification, ensuring that requirement statements are complete, consistent, concise, comprehensible, traceable, feasible, unambiguous, and verifiable, and that they conform to standards. ·         Participate in requirements prioritization. ·         Participate in peer reviews and inspections of requirements documents. Participate in peer reviews of work products derived from requirements specifications to ensure that the requirements were interpreted correctly. ·         Enter, manipulate, and report on requirements stored in a commercial requirements management tool. Define requirement attributes and facilitate their use throughout the project. ·         Manage requirements traceability information and track requirements status throughout the project. ·         Manage changes to baselined requirements through effective application of change control processes and tools. ·         Establish and implement effective requirements practices, including use and continuous improvement of a requirements process. Assist with the development of the organization’s requirements engineering policies, procedures, and tools. ·         Implement ways to reuse requirements across projects. ·         Identify ways to assist product management in product planning through requirements development and analysis. Propose new product features and updates.
Measures of Performance	·         Evaluation from product and project management on overall product quality and effectiveness in the marketplace of the requirements after the product has been developed ·         Feedback from key customer or marketing representatives on the way in which the requirements engineering process was conducted ·         Customer satisfaction measures ·         Satisfying or exceeding requirements development schedules, resource constraints, and quality goals ·         Control of requirements creep attributable to missed requirements and leakage of “unofficial” requirements into the project