Business Analyst Boot Camp

Business Analyst Boot Camp

Business Analyst Boot Camp

 

Duration:

On-site: 5 Days

Brief Description:

This fast paced education course provides training in how to conduct effective workshops/meetings, presentation skills, business modeling and documenting requirements for software development projects. The course provides an intensive case study driven approach to learn the best practices required to be a successful business analyst for the requirements life cycle phases.

Who Should Attend?:

Those who will find this of value are the, Business Systems Analysts, Project Managers, Technical Leads, Architects, Designers and Developers.

Material:

Each course participant receives a Course Handbook with agendas and scripts for conducting scoping workshops, requirements definition workshops and detailed requirements focus groups. Templates, Checklists, Samples and a Procedures Guide is also provided.

Business Analyst Boot Camp

Including Elicitation Techniques, Facilitation Skills and Business Analysis
Attendees will learn how to conduct effective meetings, presentation skills, business modeling and documenting requirements for software development projects. Boot camp training provides instructor mentoring in facilitation skills and business analysis techniques needed for defining the project scope, business requirements definition and the functional specifications for software development. The training focus is on:
  • Understanding the different levels of business requirements and where they fit in the project life cycle
  • Instructions and tips for documenting scope, business requirements using requirements lists, use cases and user stories
  • A case study driven approach to training using a provided case study or real life projects
  • Guidelines and checklists are provided for critiquing deliverables
  • Requirements Traceability Matrix
  • Facilitated session agendas and scripts for conducting scoping, requirements and detailed requirements workshops
  • Package software evaluation and selection process

Objectives:

  • Define best practices and industry standards for scoping, business requirements analysis and capturing detailed specifications
  • Provide take away documentation that can be used to implement a repeatable requirements process
  • Define a repeatable process for requirements
  • Provide case study exercises for building business models and documenting requirements using requirements lists, use cases and user stories
  • Provide each participant the opportunity to document and facilitate the different levels of business requirements and business models with mentoring from the Instructor

Day 1 AM

Course Introduction (8:30 – 9:00)
Requirements Management Best Practices (9 – 10:30)
  • What is Requirements Management?
    • Introduction to Requirements
    • Types of Requirements
    • Different levels of requirements
  • Role of the Requirements Lead/Business Analyst
  • Key requirements documents
  • Requirements management plan
    • Identifying deliverables based on the type of project
    • Checklist approach to requirements planning
  • Overview of Joint Application Development
  • Session Methodology- Preparation, Workshop and Follow-up
  • Iterative Requirements Approach
  • Timeboxing
  • Requirements roles and responsibilities
  • Key success factors to requirements definition success
Communication Techniques for Gathering Requirements (10:30 – 11:30)
  • Workshop approaches
  • Storyboarding
  • Interviewing
  • Kit Reviews
  • Teleconferencing
  • Prototype walk-throughs
  • Overview of requirements deliverables

Day 1 PM

Facilitation Skills and Techniques (11:30 – 12 and 1 – 3:00)
  • Key components of a workshop
  • Basic facilitation skills
  • Active listening skills
  • Exercise- Practice questioning and active listening skills
  • Reading and interpreting body language
  • Leadership styles
  • Facilitation rules
  • Managing conflict
  • Techniques for leading effective group dynamics
  • How to handle problem people
  • Presentation skills
  • Planning your session and building an agenda
Facilitation Exercise (3:00 – 5:00)
Each student is given the opportunity to select a technique and topic, build an agenda and facilitate a short session using the presentation skills and techniques learned in class.

Day 2 AM

Facilitation Exercise (continued) (9 – 10:30am)
Overview of the Project Life Cycle using Facilitation Techniques and Business Models (10:30 –
11am)
Discovery Phase- Problem Statement/Scope of the Project (11 – 12N)
  • Writing effective project initiation deliverables:
    • Business problem statement
    • Success criteria/objectives
    • Business parameters
    • Solution Alternatives Analysis
  • Exercise- Discovering and writing business problem statements, success criteria/objectives, business parameters

Day 2 PM

Discovery Phase- Problem Statement/Scope of the Project (1 – 2pm)
  • Constructing the context diagram and the use case model to capture the project scope
  • Exercise- Building the context diagram and use case model
  • Facilitated session agendas, scripts and facilitation techniques for conducting Problem
  • Statement Scoping Sessions
  • Prioritizing and managing the scope of a project

