Business Analysis Modules

Our modular approach allows you to create a training course by picking the specific modules that you require.

Target Audience

Modules are designed around 3 competency levels as defined by the BACA scheme.

  • Level 1 - Junior Business Analyst (from beginners up to 2 years experience)
  • Level 2 - Business Analyst (typically 1 to 5 years experience)
  • Level 3 - Senior Business Analyst (typically >4 years experience)

Where a module is described as 1-2, 2-3 or 1-3, it should be suitable for a range of levels of experience or can be tailored to a specific level. Our training consultants will be happy to advise you.

The number of delegates on each course is generally limited to a maximum of ten persons. Due to the practical nature of our courses, the effectiveness of the training is diluted by increasing the maximum number of delegates and is not generally recommended.

Approach

All modules have a practical bias with delegates being encouraged to learn through exercises and discussion about application of the learning in their own workplace.

Case study work and exercises are conducted in teams and delegates are encouraged to make short informal presentations at the end of each exercise to build their confidence.

Where relevant, delegates are supplied with simple checklists and deliverable templates to take back to their working environments and to put into use. These are based on our own experience of real world projects and serve as simple reminders when completing Business Analyst related tasks.

Instructors

All instructors are experienced Business Analysts with a minimum of 10 years experience across a broad range of industry sectors.

Module Duration

Each module has a specified duration but this can usually be tailored for a specific group. Around half the time for most modules will be devoted to practical exercises and/or group discussion.

Available modules (click for detail)


Available modules in detail

Module: Introduction to the Business Analyst Role

Level 1
Duration ½ day

Objectives /
Key Learning Points

Sets the context for Business Analysis and defines 4 basic rules of business analysis (note – this introductory module is recommended to start all Level 1 courses).
Module content

  • The role of the Business Analyst and how the role has evolved from the Systems Analyst Fundamental rules of Business Analysis
  • Business Analysis competencies
  • An introductory exercise in documenting requirements to illustrate the complexities involved in being a competent and effective Business Analyst



Module: The Project Lifecycle and the Business Analyst

Level 1
Duration ½ day

Objectives /
Key Learning Points

Provide an overview of the project lifecycle and demonstrate how the Business Analyst should be involved in all project phases. Examines how different types of project require different approaches.
Module content

  • Overview of ‘typical’ project phases
  • Project approaches such as Waterfall, Iterative and Agile – benefits and problems of different approaches
  • Deliverables produced by Business Analysts in different parts of the project lifecycle
  • How the Business Analyst fits into the ‘traditional’ project lifecycle
  • How approaches like Agile can affect the responsibilities of the Business Analyst



Module: Effective Interviewing

Level 1
Duration ½ day

Objectives /
Key Learning Points

Effective interviewing is about good listening skills. Different types of interview objective require different approaches and questioning technique.

Module content
  • The different user perceptions of IT and business change
  • Basic interviewing rules
  • Alternative approaches to interviewing
  • Practical Exercise: A role play interview session can be incorporated allowing each delegate to perform a one-to-one stakeholder interview



Module: Requirements Hierarchy and Types of Requirement

Level 1
Duration ½ day

Objectives /
Key Learning Points

Understand why different types of requirement are needed. The importance of distinguishing between high-level and detailed requirements.
Module content

  • Definition of requirements and why they need to be defined
  • Business requirements and Functional requirements
  • The importance of defining requirements at a high and low level of detail
  • Non-functional requirements and how to define them
  • The difference between requirements and solutions
  • Requirements checklist
  • Practical Exercise: Delegates are asked to define some different types of requirement from a short scenario.



Module: Requirements Elicitation Techniques

Level 1
Duration ½ day

Objectives /
Key Learning Points

Understand how different knowledge types can affect how requirements are gathered. Illustrates with examples how business stakeholders rarely understand the full set of requirements that are needed to provide a robust end-to-end solution and how the Business Analyst can drive their thinking
Module content

  • Different types of knowledge
  • Requirements workshops
  • Overview of Process modelling and data modelling and their relationship to requirements
  • Scenarios and Use Cases
  • Prototyping overview
  • Questionnaires and sampling
  • Practical Exercise: Delegates are presented with a number of business scenarios and asked to identify which elicitation techniques would be required to achieve the required outcome.




