Course Overview

In an article published by Forrester Research on December 14, 2007, “Five Trends that Will Shape the Application Development and Program Management Profession in 2008,” they predicted good news for the business analysis profession. The authors, Carey Schwaber had this to say for 2008:
The role of business analyst will change and grow in importance. Most enterprises understand how important business analysts (BA) are to maximizing the business value of projects and portfolios, but few have acted with this understanding and established career paths around BAs.”
Business Analyst maximizes the business value of projects by performing certain activities on a project. This course provides an insight of the business analyst role.
This course explains the importance of business analyst work in planning and eliciting requirements using various proven elicitation techniques such as Interviewing, Meetings and Facilitation. The learners gain knowledge on how and when to apply these elicitation techniques.
The business analyst analyzes documents and reviews the elicited requirements before communication to identified stakeholders.
The key affect of this course is our coverage of the business analyst fundamental skills. The underlying or fundamental skills are the core competencies required for business analyst to be successful.

Course Objectives

Upon completion of this course, participants will be able to:

  • Define the role of the Business Analyst
  • Understand the business analysi profession
  • Review activities performed by a BusinessAnalyst
  • Differentiate between the role of business analyst and project manager
  • Review Business Analyst activities in a typical SDLC
  • Understand the business analysis profession
  • Review and describe IIBA's knowledge areas
  • Understand the importance of requirements
  • Define requirement and describe with examples various requirements types

Primary Objectives

  • Understand the context or requirements in any given project
  • Ut ilize key elicitation techniques to gather requirements
  • Identify components of requirements management plan
  • Provides high level overview of analyze, document, review and approve requirements
  • Understand when requirements elicitation is complete (or is it ever complete)
  • Define and review sources of conflicts
  • Review conflict resolution techniques
  • Verify requirements using requirements checklist
  • Document requirements.

Secondary Objectives

  • Understand the importance of requirements baseline
  • Describe the purpose of InternationalInstitute of Business Analysis (IIBA)
  • Introduce the Business Analysis Body of Knowledge (BABOK )
  • Review and describe IIBA's knowledge areas

Course Content

Lesson 1:Introduction to Business Analysis

  • Definition the BA Role
  • BA Skills
  • Who is a BA?
  • Define Requirements
  • Types of Requirements

Lesson 2:Requirements in Context of Projects

  • What is a Project?
  • Role of PM
  • Role of BA
  • Project Scope vs. Product Scope
  • Goals
  • Objectives
  • Determine Project Scope
  • Project Scope from Enterprise Analysis resulting from a Business Case
  • Project Charter Document (Project Scope)
  • Vision Document
  • Understanding the Problem

Lesson 3:Identify components of the Requirements Management Plan

  • Identify, Describe and CategorizeStakeholders
  • Establish RequirementsCommunication Plan
  • Identify Team Roles
  • Requirements Baseline
  • Requirements Change Management
  • Requirements Risk Management
  • Establish Requirements Types
  • Define Traceability Strategy
  • Define Requirements DocumentationApproach
  • ·Create Requirements Management Plan

Lesson 4:Requirements Elicitation

  • Establish Context for Requirements Gathering
  • Understand Elicitation Techniques Spectrum
  • Elicit Requirements using Interviewing,Meetings
  • Conducting facilitated requirements workshop
  • Manage conflicts by utilizing conflict resolution techniques.
  • Requirements Planning and Management

Lesson 5 : Requirements Analysis, Documentation and Communication

  • Structure Requirements
  • Define Business Domain Model
  • Write Textual Requirements
  • Model Requirements (Solution requirements complement To-Be business models)
  • Describe Logical Data Models (Class Diagram, E-R Diagram)
  • Model Data and Behavior (Use Cases, Use Case Diagrams)
  • Model Processes (Activity Diagrams)
  • Document Requirements
  • Review Template for Documents such as BRD, SRS, Use Case Document
  • Validate and Verify Requirements
  • Requirements Verification Checklist
  • Present Requirements
  • Obtain Final Sign-Off
  • Establish Requirements Sign-Off

Lesson 6:BA as a Support Function

  • Determine Alternative Solutions
  • Support Quality Assurance Activities
  • Update Traceability
  • Support User Acceptance Test

Lesson 7:Underlying BA Competencies

  • Structured Analysis Skills
  • IT knowledge
  • Business / Domain Knowledge
  • Facilitation Skills
  • Questioning Skills
  • Communication Skills
  • Leadership Skills
  • Negotiation Skills
  • Conflict Resolution Skills
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License