Courses

Public Schedule

Mon/Tue – BA Foundation £795

Wed – Agile Methodology £395

Thu/Fri – BA Practitioner £795

Glasgow/Edinburgh/Newcastle/Manchester/Leeds/London/Bristol + one week off – 8 week cycles

Payment due on booking, 10 days notice required for cancellation or no refunds



Private Training



£495/day (+ Expenses)

Choose from Training Course/Contents, mix & match different topics, Up to 8 attendees, at your own location (UK only)

Booked and confirmed on receipt of a PO – Payment due within 7 Days or 10 Days prior to delivery whichever is first.

***All prices exclude VAT***

Business Analysis Foundation

Audience



Business analysts, business managers and their staff, business change managers, project managers and developers.

Prerequisites



There are no prerequisites for this course.

Duration



2 days. Lecture presentations are supported by group practical work which allows discussion, reinforcement of learning and enhancement of the understanding process.

Course Objectives



This course has been independently developed but follows the BCS Business Analysis Foundation syllabus. Course fees do not include the BCS examination which may be taken at any PearsonVUE testing centre. At the end of the course, delegates should be able to demonstrate knowledge and understanding of business analysis principles and techniques in the following areas:

  • The role and competencies of a business analyst.
  • Strategy analysis.
  • Business system and business process modeling.
  • Stakeholder analysis.
  • Investigation and modelling techniques.
  • Requirements engineering.
  • Business case development.
  • Management of business change.


Course Content


What is Business Analysis?

  • The origins of business analysis.
  • The development of business analysis.
  • The scope of business analysis work.
  • Taking an holistic approach.
  • The role and responsibilities of a business analyst.


The Competencies of a Business Analyst

  • Behavioural skills and personal qualities.
  • Business knowledge.
  • Techniques.
  • The development of competencies.

Strategy Analysis

  • The context for strategy.
  • The definition of strategy.
  • Strategy development.
  • External environment analysis – PESTLE and Porter's 5-Forces model.
  • Internal environment analysis – MOST, Resource Audit and Boston Box.
  • SWOT
  • Executing strategy – McKinsey 7-S Model, the Balanced Business Scorecard, critical success factors, key performance indicators


The Business Analysis Process Model

  • An approach to problem-solving.
  • Stages of the business analysis process model.
  • Objectives of the process model stages.
  • Procedure for each process model stage.
  • Techniques used within each process model stage.


Investigation Techniques

  • Interviews.
  • Workshops.
  • Observation.
  • Scenarios.
  • Prototyping.
  • Quantitative approaches.
  • Documenting the current business situation.


Stakeholder Analysis and Management

  • Stakeholder categories and identification.
  • Analysing stakeholders.
  • Stakeholder management strategies.
  • Managing stakeholders.
  • Understanding stakeholder perspectives.
  • Business activity models.


Modelling Business Processes

  • Organisational context.
  • An alternative view of an organisation.
  • The organisational view of business processes.
  • Value propositions.
  • Process models.
  • Analysing the as-is business process model.
  • Improving business processes (to-be business process).
Defining the Solution

  • Gap analysis.
  • Introduction to business architecture.
  • Definition of business architecture.
  • Business Architecture techniques.


Making a Business and Financial Case The business case in the project lifecycle

  • Identifying options.
  • Assessing project feasibility – Business, Technical and Financial feasibility.
  • Structure of a business case.
  • Investment appraisal - Payback, Discounted Cash Flow and Internal rate of return.


Establishing the Requirements

  • A framework for requirements engineering.
  • Actors in requirements engineering.
  • Requirements elicitation.
  • Requirements analysis.
  • Validating requirements.


Documenting and Managing Requirements

  • The requirements document.
  • The requirements catalogue.
  • Managing requirements.


Modelling Requirements

  • Modelling system functions – use case diagrams.
  • Modelling system data - entity relationship diagrams, class models.


Delivering the Requirements

  • Delivering the Solution.
  • Context.
  • Lifecycles - waterfall, V model, incremental, iterative.


Delivering the Business Solution

  • BA role in the business change lifecycle.
  • Design stage.
  • Implementation stage.
  • Realisation stage.


Business Analysis Practice

Audience


Business analysts, systems analysts and anyone involved in the analysis, investigation or improvement of business systems and processes.

Prerequisites


Attendance on the Business Analysis Foundation course or equivalent knowledge and experience.

Duration


2 days. Lecture presentations are supported by group practical work which allows discussion, reinforcement of learning and enhancement of the understanding process.

