The Practical BA: The why, what and how of business analysis

As a Business Analyst, you're counted on for your skills as a conceptual and practical thinker, relationship builder and translator.  You're counted on to identify and describe the change required to solve a business problem.

In this course, you'll be introduced to a pragmatic and practical approach to analysis you can apply in a waterfall, iterative and Agile environment.

Designed and delivered by our Equinox IT team of practicing Business Analysts, we'll show you how to structure your analysis activities to ensure the solution requirements you produce fully represent the business goals of the change required.

This course aligns to the Business Analysis Body of Knowledge^®. 

The primary audience for this course is business analysts, systems analysts and enterprise analysts of all levels of experience. The course will also be of value to any project team members who are involved in requirements definition activities.

Following completion of this course, students will be able to;

• Analyse and understand the business domain
• Identify and validate the root business problem
• Engage stakeholders and analyse their problems and business needs
• Identify business and information requirements
• Model business processes with related business rules
• Use effective techniques to elicit requirements
• Analyse, document and review solution and detailed requirements
• Review analysis outputs and create requirements deliverables
• Understand how to communicate with a variety of audiences        

Day One:  WHY?

Uncover the reason for the change by:

1. Understanding and describing a business domain
2. Diagnosing the business problem
3. Identifying stakeholders and their relationship to the project
4. Describing business needs

Day Two:  WHAT?

Define the goal of the change by:

1. Describing the business capability required
2. Analysing information that is needed (data and business rules)
3. Analysing business processes
4. Describing Solution Requirements

Day Three:  HOW?

Define in detail the change(s) required by:

1. Analysing software requirements
2. Documenting specifications
3. Describing detailed Solution Requirements
4. Communicating the change – telling the story

There are no prerequisites for this course.