Business Analyst Training
Business analyst is someone who analyzes an organization or business domain (real or hypothetical) and documents its business, processes, or systems, assessing the business model or its integration with technology. However, organizational titles vary such as analyst, business analyst, business systems analyst or maybe systems analyst.
- Bachelor’s degree programs in finance, accounting or business administration or degree program in any discipline.
Business Analysis Introduction
- What is a Business Analyst?
- Why become a Business Analyst?
- Role and Core Competencies of the Business Analyst
- What is Project and Why Project Initiates
- End to the End Process flow of IT Projects
System/Software Development Life Cycle
- SDLC: Waterfall v/s Agile • Business Analysis milestones in SDLC
- Understanding the IT Project Formation
- IT Project Success & Failures • Work Breakdown Structure in SDLC
- Stakeholders Identification & Success Criteria
Project Document Review
- Business Case
- Project Charter
- Stakeholder Analysis Document
- RACI Matrix, BRD, USE Cases
Test Plan, Test Strategy
- Test Cases, UAT Plan
- Lesson Learned Document
- Project Completion Report
- Importance of Release Planning
- Difference between Weekly, Monthly and Emergency Releases
Environments: Development, QA, UAT, PILOT & LIVE
- End to End Process Flow of Various Environments
- Coordination with Infrastructure/Deployment Team
SCRUM BA Process & Techniques
- How Business Analysis Process is Different in Agile Model?
- What is Agile Development Model?
- The Role of BA in Agile Projects
Mapping BA Techniques to Agile
- Forming the Agile Team Structure
- User Stories: Story Decomposition, Story Elaboration, Story Acceptance Criteria
- Meetings: Sprint Planning, Backlog Grooming, Sprint Review, Demo, Retrospective
- Introduction to JIRA
- Why Business Analysts use JIRA
Hands-On Practice: Agile SCRUM Role Play Session & JIRA Tool
- Installation of JIRA (Please install this on your computer)
- Creating Product Backlog: EPIC, User Stories, Tasks, Bug
- Opening/Closing Sprint • Story Writing on JIRA with “Given, Then, When” Technique
- Defining Acceptance Criteria in User Stories
- Story Estimations with Poker Planning
- Role Play Session for Stand-Up Meetings, Sprint Planning, Retrospective and Demo
LIVE Project - Initiation and Planning
- Understand Project Objective
- Build an understanding of Business Requirements
- Decompose Business Requirements into Functional and Non-Functional Requirements
- Plan Business Analysis Approach
- Plan Stakeholder Engagement
- Plan Business Analysis Governance
- Plan Business Analysis Information Management
- Identify Business Plan Business Analysis Performance Improvements
- Hands-On Practice: Project Artifacts Development and Review
- Build Project Team Structure
- Plan Business Analysis Documents to be Prepared
- Develop a Business Requirements Document (BRD)
- Develop Use Cases and Use Case Diagrams
- Develop a Functional Requirement Document (FRD)
- Develop System/Software Requirement Specification Document (SRS)
- Develop Mock Up’s for GUI Requirements
- Project Documents Review & Approvals
- Review and Improve Business Requirements Document (BRD)
- Analyze & Update System/Software Requirement Specification Document
- Assessment of Use Cases and Use Case Diagrams
- Evaluate Mock Up’s for GUI Requirements
- Formal Sign-off on Documents Approval
Introduction to SQL & SAS
- Structured Query Language, User Acceptance Testing
- Introduction to Database and RDBMS
- DML Commands (Insert, Select, Update, Delete)
- DDL Commands (Create, Use, Alter, Drop)
- Other DB Utilities Toad, SQL Navigator etc.
- Role of a Business Analyst in the Testing Phase
- Importance of User Acceptance Testing
User Acceptance Testing and Evaluation of Definition Techniques
- Prepare Master Test Scenarios for UAT
- Alternate Flows & Exception Flows
- ​How Use Case Diagrams Show Relationships
- ​Paths and Scenarios
Use Case Diagrams
- Class Diagrams
- ​Sequence Diagrams
- ​Activity Diagrams
- ​Introduction to Rational Suite & MS Vision
- Change Management
- ​An examination of why people resist change
- How Requirements become Un-Managed
- ​BA’s role in managing change
- ​Requirements Traceability & Change Control
- ​When Requirements Collide: Alternative Decision-Making Approaches
- ​How much time should be spent on Requirements
- ​Implementing Just enough Requirements
- Understand and prepare each project story
Resume Preparation
- Mock Interview Session
- Final Resume Review
- Canadian Job Market Guidance
- Develop Key Strategies to Get the First Break in Business Analyst Role
- BA Best Practice
- Certification Discussion