Course Objectives


This course has been independently developed but follows the BCS Business Analysis Practice syllabus. Course fees do not include the BCS examination. At the end of the course, delegates should be able to:

  • Describe how a business strategy is developed.
  • Apply strategic analysis techniques.
  • Explain the need for project discipline.
  • Explain techniques to investigate an organisation's business systems.
  • Describe an approach to improving business systems.
  • Explain the importance of stakeholder management and use a stakeholder analysis technique.
  • Use techniques for the analysis and conceptual modelling of business systems.
  • Describe how recommendations for business improvement may be identified.
  • Describe the contents of a rigorous business case for the development and implementation of business changes.
  • Identify costs, benefits, impacts and risks for an option in a business case.

Course Content



Rationale
  • A lifecycle for business change – alignment, definition, design, implementation and realisation.
  • The role of the Business Analyst within the lifecycle for business change.
  • Other roles within the lifecycle for business change.
  • The framework for business analysis activities.

Understanding the Strategic Context
  • Internal environment analysis.
  • External environment analysis.
  • SWOT analysis.
  • Critical Success Factors and Key Performance Indicators and Performance Targets.
  • The Balanced Business Scorecard as a framework for identifying Critical Success Factors and Key Performance Indicators.

Project Discipline for Business Analysis Studies
  • Terms of Reference/Project Initiation.
  • Business and project objectives.

Understanding the Situation/Issues
  • Stakeholder identification.
  • Overview of investigative techniques.
  • Representing a holistic view of the business situation.

Analysing Stakeholder Perspectives
  • Stakeholder analysis.
  • Identifying different perspectives.
  • Defining perspectives.

Analysing and Modelling Business Activities
  • Developing a conceptual business activity model from a perspective.
  • Identifying activities.
  • Identifying dependencies.

Identifying business events
  • External.
  • Internal.
  • Time-based.

Analysing business rules
  • External constraints.
  • Internal policies.
  • Internal procedures.
  • Building consensus by resolving conflicts.

Identifying Potential Solutions
  • Gap analysis – comparing the ideal and existing systems.
  • Defining a new business model.
  • Identifying IS/IT requirements to support the new business model.

Making the Business Case
  • Structure of a business case.
  • Identifying and shortlisting options for business change.
  • Identifying and categorising costs and benefits.
  • Identifying and categorising risks and approaches to their management.
  • Identifying impacts.
  • The lifecycle for the business case.

Agile in a Day


Audience


Project and programme managers, team leaders, business analysts, developers and anyone who will be involved in agile projects.

Prerequisites


None.

Duration


1 day.
This course is available on site only. Please contact us for details.

Course Objectives


Many organisations are now using agile approaches to software development. Nevertheless, deciding on an agile approach, implementing it and managing the necessary culture change has been found to be non-trivial. This course helps organisations understand the nature of agile development, its advantages and its limitations. In addition, the course covers implementation and scaling
The objectives of this course are to enable participants to:
  • Understand the principles of agile approaches to development and their advantages over traditional methods.
  • Recognise the constituent parts of Scrum and the roles involved.
  • Have a general understanding of agile planning and estimating.
  • Be able to contribute to selecting and implementing an agile approach.

Course Content


Introduction to Agile Development
  • Problems with traditional approaches.
  • The Agile Manifesto.
  • Agile Manifesto Principles.
  • A generic agile approach to projects.
  • Lifecycle of product development.
  • Project constraints in traditional and agile development.
  • Benefits of agile.

Scrum
  • Scrum approach to development.
  • Scrum Roles - Scrum Master, Product Owner, Development Team.
  • Customers and Stakeholders.
  • Product Backlog.
  • Sprints.
  • Sprint Reviews, Retrospectives and Daily Scrums.

Planning
  • Levels of planning in agile.
  • Responding to change.
  • Release and iteration planning.
  • Backlog prioritisation.
  • Backlog grooming.

User Stories and Estimation
  • What are user stories?
  • Acceptance criteria.
  • Defining Done.
  • Advantages of user stories.
  • Problems in estimating, the cone of uncertainty.
  • Estimating size with story points.
  • Estimation scales.
  • Velocity.
  • Planning Poker.

Other Agile Approaches
  • History of agile.
  • eXtreme Programming (XP).
  • Dynamic Systems Development Method (DSDM Atern).
  • Lean Software Development.
  • Kanban.

Implementing Agile
  • Selecting an agile approach.
  • Using pilot projects.
  • Steps in implementing agile across an organisation.
  • Scaling agile.