Business Analyst Training, Mentoring and Coaching

Business Analysts are responsible for gathering requirements on a project. Some of their key skills include requirement elicitation, good documentation and presentation, Visual modelling and critical thinking. The knowledge of tools for managing requirement is also essential.

 

This training will last 2 weeks and is classroom based. After this you will be placed within a project team as a Business Analyst on the project. This way you gain practical work experience.

Ideally, you should have some related previous work experience however new starters are welcome.

The training runs for 4 (Weeks). For the first two (2) weeks, delegates will focus on practicing what’s been done in the training classes (on Saturdays) through case studies. The next two (2) weeks would see the candidates implementing their acquired skills by working remotely on a live project.

Week 1

  • What is Business Analysis (BABOK version 3 – Business Analysis Body of Knowledge).
  • Understanding what Business Analysts do.
  • Breakdown of the Project Lifecycle (PLC) and Software Development Lifecycle (SDLC).
  • End-To-End Business Analysis techniques and functions across the Project and Software Development Lifecycle.
  • Understanding the requirement engineering process.
    • Elicitation (Featuring the demonstration of practical requirement elicitation techniques
    • Analysis
    • Validation
    • Documentation
    • Management
    • A breakdown of  Strategic, Tactical and Transitional requirement
    • The Tripartite view of Tactical requirements
    • User Interface (UI) view
    • Core User view
    • Process based view

CASE STUDY

    • User Interface (UI) requirements
    • Low-fidelity Wireframing

Week 2

    • Understanding Core User Requirements
    • Functional Requirements
    • Non-functional Requirements
    • User Requirement Documentation Styles (Waterfall vs. Agile)
    • The Use Case Approach
    • Use Cases and Usage Scenarios
    • User stories and Acceptance Criteria
    • The Agile Scrum Methodology and a clear understanding of the dynamic role of a Business Analyst in this framework
    • Fundamentals of Behaviour Driven Development

CASE STUDY

    • User Stories
    • Acceptance Criteria
    • Gherkin Syntax (Cucumber)
    • Affirmative style
    • Traditional Acceptance Criteria
    • Use Case and Usage Scenarios
    • Use Case Model

Week 3

    • Techniques for modelling Business Processes
    • Process Modelling, Process Re-engineering and Optimisation
    • UML modelling techniques
      •  Activity Diagram
      •  Context Diagram
      • Putting the Tripartite facets of requirements together via documentations
      • Demonstration of pre-solved process modelling case study prior to live project on-boarding

Live Project On-Boarding

    • In-class brainstorming session featuring
    • Top down approach to running brainstorming sessions (Business-Stakeholder-User requirement elicitation)
    • JRP facilitation
    • User Interface (UI) requirements
    • Low-fidelity Wireframing
    • User Stories
    • Acceptance Criteria
    • Gherkin Syntax (Cucumber)
    • Affirmative style
    • Traditional Acceptance Criteria
    • Use Case and Usage Scenarios
    • Use Case Model

Week 4

Capturing requirements for Data driven systems and solutions

    • Data Flow Diagrams (DFDs), Context-level DFDs, and Rigorous Physical Process Models (RPPM)
    • Data Schemas, Data Models and Entity-Relationship Diagrams
    • User Acceptance Testing
    • Demonstration of pre-solved Data Flow Diagram case study prior to live project on-boarding

Live Project On-Boarding

    • Data Flow Diagram and Data Models (Dependent on if specific project requires this detail of specification)
    • Expansion of already growing documentation from week 3 as stated below
    • User Interface (UI) requirements
    • Low-fidelity Wireframing
    • User Stories
    • Acceptance Criteria
    • Gherkin Syntax (Cucumber)
    • Affirmative style
    • Traditional Acceptance Criteria
    • Use Case and Usage Scenarios
    • Use Case Model
    • Process Models
    • Entity-Relationship Models
Delegates will learn how to
  • Contribute to the overall Scrum environment using BA skills
  • Create the Product Backlog from a business scenario
  • Contribute to Product Backlog prioritisation
  • Contribute to Product Backlog estimation
  • Help plan a sprint
  • Take part in / facilitate the Daily Scrum meeting
  • Control and monitor the burn-down charts
  • Take part in / facilitate the Scrum Review meeting
  • Take part in / facilitate the Scrum Retrospective meeting
  • Business Analyst
  • Agile Business Analyst
  • Junior Business Analyst
  • Title

    Business Analyst

  • Type

    Role Training Course

  • Location

     

  • Duration

     

    2 weeks
 classroom based training. Min of 3 months practical experience and you continue on the project until it’s delivered

  • Course Fees

    £899  VAT Inc.

UPCOMING BATCH

REGISTER NOW

£100

Payment will allow you book an upcoming Batch.
Registration Fee is part-payment & non-refundable.

SUBSCRIBE TO THIS COURSE


Course
Location