Business Analyst Training, Mentoring and Coaching

Business Analyst Training, Mentoring and Coaching

• LOCATION
 Manchester

• DURATION 3 weeks
classroom based training

  • Min of 12 weeks practical experience and you continue on the project until it’s delivered

COURSE FEES
 - _{was £999 (inc VAT)} - now ^{£799.20 (inc VAT)}

Overview

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

This training will last 3 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.

Training Prerequisite

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

Training Format & Setup

The training runs for 3 weeks, delegates will focus on practicing what’s been done in the training classes (on Saturdays) through case studies. Afterwards we will see the candidates implementing their acquired skills by working remotely on a live project.

Course Outline

WEEK 1

Session 1:

• Introduction to the Project Management environment

• PRINCE 2 Definition of Project

• Five Project Characteristics

• Six Project Variables

• Lunching your Project

•  Apply a Project Framework (PRINCE 2, SCRUM)

• PROJECT MANAGEMENT METHODOLOGY

• PRINCE 2

• Four integrated Elements of PRINCE2

• The Seven PRINCE2 Principles

• The Seven PRINCE2 Themes

• The Seven PRINCE2 Processes

• How does it apply?

• Establish Roles and Responsibilities within the project environment

• PLANING

• RACI Management

• RAID LOGS

• (RAG STATUS)

• Reporting

• Manage in Stages

• Create Stage Boundaries

• Stage Deliverables

• Stage Highlight Reports

• Approval and Progression

• Lesson Learned

Session 2: 

• Business Analysis

• Business Case

• Feasibility Study

• Requirements

• One-on-one interviews

• Facilitated sessions (Workshops)

• Questionnaires

• Prototyping

• Use cases

• Brainstorming

• Types of Requirement

• Functional

• Non-Functional

• Deliverables

• Prioritise user requirements – MOSCOW

• Organisational Structure

• Process Mapping

• Communication Structure

• Change Management

• Types of Change

• Change within a controlled Environment

• Change Management Tool

• Impact Assessment

• Quality Assurance

• The PMO environment

• Conclusion

WEEK 2

Session 3:

• 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

Session 4:

• 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

Session 5:

• 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

Session 6:

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

LEARNING OUTCOME

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

POTENTIAL JOB ROLES

• Business Analyst

• Agile Business Analyst

• Junior Business Analyst