Day 3 AM

Discovery Phase- Business Requirements Analysis (continued) (9:00 – 12N)
  • Documenting requirements in iterations and understanding the different levels of requirements
  • Characteristics of writing effective requirements
  • Instructions and guidelines for writing effective requirements
  • Requirements attributes
  • Quality measures checklists for writing effective requirements
  • How to identify and write effective business rules
  • Building the “to be” business process flows and activity diagrams with swimlanes
  • Exercise- Creating the “to be” business process flow with swimlanes
  • Exercise- Identifying and writing quality business requirements lists and business rules
  • Facilitated session agendas, scripts, and facilitation techniques for conducting
  • Requirements Analysis Sessions
  • Benefits of using the business use case to identify requirements
  • How to write the business use case
    • Guidelines for the use case iterations
    • Templates and Quality Checklists
  • Exercise- Writing a business use case

Day 3 PM

Discovery Phase- Business Requirements Analysis (continued) (1 – 5pm)
  • How to slice the requirements to identify the user stories
  • How to write a user story
  • Exercise- Creating a user story spreadsheet
  • How to identify objects
  • How to build the domain object model using UML notations
  • Exercise- Creating the domain object model
  • How to read and build the logical data model
  • Exercise- Instructor demonstrates how to build a data model (as needed)
  • Facilitated session agendas, scripts and facilitation techniques for conducting functional specification focus group sessions

Day 4 AM

Discovery Phase- Detailed Functional Specifications Requirements (9:00 – 11)
  • How to create the state diagram using UML notation
  • How to create the state transition diagram for GUI design
  • Exercise- Creating the state diagram
  • How to write effective non-functional requirements
    • IEEE Categories
    • Non-functional definitions and examples
  • Exercise- Writing quality non-functional requirements
  • Writing requirements using site maps and identifying inventories of screens, reports and
Discovery Phase- Detailed Functional Specifications Requirements (11– 12N)
  • How to build an activity diagram with swimlanes
  • How to create the detailed use cases

Day 4 PM

Discovery Phase- Detailed Functional Specifications Requirements (continued) (1 – 3pm)
  • How to build an activity diagram with swimlanes
  • How to create the detailed use cases
  • Defining the Screen Specifications
    • Using brainstorming and storyboarding techniques to create the draft screens
    • Creating data requirements specifications for screens
  • Defining the Report Specifications
    • Key components of the report specifications requirements
    • Report Mock-ups
    • Report Specifications Template
  • Exercise- Writing the detailed use case, data fields descriptions and storyboarding the paper prototypes.
  • How to build the data flow diagram for defining data requirements
  • Exercise- Building the data flow diagram
  • Requirements Traceability Matrix
    • Overview of requirements traceability
    • Tracing test scenarios to requirements/use cases
    • How to create traceability worksheets
Quality Assurance (3:30 – 4:00pm)
  • Quality measures for checking requirements
  • Techniques for quality checking requirements
    • Desk checking using checklists and questions for validating requirements
    • Conducting Peer Reviews for requirements validation
    • Requirements Inspection Process and Sign-off for requirements validation
Preparation for the Business Analysis & Requirements Gathering Simulation (4:00 – 5pm)

Day 5

Business Analysis and Requirements Gathering Simulation- Case Study Lab (optionally, a real life project can be used for the simulation session)
This business analysis & requirements gathering simulation demonstrates how the entire life cycle of a project fits together and how the business analysis artifacts and requirements gathering techniques taught in class build on each other. Each student facilitates a stage in the life cycle using the scoping, business requirements definition and detailed functional specifications artifacts and agendas learned in the class. The business analysis models used for the business analysis & requirements gathering simulation will be the Problem Statement/Root Causes, Success Criteria/Objectives, Scope Statements, Context Diagram, HL Use Case Diagram, Activity Diagram with Swimlanes, Business Use Cases, Domain Object Model, Detailed Use Cases and Paper Prototypes/Screen Specifications. In addition, each student will document to demonstrate an understanding of the documentation process. Each student is provided with feedback and mentoring from the instructor.

Module 1



No products found

Module 2

Virtual Facilitation Courses

JAD Facilitation Class

Date: December 3 - 5, 2018

Duration: 3 half-day sessions

 
-
+
$750.00
Request Info
View Course Details

Request On-site Form

    Stay up to date! Get exclusive information from Pierson on all the latest in Business Analyst & Agile training