Module: Requirements Documentation Techniques

Level 1
Duration ½ day

Objectives /
Key Learning Points

This module illustrates the need for different approaches and levels of formality when documenting requirements. Examines how working with off-shore developers and third party vendors influences the way in which requirements are documented and levels of formality in sign-off. A pragmatic approach is required depending on the type of project undertaken.

Module content

  • Plain text example
  • Requirements Catalogue example
  • Process based example
  • Use Case example
  • CASE tools and Requirements Databases
  • Pro’s and Con’s of different approaches
  • Requirements style in Agile projects
  • Practical Exercise: Delegates are presented with a number of project scenarios and asked to define an appropriate documentation technique.



Module: Process Modelling Basics

Level 1
Duration ½ day (this module can be extended to 1 day where a more detailed knowledge is required).

Objectives /
Key Learning Points

Why process modelling is important to Business Analysts. How to draw basic process models using BPMN. The importance of having standards.

Module content

  • Definition of a process and a process model
  • How process modelling helps the Business Analyst
  • Process modelling as a requirements definition tool
  • Overview of BPMN
  • Instructor led exercise to develop a process model
  • Best practice for process modelling
  • Hints and Tips
  • Process modelling checklist
  • Practical Exercise: Delegates are asked to produce a simple swim-lane type diagram.



Module: Data Modelling Basics

Level 1
Duration ½ day (this module can be extended to 1 day where a more detailed knowledge is required).

Objectives /
Key Learning Points

How data modelling can be used to discover requirements that would not be discovered using any other technique. Construct a basic data model and interpret a data model. Identify attributes for entities.
Module content

  • What is a data/entity model
  • How data modelling helps the Business Analyst
  • Data modelling as a requirements definition tool
  • Entities, relationships and attributes
  • Instructor led exercise to develop a data model
  • Hints and Tips
  • Data modelling checklist
  • Practical Exercise: Delegates are asked to produce a simple data model.



Module: Getting from Requirements to Solutions

Level 1
Duration ½ day (this module can be extended to 1 day where a more detailed knowledge is required).

Objectives /
Key Learning Points

How the Business Analyst is the key facilitator between business users and delivery teams to ensure a robust and cost effective system is delivered. How to run a Delivery Transition Workshop.

How requirements are turned into solutions.

Module content

  • Prioritising and assessing requirements for delivery
  • Running a delivery transition workshop
  • Setting expectations
  • The importance of detailed requirements
  • Supporting IT development
  • Implications of off-shored and outsourced development
  • IT Transition Checklist
  • Practical Exercise: Role Play demonstration of Delivery Transition workshop.



Module: Supporting Business Implementation

Level 1
Duration ½ day (this module can be extended to 1 day where a more detailed knowledge is required).

Objectives /
Key Learning Points

The Business Analyst should support the business through all aspects of implementation.

Module content

  • Identifying business impact and relevant stakeholders
  • Aspects of business implementation
  • Business Implementation checklist
  • Practical Exercise: delegates are asked to identify potential business impact areas from the case study.



Module: Producing Use Case Diagrams and Descriptions

Level 1-2
Duration ½ – 1 day

Objectives /
Key Learning Points

Use cases can be used to drive business thinking and to validate and drive out requirements.

Module content

  • Drawing use case diagrams
  • Writing use case descriptions
  • Include and Extend constructs
  • Instructor led example of producing a use case diagram
  • Instructor led example of producing a use case description
  • Links with testing
  • Practical Exercise: Delegates are asked to produce a simple use case diagram and a use case description.



Module: Project Scoping and Definition Basics

Level 1 - 2
Duration ½ day

Objectives /
Key Learning Points

Project Definition lays the foundations for a successful project. Project objectives and scope must be clearly defined.

