Business analysis is the discipline[1] of identifying business needs and determining solutions to business problems.

Solutions often include a systems development component, but may also consist of process improvement, organizational change or strategic planning and policy development. The person who carries out this task is called a business analyst or BA.[2] Those BAs who work solely on developing software systems may be called IT Business Analysts, Technical Business Analysts, Online Business Analysts or Systems Analysts. Business analysis sub-disciplines

Business analysis as a discipline has a heavy overlap with requirements analysis sometimes also called requirements engineering, but focuses on identifying the changes to an organization that are required for it to achieve strategic goals. These changes include changes to strategies, structures, policies, processes, and information systems. Examples of business analysis includes: Enterprise analysis or company analysis Focuses on understanding the needs of the business as a whole, its strategic direction, and identifying initiatives that will allow a business to meet those strategic goals. It also includes: Creating and maintaining the business architecture Conducting feasibility studies Identifying new business opportunities Scoping and defining new business opportunities Preparing the business case Conducting the initial risk assessment Requirements planning and management Involves planning the requirements development process, determining which requirements are the highest priority for implementation, and managing change.
Requirements elicitation Describes techniques for collecting requirements from stakeholders in a project. Techniques for requirements elicitation include: Brainstorming

Document analysis Focus group Interface analysis Interviews Workshops Reverse engineering Surveys User task analysis Process mapping

Requirements analysis and documentation Describes how to develop and specify requirements in enough detail to allow them to be successfully implemented by a project team. The major forms of analysis are: Architecture analysis Business process analysis Object-oriented analysis Structured analysis

Requirements documentation can take several forms: Textual Matrix Diagrams Models

Requirements communication Describes techniques for ensuring that stakeholders have a shared understanding of the requirements and how they will be implemented. Solution assessment and validation Describes how the business analyst can verify the correctness of a proposed solution, how to support the implementation of a solution, and how to assess possible shortcomings in the implementation. [edit]Business

analysis techniques

There are a number of generic business techniques that a Business Analyst will use when facilitating business change. Some of these techniques include:

PESTLE This is used to perform an external environmental analysis by examining the many different external factors affecting an organization. The six attributes of PESTLE: Political (Current and potential influences from political pressures) Economic (The local, national and world economy impact) Sociological (The ways in which a society can affect an organization) Technological (The effect of new and emerging technology) Legal (The effect of national and world legislation) Environmental (The local, national and world environmental issues) HEPTALYSIS This is used to perform an in-depth analysis of early stage businesses/ventures on seven important categories: Market Opportunity Product/Solution Execution Plan Financial Engine Human Capital Potential Return Margin of Safety MOST This is used to perform an internal environmental analysis by defining the attributes of MOST to ensure that the project you are working on is aligned to each of the 4 attributes. The four attributes of MOST Mission (where the business intends to go) Objectives (the key goals which will help achieve the mission) Strategies (options for moving forward) Tactics (how strategies are put into action)
[4] [3]

SWOT This is used to help focus activities into areas of strength and where the greatest opportunities lie. This is used to identify the dangers that take the form of weaknesses and both internal and external threats. The four attributes of SWOT: Strengths - What are the advantages? What is currently done well? (e.g. key area of bestperforming activities of your company) Weaknesses - What could be improved? What is done badly? (e.g. key area where you are performing poorly) Opportunities - What good opportunities face the organization? (e.g. key area where your competitors are performing poorly) Threats - What obstacles does the organization face? (e.g. key area where your competitor will perform well) CATWOE This is used to prompt thinking about what the business is trying to achieve. Business perspectives help the business analyst to consider the impact of any proposed solution on the people involved. There are six elements of CATWOE
[5]

Customers - Who are the beneficiaries of the highest level business process and how does the issue affect them? Actors - Who is involved in the situation, who will be involved in implementing solutions and what will impact their success? Transformation Process - What processes or systems are affected by the issue? World View - What is the big picture and what are the wider impacts of the issue? Owner - Who owns the process or situation being investigated and what role will they play in the solution? Environmental Constraints - What are the constraints and limitations that will impact the solution and its success? de Bono's Six Thinking Hats This is often used in a brainstorming session to generate and analyse ideas and options. It is useful to encourage specific types of thinking and can be a convenient and symbolic way to request someone to switch gears". It involves restricting the group to only thinking in specific ways - giving ideas & analysis in the mood of the time. Also known as the Six Thinking Hats. White: Pure facts, logical. Green: Creative, emotional.

