IIBA Endorsed Business Analysis Course.

IIBA Endorsed Business Analysis Courseba-flyer-final-kudzu-updated

Length: 8-9 weeks / 85 Hours [65 Hours in class and 7 Real-time based Projects in Healthcare and Banking – 25+ Hours
Students with or without IT experience or knowledge
Student Location – To students from around the world
Delivery Method: Instructor-Led – Live online Training (Corporate and Classroom Training available)

A. Course Summary

This course is designed to give students a solid knowledge in the role and responsibility of a Business Analyst. Topics are reinforced with intense hands-on practices including in class exercises, 7 Real-time based with reviews/feedback. This course is taught by two experienced instructors (i) with 25+ years of IT experience and (ii) PMP certified professional with over 20 years of experience.

This course will allow the students to understand various BA concepts including:

  • 6 Knowledge areas of IIBA – Discuss Business Analysis, BA process, Role of a BA etc as per IIBA guidelines – 1. Enterprise Analysis, 2. Business Analysis Planning and Monitoring, 3. Elicitation, 4. Requirements Analysis, 5. Requirements Management and Communication, 6. Solution Assessment and Validation
  • Software development methodologies (waterfall, Agile, Spiral, RAD, Scrum)
  • Prototyping and JAD [Joint Application Development]
  • Prototyping and JAD [Joint Application Development]
  • Types of requirements (Business, Functional, Non-Functional, Transition, UI etc.)
  • UML, Advanced UML [Unified Modeling Language
  • Project Management for BA’s.
  • Tools like Axure, JIRA, Quality Center and Visio (or STAR UML)
  • UML, Advanced UML [Unified Modeling Language]
  • Manual testing hands-on, related theory and SQL.
  • Interview Questions and Resume Preparation sessions.

Projects/mini-projects/Hands-on sessions via class work and/or home work:

  • 7 Projects in Healthcare and Banking. Students will learn how to write Functional Requirement Documents (FRDs), Use cases, EPIC/Agile Stories.
  • UML diagrams
  • Creating mock-up screens (wireframes) using Axure
  • Flowcharting using Visio or STAR UML
  • Business process modelling/Process flow diagrams
  • Testing and Writing Test cases
  • Writing SQL queries

B. IIBA Endorsed Business Analysis Course Details:

1.    Introduction:
1.1.     Introduction IIBA, BABOK
1.2.     Introduction to BA roles/responsibilities.
1.2.1.      What is Business Analysis
1.2.2.      Role of a Business Analyst

2.    System Development Methodologies [Part of 3.2]
2.1.    Waterfall method
2.1.1.  Various SDLC phases will be covered in detail
2.1.2.  Requirement Phase/BA’s role – covered in detail
2.2.   Rapid Application Development (RAD)
2.3.    Spiral
2.4.    Agile: Explain Agile
2.4.1.     Scrum    Scrum Basics    Sprint    Product Backlog    Sprint Backlog    Burn down chart    Sprint Planning Meeting    Stand-up meeting.
2.5.     Agile and JIRA
2.5.1.     JIRA – Introduction
2.5.2.     JIRA tool registration( Trail Version)
2.5.3.     JIRA – Dashboard
2.5.4.    Managing Product backlog
2.5.5.    Sprint Creation
2.5.6.    Managing Sprint Backlog
2.5.7.    Creating sub tasks
2.5.8.    Sprint Progress and logging work
2.5.9.    Reporting defects
2.5.10.   Sprint Closer
2.6     Introduction to Various Requirement types [Note – some of these topics will be taught along with methodologies like waterfall
or Agile or will be taught later in the course. Just explicitly documenting that these topics will be covered)
2.6.2     User/Business Requirements
2.6.3     Functional Requirements
2.6.4.     Non-Functional Requirements
2.6.5.     Transition Requirements
2.6.5.     UI (User Interface) requirements
2.6.7.     System Requirements

3.    Business Analysis Process:
3.1      Enterprise Analysis:
3.1.1.    Define Business Need:    Identify Business goal/Objectives    Identify the Business problem    Desired Outcome    Define/Document Business need
3.1.2.    Assess Capability Gaps    Analyze current capability    Identify Gaps – problems/limitations    New capabilities required to meet the business need
3.1.3.    Determine Solution    Identify Solutions    Identify methodology/Life-Cycle    Assess organization capability    Define Solution Approach
3.1.4.    Define Solution/Scope (Project or Iteration)
3.1.5.    Define Business Case:    Feasibility Study    Costs, time, manpower, value/Benefits etc.    Other things to consider for an external product    Analyzing competition    Understanding the market

3.2.      Business Analysis Planning and Monitoring:
3.2.1.    Select business analysis approach    Understand Existing process/objectives/factors.    Plan Driven vs. Change Driven    Discuss various methodologies [as in  System Development Methodologies]    Requirements for the current project    Analyze Deliverables    Prioritization    Change Management    Stakeholders and Approvals.    Tools    Complexity of the project.     Conduct Stakeholder analysis    Who should participate    How many? The number of users.    Indentify the business unit    Understand their approval level    RACI Matrix    Plan Business Analysis Activities    Identify business analysis deliverables    Determine Scope of work    When/What work will be done.    Develop Estimates    Plan Business Analysis Communication    Type of requirement documents    Elicitation techniques    Communicate – Who/what/when/how    Business Analysis Communication Plan    Plan Requirements Management Process    Plan how changes are handled – Change Management    Plan how changes are prioritized/approved    Plan Traceability    Manage Business Analysis Performance    Track, Report and corrective actions.

3.3.      Elicitation:
3.3.1.       Prepare for Requirement Gathering    Review/Understand Business needs/requirements    Plan what/when needs to be gathered    Identify who needs to be involved in this process
3.3.2.    Conduct Requirement Gathering    Gather Requirements from the users/clients    Discuss various techniques used for gathering    Interview, Brainstorming, Focus Gps, JAD etc.    Other information to consider:    Tracing requirements    Capture Attributes like Priority    Attributes of a good requirement     Where to collect the requirements
3.3.3.    Document Elicitation Results:    Meeting minutes/other written documents/recordings    Document Requirements    Document open issues/concerns/questions
3.3.4.    Confirm Elicitation    Review Requirements with the stakeholder    Get approval from Stakeholders
3.3.5.    Other:
3.3.6.    Prototyping (wireframe):    Explain Prototyping    Homework using Axure tool    Create a mock up screen using a prototyping tool
3.3.7.    Joint Application Development [JAD]    JAD discussion    Role of a BA    Key Participants    Steps for a successful JAD session    Mock JAD Session

3.4.     Requirements Analysis:
3.4.1.    Prioritize Requirements    Basis for Prioritization    Challenges.    Discuss MOSCOW    Timeboxing/Budgeting
3.4.2.    Organize Requirements    Guidelines for organizing requirements    Level of Abstraction    Model selection    Why Models    Modeling Concepts    Techniques    Data Modeling    Process Flow Diagrams/Business Process Modeling    Use cases    User Story boarding
3.4.3.    Specify and Model Requirements    Writing requirements (Stakeholder/Solution)    Guidelines    Matrix Documentation    Process modeling, prototyping, use cases, UML Diagrams    Define attributes.
3.4.4.    Define Assumptions and Constraints    Document Assumptions    Document Constraints    Business    Technical
3.4.5.    Verify Requirements    Check for Quality    Various verification activities    Reviews:    Internal Review    Customer/SME/Stakeholder Review    Team Review: BA, Customer/SME, Technology Teams
3.4.6.    Validate Requirements    Business Value:    Techniques for validating requirements    Deliver value to customers?    Aligned with business goals and objectives?

3.5.     Requirements Management and Communication
3.5.1.    Manage Solution Scope & Requirements    Formal walk-through with the stakeholders    Getting the approval from the stakeholders    Changes:        Baselining requirements        Change Management vs. Change Driven
3.5.2.    Manage Requirements Traceability    Identify and document    Backward traceability    Forward traceability    Benefits:    Impact Analysis    Requirements Coverage    Requirements Allocation
3.5.3.    Maintain Requirements for Re-use
3.5.4.    Prepare Requirements Package    (Possible) List of documents in a package    Documents for Vendor Selection
3.5.5.    Communicate Requirements    General Communication    Enterprise Analysis Tasks    Elicitation Tasks    Requirements Analysis Tasks    Solution Assessment and Validation Tasks    Handling a Presentation    Who is involved in this process

3.6.     Solution Assessment and Validation
3.6.1.    Assess Proposed Solution    Assessing a single solution    Assessing multiple solutions    Selecting a solution
3.6.2.    Allocate Requirements    Solution components    Release handling
3.6.3.    Assess Organizational Readiness    Cultural Assessment    Operational or Technical Assessment    Training    Documentation    Stakeholder Impact Analysis
3.6.4.    Define Transition Requirements    What is Transition Requirements    Why it is needed
3.6.5.    Validate Solution    Investigate Defective Solution Outputs    Requirement    or    Application    Assess Defects and Issues
3.6.6.    Evaluate Solution Performance    Post-implementation assessment    Understand and evaluate the value of the solution    Solution Replacement or Elimination

3.7.      Underlying Competencies
3.7.1    Analytical Thinking and Problem Solving
3.7.2    Behavioral Characteristics
3.7.3    Business Knowledge
3.7.4    Communication Skills
3.7.5    Interaction Skills
3.7.6    Software Applications

3.8.      Techniques and Hands-on BA exercises are listed here.    Techniques    Decision Analysis    Estimation    Metrics and Key Performance Indicators    Risk Analysis    SWOT Analysis    Vendor Assessment

3.9.      7 Real-Time Projects: (Documenting BRDs/FRDs/Use Cases/EPICs/Stories): note – These Projects will be done throughout the course.
3.9.1.      Project-1 – Creating a mock-up screen for a Healthcare application
3.9.2.     In class exercise for Project-2.
3.9.3.     Project-2 – Airline Application – Writing an FRD/BRD
3.9.4     In class exercise for Project-3.
3.9.5    Project-3 – Healthcare Application – Writing an FRD/BRD.
3.9.6.      Project-4 – Banking Application – Writing an FRD/BRD.
3.9.7.     In class exercise for Project-5.
3.9.8.     Project-5 – Banking Application – Writing a Usecase/UML diagram
3.9.9     Project-6 – Healthcare Application – Writing a Usecase/UML diagram
3.9.10   Project-7 – Healthcare Application – Agile-based – Writing EPICs/Stories
3.9.11   Project-8 – Banking Application – Agile-based – Writing EPICs/Stories. Completing various types of diagrams using Visio

3.10.    Project Management for BAs
3.10.1    Project Management for a BA
3.10.2    Why does a project need a BA and a PM – how the roles are similar and different
3.10.3    Project Charter and Project Plan
3.10.4    5 Processes in a Project and the brief overview of Inputs, Tools and Techniques and Outputs – PMBOK table.

4.0       Software Testing Life Cycle
4.1.1      Test Plan Preparation      Test Case Design      What is testing? Why to test?      What is a test case?      How to develop test cases from IT requirements?      Test Case Design Techniques      Test Cases: In class 9 to 10 Manual Testing Exercises and Homework     Cover real-time applications.
4.1.2      Test Execution
4.1.3      Defect Reporting      What is Defect?      Bug Life Cycle      Defect Log Format      Understanding Priority and Severity      Example
4.2      Test Report preparation
4.3     Testing Types
4.3.1     White box testing
4.3.2      Blackbox testing      Functional      Smoke Testing      System Testing      End to End Testing      Regression Testing      Retesting      Concurrency Testing      Exploratory Testing      Compatibility Testing      User Acceptance (UAT) Testing      Non Functional Testing      GUI Testing      Performance testing      Security Testing

5 SQL and Advanced SQL
5.1      Introduction to SQL
5.1.1     SQL
5.1.2      Database
5.1.3     Table, Rows and Columns
5.1.4     Data Types
5.1.5     Primary Key, Alternate/Secondary Keys/NOT NULL/UNIQUE/CHECK and Foreign Keys
5.2     Statements:
5.2.1      SQL
5.2.2      Select and Select *
5.2.3      Column Alias, Null Value, Arithmetic Expressions
5.2.4     Concatenation Operator(||), Literal, DISTINCT
5.2.5     Where
5.2.6      Order By (Desc, Asc)
5.2.7      And & OR, Like
5.2.8      Not
5.2.9      IN
5.2.10      Not In
5.2.11      Insert, Update, Delete
5.2.12      DESCRIBE
5.3      Advanced SQL with Oracle
5.3.1      SQL commands:
5.3.2      Update, Delete
5.3.3      Create, Alter, Drop
5.3.4      Truncate, Select with various operators,
5.3.5      Count, Sum, Distinct,
5.3.6      Order by, Group by, Having
5.3.7      Working With Dates
5.3.8      Sub Query
5.3.9     Introduction to Joins      Inner Join      Self Join      Outer Joins – Left/Right/Full
5.3.10      Hands on all above with Oracle APEX online
5.4     Why QA professionals need to know SQL basics
5.4.1      Sample queries for data verification
5.4.2      acquiring test data
5.4.3      SQL Injection attack
5.4.4      What to test in Relational DB apps

6. Quality Center tool
6.1      Introducing Quality Center
6.1.1      The Quality Center Testing Process
6.1.2      Starting Quality Center
6.1.3      The Quality Center Window
6.2      Specifying Releases and Cycles
6.2.1     Defining Releases and Cycles
6.2.2     Viewing Releases and Cycles
6.3      Specifying Requirements
6.3.1      Defining Requirements
6.3.2      Viewing Requirements
6.3.3      Modifying Requirements
6.4      Planning Tests
6.4.1      Developing a Test Plan Tree
6.4.2      Designing Test Steps
6.4.3      Copying Test Steps
6.4.4     Calling Tests with Parameters
6.4.5      Creating and Viewing Requirements Coverage
6.5      Running Tests
6.5.1      Defining Test Sets
6.5.2     Adding Tests to a Test Set
6.5.3     Running Tests Manually
6.5.4      Viewing and Analyzing Test Results
6.6      Adding and Tracking Defects
6.6.1      How to Track Defects
6.6.2      Adding New Defects
6.6.3      Updating Defects

Disclaimer: Yes-M Systems and/or their instructors reserve the right to make any changes to the syllabus as deemed necessary to best fulfill the course objectives. Students registered for this course will be made aware of any changes in a timely fashion using reasonable means.


C.    BA Instructor Profiles:

Instructor 1 (Nandu): M.B.A (University of Alabama), M.S (Operations Research and Computer Applications)

  •  IT Experience: 25+ years of experience in variety of areas that includes Training, Design, Development, Product Manager, Sr. Business Analyst, QA, IT Audit and Security.
  •  Companies worked for (Consulting or as an Employee): IBM, EDS, BellSouth, Cingular, Sprint-Nextel, United Healthcare, and several start-ups.
  •  CISA (Certified Information Systems Auditor)
  •  CISM (Certified Information Systems Manager)


Back to Top
Call for Enquiry