I have been working with several clients around identifying and developing business analysts. \u00a0As a certified business analyst professional I can give a keen insight into what skill sets are required for a successful candidate. \u00a0As business analysts, we\u00a0spend our days analyzing all of the initiatives of our companies, what projects are being implemented, when and why and what the impacts will be on our products and services, our systems and processes, our clients and stakeholders.\u00a0 We dive in to understand how each initiative aligns with which corporate goal and development agenda items.<\/p>\n
Surprising to me, many people asked me the same question – “What does a business analyst actually do?<\/em>”<\/p>\n From our conversations, and from their past experience, it would seem that most people, and bosses confuse business analysts and project managers. \u00a0In fact, at many firms the same person filled both roles on major initiatives. \u00a0That’s bad.<\/p>\n So to help clarify I am sharing this five part article series “What Does a Business Analyst Do?<\/em>” with all of my clients.<\/p>\n Let’s get started, shall we?<\/p>\n ___________________________________________________________________________________________<\/p>\n The primary role of the business analyst (BA) is to act as the requirements manager<\/u><\/em><\/strong> for a project.\u00a0 This role may begin in the earliest stages of the project life cycle as your business decides whether a project is even necessary, and it may continue through testing, delivery, and closeout as the BA works with the solution team to ensure requirements are met.\u00a0 A close relationship and communication with the your firm’s strategy office and\/or new initiatives committees will be paramount.<\/p>\n The BA as a Communicator<\/em><\/strong><\/p>\n Communication is a key skill needed for a BA’s success as a facilitator, presenter and negotiator.\u00a0 The BA must possess good communications skills in order to communicate the impact of the solution to your\u00a0end users and other stakeholders.<\/p>\n Often, the BA is responsible for negotiating the terms of solutions between stakeholders and the technical team.\u00a0 The BA must be IT savvy to effectively communicate with the technical members of the team such as any systems analysts, application developers, designers, and testers.\u00a0 The BA should communicate solution requirements in terms that enable the IT’s* project team to easily and effectively translate the requirement into specifications. [*Note: In using “IT” it is understood that there may be technical stakeholders other than IT, but for expediency I will use “IT” as an example in these postings]<\/p>\n <\/p>\n The BA as Process Modeler<\/em><\/strong><\/p>\n Process modeling is another key skill used by the BA to ensure that your firm is able to meet business needs effectively.\u00a0 Through continuous process improvement, benchmarking, and process modeling, the BA ensures that all tasks and activities carried out by the business address the business needs.\u00a0 It is valuable to have a BA who can also challenge and question all processes thoroughly in order to allow the exploration of retiring legacy, non-value added processes.<\/p>\n The BA must be knowledgeable and skilled in modeling their business line to identify business needs, problem areas, business requirements, opportunities for improvement, any other gaps, and solution assessment.\u00a0 In addition to modeling, the BA should be skilled in defining the business problem, evaluating existing processes, finding root causes, designing and documenting new processes in line with your firm’s business strategy driving the solution as well as monitoring implementation of the solution.<\/p>\n <\/p>\n The BA as Risk Manager<\/em><\/strong><\/p>\n The ability to evaluate risk is critical to the BA’s success.\u00a0 Although the project<\/u> manager has primary responsibility to identifying, assessing, and responding to project<\/u> risks, the BA provides risk-decision support in collaborating with the project manager, and during the project’s implementation the BA is responsible for managing requirements risks.\u00a0 This requires knowledge of techniques for identifying requirements risks; defining a requirements risk management approach; and performing requirements risk planning, monitoring, and control.\u00a0 A robust relationship and communication with your firm’s risk managers, quality analysts, and\/or legal team is key.<\/p>\n The BA provides input to the project manager, project sponsor, and portfolio management team regarding risks that may have a positive or negative effect on the proposed or active project.\u00a0 This is pertinent to decisions prior to project launch and project execution.\u00a0 In the pre-project period, the BA must conduct the initial risk assessment by assisting executive management in identifying risk probability and impact.\u00a0 The result will provide input and support for management’s decision as to whether the proposed project should go forward, be delayed, or be canceled.<\/p>\n As the individual who is most knowledgeable about the business opportunity, the BA typically is in a unique position to identify and assess risks during analysis and solution development.<\/p>\n <\/p>\n The BA’s Contribution to Enterprise Analysis<\/em><\/strong><\/p>\n In addition to risk-decision support, the BA may be involved in numerous other pre-project activities such as strategic enterprise analysis.\u00a0 Senior BAs, for example, may support the strategic planning process by being asked to perform competitive analysis and benchmark studies.\u00a0 They may also become involved facilitating strategic goal-setting sessions, preparing the business case for future projects, and monitoring business results after project implementation.<\/p>\n <\/p>\n The Role of the BA in Requirements Elicitation and Documentation<\/em><\/strong><\/p>\n In requirements elicitation, the BA’s goal is to manage the processes and techniques that will elicit and validate the information needed from the business and its users to facilitate the successful development of a solution.\u00a0 In this capacity, the BA must –<\/p>\n The BA must use effective elicitation approaches and techniques and know how to prepare and execute them in any given situation.\u00a0 For example, the BA must be skilled in interviewing, facilitating collaborative sessions, observation, resolving conflicts, analysis, and so on.<\/p>\n In general terms, the BA is responsible for eliciting, validating, and documenting requirements in the most appropriate format for IT, and for managing risks to the requirements.\u00a0 Steps in this role may include –<\/p>\n It is important to remember that solutions are not<\/u><\/em><\/strong> predetermined by the BA; they are driven solely by the requirements and resource capacity of the business.<\/p>\n <\/p>\n The Role of the BA in Testing the Solution<\/em><\/strong><\/p>\n When testing solutions, BAs are often directly responsible for –<\/p>\n The BA needs to show that the implemented solution meets business requirements<\/u>.\u00a0 To do this, he or she is often responsible for creating test scenarios and test cases.\u00a0 A test scenario is a procedure describing a user’s experience in interfacing with the solution.\u00a0 A test case is an execution of the scenario with specific input determined by business rules.\u00a0 BAs coordinate and execute usability testing with participation from user representatives for the purpose of measuring the quality of the user’s experience with the solution.\u00a0 Customer satisfaction assessments are planned and executed by BAs.\u00a0 They require the BA to be skilled in interviewing, observation, conducting focus groups, and designing questionnaires.<\/p>\n\n
\n
\n