Yellow: Bright, optimistic, positive. Black: Negative, devils advocate. Red: Emotional. Blue: Cold, control. Not all colors / moods have to be used Five Why's Five Whys is used to get to the root of what is really happening in a single instance. For each answer given a further 'why' is asked. MoSCoW This is used to prioritize requirements by allocating an appropriate priority, gauging it against the validity of the requirement itself and its priority against other requirements. MoSCoW comprises: Must have - or else delivery will be a failure Should have - otherwise will have to adopt a workaround Could have - to increase delivery satisfaction Would like to have in the future - but won't have now Five Why's Five Whys is used to get to the root of what is really happening in a single instance. For each answer given a further 'why' is asked. MoSCoW This is used to prioritize requirements by allocating an appropriate priority, gauging it against the validity of the requirement itself and its priority against other requirements. MoSCoW comprises: Must have - or else delivery will be a failure Should have - otherwise will have to adopt a workaround Could have - to increase delivery satisfaction Would like to have in the future - but won't have now VPEC-T Main article: VPEC-T

This technique is used when analyzing the expectations of multiple parties having different views of a system in which they all have an interest in common, but have different priorities and different responsibilities. Values - constitute the objectives, beliefs and concerns of all parties participating. They may be financial, social, tangible and intangible Policies - constraints that govern what may be done and the manner in which it may be done Events - real-world proceedings that stimulate activity Content - the meaningful portion of the documents, conversations, messages, etc. that are produced and used by all aspects of business activity Trust - between users of the system and their right to access and change information within it

Roles of business analysts

As the scope of business analysis is very wide, there has been a tendency for business analysts to specialize in one of the three sets of activities which constitute the scope of business analysis, the primary role for business analysts is to identify business needs and provide solutions to business problems these are done as being a part of following set of activities. Strategist Organizations need to focus on strategic matters on a more or less continuous basis in the modern business world. Business analysts, serving this need, are well-versed in analyzing the strategic profile of the organization and its environment, advising senior management on suitable policies, and the effects of policy decisions. Architect Organizations may need to introduce change to solve business problems which may have been identified by the strategic analysis, referred to above. Business analysts contribute by analyzing objectives, processes and resources, and suggesting ways by which re-design (BPR), or improvements (BPI) could be made. Particular skills of this type of analyst are "soft skills", such as knowledge of the business, requirements engineering, stakeholder analysis, and some "hard skills", such as business process modeling. Although the role requires an awareness of technology and its uses, it is not an IT-focused role. Three elements are essential to this aspect of the business analysis effort: the redesign of core business processes; the application of enabling technologies to support the new core processes; and the management of organizational change. This aspect of business analysis is also called "business process improvement" (BPI), or "reengineering". Systems analyst

There is the need to align IT Development with the systems actually running in production for the Business. A long-standing problem in business is how to get the best return from IT investments, which are generally very expensive and of critical, often strategic, importance. IT departments, aware of the problem, often create a business analyst role to better understand, and define the requirements for their IT systems. Although there may be some overlap with the developer and testing roles, the focus is always on the IT part of the change process, and generally, this type of business analyst gets involved, only when a case for change has already been made and decided upon.

Organizational Structure of the Business Analysis Function