Module content

  • The importance of project definition/initiation
  • Contents of a PID/PDR
  • Defining SMART Objectives
  • Understanding project constraints
  • Quality criteria for IT systems
  • Project Scoping checklist
  • Practical Exercise: Delegates are asked to define objectives for the case study and an outline of scope and scoping questions that need to be asked of the Project Sponsor.



Module: Business Case Basics

Level 1 - 2
Duration ½ day

Objectives /
Key Learning Points

The importance and use of business cases. How to construct a simple business case.

Module content

  • Project roles in producing a business case
  • Constructing a basic business case
  • Identifying costs and benefits
  • Overview of NPV, IRR and ROI
  • Benefits realisation
  • Business Case checklist



Module: Effective Prototyping techniques

Level 1
Duration ½ day

Objectives /
Key Learning Points

Prototyping is an important (often under-used) part of IT development. Prototyping builds user confidence if done correctly. Prototyping as a process should be carefully planned and managed.
Module content

  • The importance of prototyping
  • Roles and responsibilities in prototyping
  • Planning a prototyping activity
  • Dangers of prototyping
  • Inputs to prototyping
  • Practical Exercise: Delegates are asked to produce some simple prototypes based on other project deliverables and with input from a business stakeholder.



Module: User Experience Basics

Level 1 - 2
Duration ½ - 1 day

Objectives /
Key Learning Points

A great user experience will reduce business costs. To define the importance of good user interface design and the Business Analysts role in ensuring that it is fit for purpose. Key principles of screen design as well as other types of user interface.

Module content

  • Importance of User Experience
  • Business Analyst responsibilities
  • Profiling your users
  • Examples of poor UI design
  • UI Design Principles
  • Prototyping techniques
  • Defining usability
  • Legal requirements
  • Practical Exercise: Delegates are asked to design the structure of a basic website including navigation flow and a number of specific screen designs.



Module: Ensuring Requirements Quality

Level 1 - 2
Duration 1 day

Objectives /
Key Learning Points

Each project should individually consider its quality criteria for requirements documentation. Quality must be considered from a business and a technical perspective.

Module content

  • Quality criteria for requirements
  • Objective and Requirements
  • Requirements documentation techniques
  • Requirements from a business perspective
  • Requirements quality from a technical perspective
  • Levels of requirement
  • Using Walkthroughs effectively
  • Practical Exercise: Delegates are asked to validate a number of requirement statements. A structured walkthrough exercise is carried out.



Module: User Acceptance Testing Basics

Level 1 - 2
Duration ½ - 1 day

Objectives /
Key Learning Points

User Acceptance Testing needs to be carefully planned and managed. Test scripts will be linked to requirements documents and use case descriptions. How the Business Analyst can manage issues between the business, testers and development teams.
Module content

  • Definition of User Acceptance Testing
  • User Acceptance Test Planning
  • Defining acceptance criteria
  • Use Cases and Scenarios
  • Test Scripting
  • Test Execution
  • UAT checklist
  • Practical Exercise: Delegates are asked to produce some simple scenario based UAT scripts.




Module: Agile Introductions

Level 1-3
Duration ½ - 1 day

Objectives /
Key Learning Points

Introduce the principles of Agile and how this may impact on the Business Analyst role and their deliverables.
Module content

  • Agile and Scrum overview
  • Sprints and Iterations
  • Roles in Agile
  • User Stories
  • Managing backlogs
  • Assigning business value
  • Practical Exercise: Delegates are asked to write some user stories with acceptance test conditions. An example Scrum meeting is held to demonstrate the principles of Scrum.



Module: Data Modelling Intermediate

Level 2 -3
Duration 1 day

Objectives /
Key Learning Points

A correct data model can reap vast benefits in future years but an incorrect data structure will impede the business for years to come.
Module content

  • Data Modelling Rules
    • Resolving many to manys
    • Resolving one to ones
  • Alternative data modelling styles
  • Defining attributes
  • Physical translation
    • Primary keys
    • Foreign keys
  • Data Modelling through the project lifecycle
  • Data Modelling Checklist