Curriculum Map to BABOK v3 IIBA

BABOK Guide Chapters used for Mapping to Class Curriculum

  • Chapter 1- Introduction (N/A)
  • Chapter 2- Business Analysis Planning & Monitoring (Module 1)
  • Chapter 3- Elicitation and Collaboration (Modules 1, 2, 4, 5, 6)
  • Chapter 4- Requirements Life Cycle Management (Modules 3, 5, 6)
  • Chapter 5- Strategy Analysis (Modules 3, 6)
  • Chapter 6- Requirements Analysis & Design Definition (Modules 3, 4, 5, 6)
  • Chapter 7- Solution Evaluation (Module 5)
  • Chapter 8- Underlying Competencies (Modules 2, 6)
  • Chapter 9- Techniques (Modules 4, 5, 6)

The overwhelming majority of the BABOK v3.0 is covered in Pierson’s Business Analyst Boot Camp training program.  However, Pierson’s class is intended to provide the participants with a practical proven repeatable process to accomplish their requirements tasks and is designed to develop the required skills needed including practical exercises.  The training is presented in a Requirements Life Cycle order. Joy Matthews, who is the author of the training, was a member of the BABOK v2.0 Review Board. Pierson Requirements Group is an IIBA Endorsed Education Provider. The training course offered below was reviewed and approved by the IIBA.  All of Pierson’s training classes are eligible for CDUs from the IIBA and PDUs from the PMI.

 

Pierson Curriculum

BABOK v3.0 Chapters Mapping

Module 1

Fundamentals of Requirements

Introduction

Requirements Management Best Practices

  • What is Requirements Management?
  • Introduction to Requirements
    • Types of Requirements
    • Different levels of requirements
  • Role of the Requirements Lead/Business Analyst
  • Key requirements documents
  • Requirements management plan
  • Overview of Joint Application Development
  • Session Methodology- Preparation, Workshop and Follow-up
  • Iterative Requirements Approach
  • Time boxing
  • Requirements roles and responsibilities
  • Key success factors to requirements definition success
  • CH 2- Business Analysis Planning & Monitoring
  • CH3- Elicitation & Collaboration

Module 1 (continued)

Communication Techniques for Gathering Business Requirements

  • Workshop approaches
  • Storyboarding
  • Interviewing
  • Kit Reviews
  • Teleconferencing
  • Prototype walk-through
  • Business Models- context diagram, use case diagram, business process flows, use cases
  • CH 9- Techniques

Module 2

Facilitation Skills & Group Dynamics

Facilitation Skills and Techniques

    • Key components of a workshop
    • Basic facilitation skills
    • Active listening skills
  • Exercise- Practice questioning and active listening skills
  • Reading and interpreting body language
  • Leadership styles
  • Facilitation rules
  • Managing conflict
  • Techniques for leading effective group dynamics
  • How to handle problem people
  • Presentation skills
  • Planning your session and building an agenda

Facilitation Exercise

Each student is given the opportunity to select a technique and topic, build an agenda and facilitate a short session using the presentation skills and techniques learned in class.

  • CH 3- Elicitation & Collaboration
  • CH 8- Underlying Competencies – Interaction skills- facilitation and negotiation, leadership and influencing, teamwork

Module 3

Scoping Business Needs

Overview of the Requirements Gathering Sessions and Business Models

Discovery Phase- Problem Statement/Scope of the Project

    • Writing effective business case deliverables:
      • Business problem statement
      • Success criteria/objectives
      • Business parameters
      • Solution Alternatives Analysis
  • Exercise- Discovering and writing business problem statements, success criteria/objectives, business parameters, solution alternative analysis
    • How to write effective scope statements & assumptions
  • Exercise- Creating questions, role playing to practice conducting business management interviews and writing the project scope statements & assumptions
    • Constructing the context diagram and the use case model to capture the project scope
  • Exercise- Building the context diagram and use case model
    • Facilitated session agendas, scripts and facilitation techniques for conducting Problem Statement Scoping Sessions
  • Prioritizing and managing the scope of a project
  • CH 4-Requirements Life Cycle.
  • CH 5-Strategy Analysis
  • CH 6-Requirements Analysis & Design Definition

Module 4

Business Requirements Analysis

