• Instructor: Rajan R.
  • Students: 2301
  • Duration: 10 weeks

BUSINESS ANALYSIS (Complete Course Package)

Objectives:
At the end of the training course, participants will know how to conduct a business systems
analysis assignment using tools, Methodologies and techniques in Software Development Life
Cycle Phases.
Who should attend?
● Entry-level IT Business Analysts
●Domain expertise’s aspiring to get into the business analysis
● Self-taught IT Business Analysts wanting to fill in the gaps and put all the Pieces
together
● Systems Analysts and programmers interested in expanding their role into the business
area
Our course syllabus has been evaluated to meet the requirements and are in alignment with the
Business Analysis Body of Knowledge® (BABOK®) and Scrumalliance® on Agile-Scrum
practices.

o Understanding the change, Value, stakeholders and Business Analysis
o Business Analysis Overview
o What is Business Analysis?
o Significance of Business Analysis
o Business analysis practical applications
o Factors to be considered
o Roles and responsibilities of BA
o Activities business analyst can perform
o Contribution to project
o Expected mandatory work as a business analyst

o Personal traits
o Professional traits
● BA Methodologies
● Agile methodologies and SCRUM
● Role of BA in SCRUM

● Agile principles
● Agile values
● Scrum Ceremonies
● Scrum Roles
● Scrum artefacts

● Requirements elicitation
o What is the requirement elicitation?
o How to conduct elicitation?
o Factors influencing the elicitation
o How to record the outputs?
o How to communicate and get confirmations on elicited results?
o Requirement elicitation techniques
● Requirement modelling
o What is requirements modelling?
o Need for requirements modelling?
o Factors to be considered while modelling the requirements
o Requirement modelling techniques
● Requirement Management
o Tracing the requirements
o Requirement traceability matrix
o Lifecycle of requirements
● Managing change requests
o What is change request?
o Change management process
o Creating and analysing change requests
o Impact analysis
o Factors to be considered while analysing the impact
o Evaluating Business value

● User Story creation
o What is user story?
o Why is it used?
o How to create user stories from requirements?
o User story templates
o Factors to be considered while creating the user stories
o Creating user stories from Usecases
o Understanding value vs motivation of a user story
o Splitting the user stories
● Product backlog/User story Prioritization
o What is prioritization?
o Factors to be considered while prioritizing the stories
o Selecting user stories for sprint
o Creating tasks for a user story
● Refinement/Backlog grooming
o What is backlog grooming?
o Significance of backlog grooming
o Just in time requirements
o Just in time documentation
o How much is too much?
o Challenges in backlog grooming
o Story elaboration techniques
o Understanding Value addition of user stories
o Providing Clarifications to team on user stories
o Practical challenges during sprint
o Performance related aspects of user story

● Release planning
o What is a release?
o What is release planning?
o How to plan a release?
o Role of Business Analyst in release planning
● Story decomposition Technique
o Understanding Vision
o Understanding Themes
o Understanding Epics
o Understanding user stories
o Understanding Acceptance criteria
● Selecting themes for releases
o Factors to be considered while selecting the themes
o Theme prioritization techniques
● Selecting stories for releases
o Factors to be considered while selecting stories for release
● Prioritizing stories for release planning
o User Story prioritization techniques
o MoSCoW technique
o Other techniques
● Story mapping Technique
o Significance of Story mapping
o How is it done?
● Supporting development team
● Supporting Testing activities
o Pre-UAT
o User Acceptance testing

● Stake holder management
● Who are stakeholders?
● Importance of stakeholders
● Identifying stakeholders
● Working with stakeholders
● Handling stakeholders concerns
● How to build good rapport with Stakeholders?
● How to avoid conflicts with stakeholders?
● Risk management
o What is a risk?
o Impacts of risk?
o Illustrative examples of risks
o Significance of identifying risks in a project or in business analysis
o Risk register
● Requirements monitoring and control
o How to monitor requirements?
o Trace the requirements
o RTM
● Sign off
o What is a sign off?
o Significance of sign off
o User story sign off
o UAT sign off
o Sign off in Change requests

● AS-IS study
o What is AS-IS state?
o What is AS-IS Process?
o How to conduct AS-IS study?
o AS-IS study report
● To-Be Proposal
● What is TO-BE State?
o To-Be processes
o Documenting TO-BE state proposal
o Incorporating feedback
● SWOT analysis
o Significance of SWOT analysis
o How to user SWOT for Professional work?
o How to use SWOT for personal improvement?
o SWOT strategies
o Usage limitations
● Process engineering
o What is a process?
o Process maps
o Swim lanes
o AS-IS Process map
o TO-BE process map
o Tools for creating process maps
● Proposing solutions
o Identifying solution options
o Working with teams
o Evaluating solution
● Adding value to business
o What is value addition?
o Type of values for a business
o Understanding business context
o Identifying value adds
o Proposing value addition

● Lightweight Documentation
● Relative Estimation
● MoSCoW Prioritization
● Retrospective
● Personas

● Behaviour Driven Development
● Storyboarding
● Story Mapping
● Lightweight Documentation
● Personas

● Kano analysis
● MoSCoW Prioritization
● Story decomposition
● Story Mapping

● Kano analysis
● Real options
● Personas
● Value stream analysis
● Purpose alignment model

● Behaviour Driven Development
● Kano Analysis
● Lightweight Documentation
● MoSCoW Prioritization
● Purpose Alignment Model
● Real Options
● Story Decomposition
● Story Elaboration
● Story Mapping
● Storyboarding
● Value Stream Analysis
● For Solution Evaluation
● Personas
● Value Stream Analysis

● Financial domain – Software perspective

● Business requirements
● Identifying Types of requirements
● Identifying requirements from process
● Identifying Epics from requirements
● Identifying User stories from Epics
● Prioritization techniques
o Theme prioritization techniques
o User story prioritization techniques
● Elicitation techniques
o Classic techniques
o Contextual techniques
o Group techniques
● Modelling techniques
● User story creation
● Acceptance criteria
● Refinements/Backlog grooming
● Just-in-time Documentation
● Splitting the User Stories

This training is designed uniquely which adds value to you and your career. This training makes
you job ready. Few more value additions you get from this training are:
● Examples from real time projects
● References from real time scenarios
● Illustrations and experiences from real IT world
● Tips and tricks to perform as a better BA
● Techniques to adapt changing environments when you need to work with different
domains

● Right balance of theory & practical scenarios
● Orientation towards real time scenarios than just theoretical explanations
● Upto-date training coverage as per industry requirement
● Easily understandable examples for IT and non-IT background candidates
● Clear illustrations of topics for both experienced and job aspirants
For further information feel free to get in touch and request for a demo session.
Wish you happy learning!

Curriculum is empty

Price

Free

Leave a Reply

Your email address will not be published.

Call Now ButtonCall NowRequest Form