Summary: The business analyst work starts by defining the scope of the business area.

The BA must make sure that the project scope is clear before the requirement gathering starts. The scope may be given by the project manager, project sponsors or the BA takes the responsibility for defining and documenting the scope as part of the requirements gathering task. The enterprise analysis task is done which provide details about the business needs, problems faced, goals and objective of the organization. This provides strong inputs for planning business analysis approach and activity. Gap analysis is done to evaluate the shortcoming in existing infrastructure and business process; then accordingly methods are identified to take the The project scope helps to understand the purpose of the project and its objectives. It includes the project viewpoint, project assumptions, and business risks. Scope helps to understand the current challenges faced by the business and what solution would be required to take the company from current to desired state. Well defined scopes strengthen the Analysis process, inputs from various stakeholders is taken to better understand and draft the scope.

After the scope of business is defined the works proceed to elicit the requirements. Eliciting requirements must completely define the project that goes compatible with the scope defined. The BA must identify key people and proper channel to gather the requirements. Gathering requirement is an iterative process that involves follow with multiple people, collecting information from various stakeholders and summarizing all to form a common opinion toward the desired business goals. The requirements are prioritize and address as per the project solutions.

Plan, monitor and report on business analyst performance This task enables planning and monitoring the health of business analysis work throughout project work. It will help in documenting necessary metrics which are qualitative measures or a process or project. It includes the tracking mechanism to assess, work performed by business analysts and step to correct any problem areas. Expert judgment is done to assess the inputs needed to develop a BA approach plan. Input is provided by expertise person or group as per the business need. Stakeholder analysis is done so that the required project roles are identified filled and interest of the stakeholder is taken care of and prioritized accordingly.

Variance analysis is done to measure the magnitude of variation in business analysis work done. The business analysis performance measures described in the task plan, monitor and report on BA performance are use to assess the difference between planned and actual work. It also helps in identifying corrective measures to bring back work in line aligned with business analysis plan. The requirement management and communication work is an iterative work which goes in parallel with PA plan analysis, enterprise and requirement analysis. Managing the requirement is an important as it ensures that the work moves smoothly as per the plan and effective business communication with stakeholders and any owner is team is established. Managing requirement involves change control, requirement storage, tracing related requirements and maintaining them for reuse.

Task for managing requirement and communication are- Manage solution and requirement scope, Maintain requirement traceability, maintaining requirement for re-use, prepare requirement package and communicate requirement. Requirement must be checked against the solution scope to make sure that they are against the agreed project boundaries. Stakeholder list, roles and responsibilities, requirement and management plan are key input to this task. It is important to maintain relationships between requirements and other solution components. Tracing a requirement refers the ability to look at the requirement and other to which it is related. Many tools support this task. Traceability is a useful tool for performing impact analysis. A satisfied requirement can be re-used for future project. It helps in product enhancement and future system changes. Requirement can be prepare in many format. The selected format must be aware to all party and it should be clear, concise, and accurate and must have appropriate level of details. It is the responsibility of the BA to present the requirement in correct format as this is very critical to the project. Communicating requirement is an important aspect of BA work flow which needs to bring all stakeholders to a common understanding of the requirements. Also there may be conflicts in managing requirements because it serves many people need; it is BAs responsibility to make sure that final requirement brings common understanding among all stakeholders and aligns appropriately with business need. In case of any conflict between stakeholders, the same is documented in requirement log issue. The BA task requires conducting one or more presentation during the project cycle. Overall objective of the presentation and the target audience should be clear before BA make requirement presentation. Presentation may be formal or informal. Requirement review can be conducted at any time during the project. Its purpose it to have project stakeholders verify the accuracy of the requirements, and the review purpose should be clearly stated.

The BA must have complete requirement document, list of appropriate reviewers, a meeting vehicle, and facilitation skills. Obtaining final approval from the stakeholder is the final task within requirement management and communication. Enterprise analysis is the starting point for initiating a project. It is continued as the change progress and more information is collected. It consists of the collection of task for analyzing the business situation to completely understand the problems and opportunities. Assessing the current and future view is the enterprise to understand the change required to meet desired business and strategic goals. Essentials task required to perform the enterprise analysis task are defining business need, gap in capabilities, solution approach, defining solution scope and business case. Business need define business problem or new business opportunity in brief detail to determine the recommended solution. New business needs can be generated in many ways- top down or bottom up, middle management or from external drivers. Technique employed to define the business need includes: Decomposition of techniques to convert goals into achievable objective and measures. Opportunity and problem analysis.

