IIBA Endorsed Business Analysis Course.

  Course Details (PDF)

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

Length: Approx 8 weeks/60 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 Classroom Training available)

A. Course Summary

This 60 to 65 hour 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, mini-projects/home works with home work 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]
  • Types of requirements (Business, Functional, Non-Functional, Transition, UI etc)
  • UML, Advanced UML [Unified Modeling Language]
  • Project Management for BA’s.
  • Tools like Axure, Quality Center or Version one, Visio (or STAR UML) and Enterprise Architect.
  • 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:

  • Students will learn how to write Functional Requirement Documents (FRDs), Use cases, 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. Contact us for more details:

Company name: Yes-M Systems
Phone numbers (USA): 678-643-7777
nanduv@gmail.com, nandu@myyesm.com
Kudzu Reviews:
Facebook: http://www.facebook.com/yesmsystems

C. About Yes-M Systems:

  1. Established in 2005 (Atlanta, GA, USA), 10th year in business.
  2. A+ accreditation from US Better Business Bureau (http://www.bbb.org/atlanta/business-reviews/internet-consultants/yes-m-systems-in-duluth-ga-27431372)
  3. Received the “Best of 2012” and “Best of 2013” awards from US-based Kudzu (http://www.kudzu.com/m/Yes-M-Systems-30363491/reviews/)
  4. Trained close to 3000+ students from all over the world.
  5. Experienced, passionate and committed trainers
  6. IT Training in various technologies including Java, Dot Net, SAP, Oracle, QA, BA etc (See Courses We offer section for more information)
  7. Professional guidance/help with resumes and interview preparations.
  8. Recruiter help with marketing/jobs
  9. Yes-M Systems Certification at the end of the training.

D. 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 phases will be covered in detail
2.2.    Rapid Application Development (RAD)
2.3.    Spiral
2.4.    Agile:
2.4.1.    Explain Agile    Scrum    Scrum Basics    Sprint    Product Backlog    Sprint Backlog    Burn down chart    Sprint Planning Meeting    Stand-up meeting.
2.5.    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.5.1.     User/Business Requirements
2.5.2.     Functional Requirements
2.5.3.     Non-Functional Requirements
2.5.4.    Transition Requirements
2.5.5.    UI (User Interface) requirements
2.5.6.    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.8.2.    Exercises (Documenting BRDs/FRDs) –  note – these exercises will be done throughout the course.    Exercise-1 – In class exercise    Exercise-3 – Homework-1 (HW1) – Airline Application-1    Exercise-3 – In class exercise    Exercise-4 – Homework-2 (HW2) – Airline Application-2    Exercise-5 – Homework-3 [if you complete HW1 and HW2] – Banking Application-1.
3.8.3.    Writing use cases    Exercise-6 – Write a use case – In class exercise    Exercise-7- Writing a use case – home work – Banking Application-2    Exercise-8 – Writing a use case – home work – Retail Application-1.
3.8.4.    Creation of User stories – User story and example    BA Tools: Visio, STAR UML, Enterprise Architect    Flow charts    Various UML diagrams     Usecase, Activity, State    Sequence, Behavioural    Process Flow diagrams/ Business process modelling
3.8.5.    Prototyping  using Axure (as listed in 3.3.6)
3.8.6.    JAD (as listed in 3.3.7)

3.9.    Project Management for BAs
3.9.1    Project Management for a BA
3.9.2    Why does a project need a BA and a PM – how the roles are similar and different
3.9.3    Project Charter and Project Plan
3.9.4    5 Processes in a Project and the brief overview of Inputs, Tools and Techniques and Outputs – PMBOK table.

3.10       Testing/Validation:
3.10.1    Why a BA must know testing
3.10.2    Test review/Test Plans
3.10.3     Manual Testing basics
3.10.4     Writing Test scripts
3.10.5     Types of Testing
3.10.6     Quality Center or Version 1 Overview.
3.10.7     UAT testing

3.11     SQL – Basic and Advanced
3.11.1    SQL Basics
3.11.2    Primary Key, Secondary Key, Foreign Key
3.11.3    Various Select Statements
3.11.4    Joins, Inserts, Updates, Delete
3.11.5     Count, Sum, Distinct,  Having,  Group By

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.

E.    Courses we offer:

A.    QA and BA courses:

  • QA [Quality Assurance or QA Testing]
  • BA [Business Analysis or Business Analyst]
  • QA and BA as a single course (Integrated QA+BA) at a reduced fee.
  • Advanced/specialization courses:
    a.   60-hour Selenium course with Core Java
    b.   ETL Testing
    c.   Advanced Mobile Testing
    d.   Advanced QTP
    e.   Any combination of a, b, c, d.
  • Certification QA
    a.   QTP
    b.   ISTQB
    c.   Quality Center
  • Healthcare and Finance specialization
    a.    Healthcare as a Domain Class
    b.    Healthcare BA [Business Analyst with specialization in Healthcare]
    c.    Healthcare QA [Business Analyst with specialization in Healthcare]
    d.    Healthcare QA [Quality Assurance or QA Testing]
    e.    Business analyst with Finance specialization.
    f.    Quality Assurance with Finance specialization

B.    Java courses:
        a.   Core Java
        b.   Advanced Java
        C.   Combination of Core Java and Advanced Java

C.   Healthcare and Finance specialization
      a.    Healthcare as a Domain Class
      b.    Healthcare BA [Business Analyst with specialization in Healthcare]
      c.    Healthcare QA [Business Analyst with specialization in Healthcare]
      d    Healthcare QA [Quality Assurance or QA Testing]
      e.    Business analyst with Finance specialization.
      f.    Quality Assurance with Finance specialization

D.    Microsoft Courses:
        a.    Dot Net
        b.    Microsoft Business Intelligence [MS BI]
        c.    Sharepoint
        d.    MS SQL Server

E.    SAP Courses:
        a.    SAP FICO
        b.    SAP MM
        c.    SAP HR
        d.    SAP BO
        e.    SAP BI
        f.    SAP HANA

F.    Oracle Courses:
        a.    Oracle Financial
        b.    Oracle DBA
        c.    PL/SQL

G.    Other Courses:
         a.    Hadoop
         b.    Hadoop with Java
         c.    Salesforce
         d.    Project Management (PMP)
         e.    Maximo
         f.    Tabeau
         g.    Informatica
         h.    Cognos

F.    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