Module: Running Effective Requirements Workshops

Level 2 - 3
Duration 1 day

Objectives /
Key Learning Points

Following successful participation in this course, delegates will know how to organise, run, participate in, and facilitate workshops.
Module content

  • Planning and organising a workshop
  • Being an effective workshop participant
  • Facilitating a workshop
  • Approaches to running a workshop
  • Workshop Techniques (e.g. Process Diagrams, Mind-mapping, brainstorming)
  • The individual and the group
  • Recording and follow up
  • Practical Exercise: Practical session – Delegates are asked to prepare hold a workshop. Further practical exercises occur where a variety of workshops scenarios are presented for course attendees to deal with.



Module: Process Improvement and Redesign

Level 2 -3
Duration 1 day

Objectives /
Key Learning Points

Process improvement requires strong sponsorship and clear direction. Processes can be documented analysed and evaluated

Module content

  • Definition of a process
  • Initiating the improvement programme
  • Process effectiveness vs. process efficiency
  • Process diagramming using BPMN
  • Process Goals and Outcomes
  • The importance of metrics
  • Identifying value and waste
  • Analysing existing processes
  • Identifying improvements
  • Process Reengineering vs Process Improvement
  • Understanding human factors
  • Aligning process resources with the achievement of business objectives
  • Practical Exercise: Delegates are asked to evaluate and redesign an existing business process.




Module: Estimating for Requirements Analysis

Level 2 - 3
Duration 1 day

Objectives /
Key Learning Points

Breaking down a problem into its component parts assists more accurate estimates. Estimating is often done ‘finger in the air’ but specific techniques will produce more accurate estimates.
Module content

  • Problem breakdown
  • Influencing factors
  • Evaluating project risk
  • Estimating techniques
  • Planning Poker
  • Dealing with estimating conflicts
  • Estimating checklist
  • Practical Exercise: Delegates are asked to produce some estimates for a number of different project scenarios. A Planning Poker exercise is carried out.



Module: Writing and Executing System Test and User Acceptance Test scripts

Level 2
Duration ½ day

Objectives /
Key Learning Points

System and User Acceptance Testing have different objectives. Test scripts must be based on a number of different inputs. Business Analysts can help the testing process run more smoothly.
Module content

  • Testing Definitions
  • Testing Inputs
    • Requirements
    • Functional specifications
    • Use Cases
    • Process Models
    • Data Models
  • Overview of test management
  • Defining Acceptance Criteria
  • Writing System test scripts
  • Writing User Acceptance test scripts
  • Executing Scripts
  • Raising Faults
  • Testing Checklist
  • Practical Exercise: Delegates produce a basic requirements document, a use case diagram and a simple process diagram. They are later asked to produce some simple System and UAT scripts.




Module: Requirements Analysis for Package Solutions

Level 2 - 3
Duration 1 day

Objectives /
Key Learning Points

Dealing with package solutions requires the overall project approach to requirements to be evaluated. Relationships with package suppliers must be managed carefully and various other stakeholders must be involved.

Module content

  • Requirements approach
  • Requirements documentation
  • Identifying stakeholders
  • Dealing with package suppliers
  • Gap analysis
  • Solution evaluation and decision
  • Package customisation
  • On-going package maintenance
  • Procurement checklist
  • Practical Exercise: Delegates are asked to evaluate a number of potential package solution scenarios and to develop example requirements to be used for package evaluation. A gap analysis exercise is performed.




Module: Requirements Definition for Off-shored Development

Level 2 -3
Duration 1 day

Objectives /
Key Learning Points

Outsourcing and off-shoring of IT development require a different approach to requirements documentation.

Module content

  • Roles in off-shored development
  • Requirements approach
  • Requirements documentation
  • Defining high level requirements
  • Defining detailed requirements
  • Using Structured English
  • Stakeholder issues
  • Cultural issues
  • Practical Exercise: Delegates are asked to produce some high-level and detailed requirement examples.

» For more information call us now on 01943 830825 or send us a message online

« Business Analysis Training Main Page