Gap analysis determine the amount of change require to achieve the business goals and objectives. Business need and enterprise architecture is input to this task. Internal and external analysis, gap analysis and developing target state enterprise are key element for determining the gap analysis. Requirement Analysis is performed for brief understanding of stated requirements. The output of this task produce modeled requirements that have been prioritized, organized, verified, and validated by the stakeholders. Requirement prioritization determines the importance of the requirements considering various internal and external factors. Business case, stated requirements, stake holder analysis are key inputs required to produce the prioritized requirements. The final requirements as an output is assigned a priority number based on the priority. The task defined as part of the requirements analysis include Prioritize, Organize, Specify and model requirements, Determine assumptions and constraints, verify and validate requirements. Different criteria decide the prioritization- business values, technical risk, implementation difficulty, compliance, success probability and stakeholder agreement and key elements of them. Various techniques support the prioritization process.

 MoScoW Analysis divides the requirements into four categories: Must, Should, Could and wont. Kano Analysis divides product characteristics into three categories: Threshold, performance and excitement. Timeboxing/ Budgeting prioritize the requirements based on allocation of the resource. In Voting proposed featured and voted by each participant in prioritization process and the based on the lead count requirements and processed.

As stake holder play key role in decision making, inputs from the concerned stakeholder should be taken while deciding the priority of the requirements. The requirements are organized which is highly influenced by the nature of the project. Various techniques are used for organizing individual requirements into a logical structured set of requirements. Functional decomposition is of one the prevalent techniques used to organize requirements. Decomposition helps to understand how requirements impact the business area. Requirement organization task does the structuring of the requirements and establish a relationship between them. Specifying and modeling requirement document, stakeholder needs and describe the requirements in various diagrammatic and textual ways, which is easy to understand and correlates with the needs of the stakeholders. Assumptions and constraint are identified during analysis that will impact the solution design. The BA not only identify the assumptions but also give effort to confirm the accuracy and manage the risk associated so that the define solution can meet business need. Constraints are limitation to the project. Assumptions and constraint are identified as an output of elicitation. Business and technical constraint and assumptions are key input elements to determine assumptions and constraints. The task verifying requirement evaluates and verify requirement to check if they are well define and meets the quality specification. It helps the solution development team in designing process. Verification process ensures that the requirement have been defined correctly. However requirement verification differs from requirement validation. Validation is pre-requisite form verification purpose. Validation checks the stated requirement from business goals and objective point of view, whereas verification focuses on quality. Input to this task is complete set of artifact requirements which are prioritized, specified and organized properly. Non-functional requirement describes the required qualities of the system which supplements the functional requirement documentation. It helps to identify the usability and performance characteristics. Organization modeling describes the structure of the organization that describes roles, responsibilities and reporting structure which with the goals of the organizations goals.

Solution Assessment and validation This activity is performed to assess and validate the component of the solution. It describes the tasks that ensure that the solution meets the defined business need. BA ensures that the solution assessment is done properly so that it justifies stakeholder concerns. The task involves in this process are- Assess proposed solution, Allocate requirements, Assess organization readiness, Define transition requirement, validate solution, Evaluate solution performance. The proposed solution is assessed to determine how closely they meet stakeholder and solution requirements. It may be performed on single solution or on available multiple solution options. Assumptions and constraint, prioritized requirement and solution option act as input parameter for assessing proposed solution. Allocating requirements is the process of assigning stakeholder and solution requirements to solution components. Allocation process begins as early during the project lifecycle and it continues to perform until the valid needs are met. The majority of business solutions will be composed of solution components. The solution design must have a defined set of components and cost and effort associated with it. Solution scope allocates business requirement to components and releases. Assess organizational readiness evaluates the impact of new solutions for the organization. Whether the organization is prepare for the change that the solution will cause. The purpose of define transition requirement is to find capabilities needed to transition from existing solution to a new solution. Solutions are then validated to check if they meet with desired business need. Problem found if any is identified and it is reported and prioritized for resolution. After the solution is deployed, the performance is analyzed to check it positive and negative impact. It is done to understand the value they deliver and identify opportunities for improvement in the future. It clearly reflects how the system is working in real life scenario, also to check if it related to the organization business goals and objectives.