The role of Business Analysis can exist in a variety of structures within an organizational framework. Because Business Analysts typically act as a liaison between the business and technology functions of a company, the role can be often successful either aligned to a line of business, within IT or sometimes both. Business Alignment When Business Analysts report up through the business side, they are often subject matter experts for a specific line of business. These Business Analsysts typically work solely on project work for a particular business, pulling in Business Analysts from other areas for cross-functional projects. In this case, there are usually Business Systems Analysts on the IT side to focus on more technical requirements. IT Alignment In many cases, Business Analysts live solely within IT and they focus on both business and systems requirements for a project, consulting with various SMEs to ensure thorough understanding. Depending on the organizational structure, Business Analysts may be aligned to a specific development lab or they might be grouped together in a resource pool and allocated to various projects based on availability and expertise. The former builds specific subject matter expertise while the latter provides the ability to acquire cross-functional knowledge. Business Analysis Center of Excellence Whether Business Analysts are grouped together or are dispersed in terms of reporting structure, many companies have created Business Analysis Centers of Excellence. A Center of Excellence provides a framework by which all Business Analysts in an organization conduct their work, usually consisting of processes, procedures, templates and best practices. In additional to providing guidelines and deliverables, it also provides a forum to focus on continuous improvement for the Business Analysis function.

Business process improvement

A business process improvement (BPI) typically involves six steps: 1. Selection of process teams and leader Process teams, comprising 2-4 employees from various departments that are involved in the particular process, are set up. Each team selects a process team leader, typically the person who is responsible for running the respective process. 2. Process analysis training The selected process team members are trained in process analysis and documentation techniques. 3. Process analysis interview The members of the process teams conduct several interviews with people working along the processes. During the interview, they gather information about process structure, as well as process performance data. 4. Process documentation The interview results are used to draw a first process map. Previously existing process descriptions are reviewed and integrated, wherever possible. Possible process improvements, discussed during the interview, are integrated into the process maps. 5. Review cycle The draft documentation is then reviewed by the employees working in the process. Additional review cycles may be necessary in order to achieve a common view (mental image) of the process with all concerned employees. This stage is an iterative process. 6. Problem analysis A thorough analysis of process problems can then be conducted, based on the process map, and information gathered about the process. At this time of the project, process goal information from the strategy audit is available as well, and is used to derive measures for process improvement.

Identifying Business Needs

Includes the following steps: 1. Business definition 2. Understand business domain(s) 3. Organization goals 4. Core competence 5. Competitive stance [edit]Goal

of business analysis

Ultimately, business analysis want to achieve the following outcomes: Reduce waste Create solutions Complete projects on time Improve efficiency Document the right requirements

One way to assess these goals is to measure the return on investment (ROI) for all projects. According to Forrester Research, more than $100 billion is spent annually in the U.S. on custom and internally developed software projects. For all of these software development projects, keeping accurate data is important and business leaders are constantly asking for the return or ROI on a proposed project or at the conclusion of an active project. However, asking for the ROI without sufficient data of where value is created or destroyed may result with inaccurate projections. [edit]Reduce

waste and complete projects on time

See also: Project cancellation Project delays are costly in two different dimensions: Project costs For every month of delay, the project team continues to rack up costs and expenses. When a large part of the development team has been outsourced, the costs will start to add up quickly and are very visible if contracted on a time and materials basis (T&M). Fixed price contracts with external parties limit this risk. For internal resources, the costs of delays are not as readily apparent, unless time spent by resources is being tracked against the project, as labor costs are essentially fixed costs. Opportunity costs Opportunity costs come in two flavors lost revenue and unrealized expense reductions. Some projects are specifically undertaken with the purpose of driving new or additional revenues to the bottom line. For every month of delay, a company foregoes a month of this new revenue stream. The purpose of other projects is to improve efficiencies and reduce costs. Again, each month of failure postpones the realization of these expense reductions by another month. In the vast majority of cases, these opportunities are never captured or analyzed, resulting in misleading ROI calculations. Of the two opportunity costs, the lost revenue is the most egregious and the impacts are greater and longer lasting.

Improve project efficiency

Efficiency can be achieved in two ways: by reducing rework and by shortening project length.

Rework is a common industry headache and it has become so common at many organizations that it is often built into project budgets and time lines. It generally refers to extra work needed in a project to fix errors due to incomplete or missing requirements and can impact the entire software development process from definition to coding and testing. The need for rework can be reduced by ensuring that the requirements gathering and definition processes are thorough and by ensuring that the business and technical members of a project are involved in these processes from an early stage. Shortening project length presents two potential benefits. For every month that a project can be shortened, project resource costs can be diverted to other projects. This can lead to savings on the current project and lead to earlier start times of future projects (thus increasing revenue potential).