THE ROLE OF BUSINESS ANALYSIS IN IT OUTSOURCING by YURII SAVHUK

Сontents: 1. What is business analysis? 2. Who is business analyst? 3. What are the roles and responsibilities of BA in outsource projects? 4. DOs & DO NOTs of BA 5. Skill required for BA. 6. What is SDLC and How BA is involved in each Phase? 7. UML Diagrams. 8. Requirements of BA.

Lets talk about the Business part of Business Analysis

Why Business Analysis is so important? Projects fail because the outcome is not as desired by business and business analysis is the bridge between the outcome and the need

BUSINESS BUSINESS ANALYST TECHNOLOGY

Role of the Business Analyst Usually assigned to the project after it has started Responsible for bridging the gap between the Business and IT Learn the business inside and out Essentially the architect of effective business systems Job title, definition and responsibilities viewed inconsistently across the industry

Some of the responsibilities of BA

BUSINESS ANALYSIS : Business analysis is a research discipline of identifying business needs and determining solutions to business problems. o The person who carries out this task is called a business analyst or BA. (or) o Business Analyst is the Bridge between Stake Holder and the Developers.

ROLES AND RESPONSIBILITIES OF BA: Plan Requirements Gathering Multiple Solutions Support after Implementation Verification of Solution Knowledge transfer to developers Software Document preparation Test case Preparation As-Is to be Scenario Gap Analysis Define the Scope using optimum Solution

PM & BA

Skills Comparison - Similarities Project Manager Strong communication skills Understanding of the SDLC Negotiation/ consensus building Strong interpersonal and client management skills Business Analyst Strong communication skills Understanding of the SDLC Negotiation/ consensus building Strong interpersonal and client management skills

Skills Comparison - Differences PM Ability to see the big picture for the project Directs project team Helps people (project team) get things done Ensures the product is delivered on time, within budget BA Detail-oriented Listens to people (SMEs) Helps SMEs describe how and why they perform tasks Ensures the product is built right according to the requirements

Skills Comparison - Differences PM Removes issue barriers Manages project change control Manages the Work Breakdown Structure (WBS) Management skills BA Identifies business issues Manages requirements change requests Performs requirements-related tasks in the WBS Investigative skills

How do a PM and a BA Work Together? Fundamentally, the PM manages project resources (people, money) and the BA manages the business stakeholders The BA reports to the PM on a project These two roles have significant overlap of responsibilities in certain areas Excellent PMs and BAs will work hand-in-hand to make the most of each others strengths

How do a PM and a BA Work Together? Areas of overlapping responsibilities Project scope definition Project statement of purpose Project objectives Project business risks Client relationship Communication with SMEs and technical team Review of requirements, designs and plans

How do a PM and a BA Work Together? Areas of clear delineation of responsibilities Business Analyst Gathering, documenting and reviewing business requirements from SMEs Translating business requirements into functional system specifications to be developed by the technical team Testing the solution, training SMEs on the new system and documenting new procedures Project Manager Plan and organize projects determining scope, deliverables, milestones, schedule, resources Manage project scope, risk, issue, communication, quality and cost Interact, collaborate, and negotiate with all project stakeholders and business partners/clients

DOS & DONTS OF BUSINESS ANALYST: Never say NO to the client. Never assume or imagine about anything being a business analyst. Confirm even the very minute details. Each and every communication that is made should only be through the official s or the corporate s. Ask the client for the MOTTO of each and every functionality.

SKILLS REQUIRED FOR BA: Analytical thinking and Problem solving - Creative Thinking - Learning - Decision Making - Problem Solving Business Knowledge - Business Principles and Practices - Industry Knowledge - Solution Knowledge Interaction Skills - Facilitation and Negotiation - Teamwork - Leadership and Influencing Communication Skills - Oral - Listening - Teaching - Written Software Applications - Generalized - Specialized Behavioral Characteristics

SDLC AND DIFFERENT MODELS IN SDLC: A Software Development Life Cycle is essentially a series of steps, or phases, that provide a model for the development and lifecycle management of an application or piece of software. Types of SDLC Models: - Water fall Model - Spiral Model - Iterative Model - V-Model - Big Bang Model - Agile Model - RAD(Rapid Application Development)Model - Software Prototype

Business Analyst Techniques: GAP Analysis SWOT Analysis RISK Analysis Root Cause Analysis

SWOT ANALYSIS: IT IS A STRATEGIC PLAN USED TO EVALUATE S TRENGTH, W EAKNESS, O PPORTUNITY AND T HREATS INVOLVED IN A PROJECT

GAP ANALYSIS Difference Between Current state and Proposed state - Where are we? - Where do we want to be?

RISK ANALYSIS:

ROOT CAUSE ANALYSIS:

REQUIREMENTS OF BA: Requirements are defined as the conditions or statements which meet the demands of the client and the stakeholders. Functional Requirements: - These statements explain the different aspects of the application/software to be developed. - It describes that What the System should do. Non-Functional Requirements: - The non-functional requirements are defined to explain the different abilities of the software developed. - Non-Functional Requirement Types also called ilities Availability Usability and Reusability Reliability Flexibility Supportability Performance Functional+Non-Functional=Complete Requirements

Thank you!!

Why Does a Project Need a PM and a BA? Having both a Project Manager (PM) and a Business Analyst (BA) is critical to a projects success. Each role provides specialized capabilities that can make the difference between a project that succeeds and one that struggles. The PM and BA each play distinct, critical roles on a project Both have a common ultimate goal, but focus on different aspects to achieve it It is difficult to wear both hats effectively on the same project The roles often intersect but also diverge