Discovery Phase- Requirements Analysis

    • Documenting requirements in iterations and understanding the different levels of requirements
    • Characteristics of writing effective requirements
    • Instructions and guidelines for writing effective requirements
  • Requirements attributes
    • Quality measures checklists for writing effective requirements
    • How to identify and write effective business rules
    • Building the “to be” business process flows and activity diagrams with swimlanes
  • Exercise-  Creating the “to be” business process flow
  • Exercise- Identifying and writing quality requirements lists and business rules
  • Facilitated session agendas, scripts, and facilitation techniques for conducting Requirements Analysis Sessions
  • Benefits of using the business use case to identify requirements
  • How to write the business use case
    • Guidelines for the use case iterations
    • Templates and Quality Checklists
  • Exercise-  Writing a business use case

Discovery Phase- Requirements Analysis (continued)

    • How to slice the requirements to identify the user stories
    • How to write a user story
    • Exercise- Creating a user story spreadsheet
    • How to create the domain object model
  • Exercise- Creating the domain object model
  • How to read and build the logical data model
  • Exercise- Instructor demonstrates how to build a data model (as needed)
    • How to create the state diagram using UML notation
  • Exercise- Creating the state diagram
    • How to write effective non-functional requirements
      • IEEE Categories
      • Non-functional definitions and examples
  • Exercise-  Writing quality non-functional requirements
  • Writing requirements using site maps and identifying inventories of screens, reports and system interfaces
  • CH 6-Requirements Analysis & Design
  • CH 3-Elicitation & Collaboration
  • CH 9-Techniques

Module 5

Functional Requirements Specifications

Discovery Phase- Specifications

    • How to create the detailed use cases
    • How to build an activity diagram with swimlanes
    • Using brainstorming and storyboarding techniques to create the draft screens
    • Creating data requirements specifications for screens and reports
  • Exercise- Writing the detailed use case, creating the activity diagram with swimlanes for the use case, data fields descriptions and storyboarding the draft screens
    • Defining the Report Specifications
      • Key components of the report specifications requirements
      • Report Mock-ups
      • Requirements gathering techniques for report specifications and review of the Report Specifications Template
    • How to build the data flow diagram for defining data requirements
  • Exercise- Building the data flow diagram
    • Facilitated session agendas, scripts and facilitation techniques for conducting high level design focus group sessions
    • Requirements Traceability Matrix
      • Overview of requirements traceability
      • Tracing test scenarios to requirements/use cases
  • How to create traceability worksheets
    • CH 6- Requirements Analysis & Design
    • CH 9- Techniques
    • CH 3- Elicitation & Collaboration
    • CH 4- Requirements Life Cycle
Requirements Review (Requirements Sign-off)

    • Techniques for quality checking requirements
      • Checklists
      • Desk Checking
      • Peer reviews for requirements inspection
  • Exercise- Desk checking requirements and conducting a Requirements Inspection Meeting
  • Change control process and template
  • CH 7- Solution Evaluation

Module 6 (Day 4 – 5)  

Business Analysis and Requirements Gathering Simulation

This business analysis & requirements gathering simulation demonstrates how the entire life cycle of a project fits together and how the business analysis artifacts and requirements gathering techniques taught in class build on each other. Each student facilitates a stage in the life cycle using the scoping, business requirements definition and software specifications artifacts and agendas learned in the class.  *The business analysis models used for the business analysis & requirements gathering simulation will be the Problem Statement/Root Causes, Success Criteria/Objectives, Scope Statements, Use Case Model, Activity Diagram, Business Use Case, Domain Object Model, State Chart, Detailed Use Case and Paper Prototype. In addition, each student will document to demonstrate an understanding of the documentation process using Visio, Excel and Word documentation tools.  Each student is provided with feedback from the instructor and is given a written evaluation.

Students will apply and be evaluated on applying the BABOK Competencies as follows:

    • Business Analysis Planning
    • Elicitation & Collaboration
    • Requirements Life Cycle
    • Strategy Analysis
    • Requirements Analysis & Design Definition
  • Underlying Competencies- analytical thinking and problem solving, behavioral characteristics, communication skills, interaction skills and software applications

*Refer to description of the simulation for techniques used.

 

Materials

Each seminar participant receives a Seminar Handbook with sample agendas and scripts for conducting problem statement scoping sessions, requirements definition sessions and functional specifications focus groups.  Guidelines, Templates, Checklists and a Requirements Management Procedures Guide is also provided. Maximum of 12 – 15 people.

Close Menu
×
×

Cart