Program

IT Business Analyst-5

IT Business Analysts are responsible for discovering, synthesizing, and analyzing information from a variety of sources within an enterprise, including tools, processes, documentation, and stakeholders. The business analyst is responsible for eliciting the actual needs of stakeholders - which frequently involves investigating and clarifying their expressed desires - in order to determine underlying issues and causes.

Our course is designed for whose who have basic knowledge in this field and want to improve their knowledge, also understanding enterprise problems and goals, analyze needs and solutions, devise strategies, drive change, and facilitate stakeholder collaboration in any IT project.

The tuition fee for the specialty IT Business Analyst is 2250 AZN.

Application to the program is currently not active
Start date

October 2024

Duration

5.5 months

Group size

20-25 students

Schedule

Monday and Friday 19:00, Sunday 11:00

Admission requirements
Expectation

Working experience in the analytics or customer service role and soft skills

Language skills

Knowledge of English at least Intermediate level

Requirement

To have a personal computer or a laptop

Age

18 years and older

Upon the course completion you will::

Main principles of Business analysis

Requirement elicitation, analyse, and prioritaziton

Business process analysis, planning, and modelling

Foundation of Project management (Traditional, Agile)

Software testing tailored for Business Analyst

Technical knowledge (Software architecture, SQL, Database, UI/UX Design, Software Tools)

Program

IT Business Analyst-5
17

Number of modules

  • Software Development Life Cycle
  • Software Development Methodologies – Water Fall, Iterative, Agile, etc.
  • What is business analysis?
  • The career path into business analysis
  • What is a Business Process
  • Critical Analysis of a Business Process
  • Business Process Mapping & Flow charting
  • As Is -To Be Analysis For a Business Process
  • Business Process Mapping and Modelling Frameworks
  • Business Process Mapping and Modelling Software
  • Business Process Re-Engineering & Re-Design
  • Business Process Automation, Disinter mediation and Re-intermediation
  • Stakeholder Definition
  • Importance of Stakeholder ​                         
  • Interview with Stakeholder
  • Stakeholder Identification – Onion Diagram
  • Stakeholder Identification – Wheel
  • Stakeholder Classification – Power Influence Matrix
  • Stakeholder Engagement Techniques – Power/Influence Vs Interest
  • Stakeholder RACI Chart, its preparation through Visio
  • Stake Holder Personal
  • Stakeholder Alignment and Sponsorship
  • Managing Internal stakeholders
  • Preparing Stakeholder map through Excel
  • What is a Requirement
  • Attributes of Requirements (SMART)
  • Importance of Requirements for IT Projects
  • Functional and Non Functional Requirements
  • Overview of Requirements Engineering and Management
  • Business Process Re-Engineering & Re-Design
  • Important Requirement Process Steps : Elicitation, Analysis, Documentation, Validation, Management
  • Requirement Software Companies - Task management systems
  • RA : The Business Analyst Tasks
  • Prioritize Requirements
  • Specify and Model Requirements
  • Define Assumption and Constraints
  • Verify Requirements
  • Validate Requirements                                                                                       
  • BR document
  • Scope document
  • History of UML , its founding fathers and role of OMG (Object Management Group)
  • UML Diagrams –UML Structure and UML Behavior Diagrams
  • Important UML Diagrams for IT Business Analysts
  • Overview of UML Structure Diagrams
  • Class Diagrams
  • Activity Diagrams
  • Use Case Diagrams
  • Sequence Diagrams
  • Other UML Diagrams      
  • What is BPMN
  • Origin of BPMN -BPMI (Business Process Management Institute) and OMG (Object Management Group)
  • BPMN Notations
  • Types of Process Modelling – Process Maps, Models, Descriptions
  • BPMN Elements : Flow Objects, Data, Swim Lanes, Connecting Objects, Artifacts
  • Live Process monitoring through compounds
  • Why collaboration is key
  • Where the roles overlap
  • Estimating and planning
  • Communication 
  • Risk management
  • Scope management and change
  • Change request management
  • UX Questionnaire
  • UX Project Plan
  • Listening Tour
  • Opportunity Workshop
  • Project Brief
  • Strategy Workshop
  • Guerilla User Research
  • Proto-Personas
  • Heuristic Markup
  • Comparative Assessment
  • Design Principles
  • Sketching
  • Task Flows
  • Wireframes
  • IT Infrastructure 
  • HTTP Req&Res
  • MVP (MVC)
  • CI/CD
  • Release management
  • SRE fundamentals  
  • Database concepts and the 3rd Normal Form, Primary Key, Foreign Key and Database design
  • SQL Data Definition Language Statements : Create, Alter and Drop
  • SQL Data Manipulation Language Statements : Insert, Update and Delete
  • SQL Data Query Language : Select, Join
  • Introduction to APIs: Understanding APIs | API Architecture and Components | API Standards and Protocols
  • API Specification Fundamentals: Introduction to API Specification | OpenAPI Specification (OAS) | Practical Exercise: Writing an OpenAPI Specification
  • API Request and Response Handling: Constructing API Requests | Processing API Responses | Error Handling and Validation
  • API Security and Best Practices: API Security Fundamentals | Best Practices in API Design | Practical Exercise: Implementing API Security Measures
  • Tools and Technologies for API Management: API Development Tools | API Documentation and Mocking | API Monitoring and Analytics
  • Test Case & Test Scenario
  • White-Box Techniques
  • Agile Test Quadrant
  • UAT     
  • Monolithic architecture
  • Microservice arcitecture
  • Microfrontend
  • Single-page application architecture
  • Database design
  • Architecture diagramming  
  • Messaging (Kafka & Rabbit MQ)                                                                      
  • Event based development
  • Authorization
  • Information Security for BA 
  • Database design
  • Arcitecture diagramming   
  • What is Software Release?
  • What is Release Management?
  • Who is Release Manager? - Roles & Responsibilities
  • Who is Release Manager? - Technical Skills
  • Release vs Change vs Deployment Managements
  • Why need Release Manager, If we have PO?
  • Frameworks that instill the concept of Release Management
  • Frameworks and practices that instill roles as RM, DM, SA, etc.
  • Release Strategies - Slow Cadence, Quick Cadence, Release Train, Continuous Release
  • Scaled Agile Framework (SAFe) / Release Train Engineer
  • SAFE / Roles of Release Train Engineer
  • The role of Product Owners (POs) in Release Planning
  • The role of Business Analysts (BAs) in Release Process
  • Risk Management in Release Management Process
  • Release Process over samples
  • Branching Strategies // Epic-base branching model
  • Post-Release Analysis and Continuous Improvement
  • Agile Software Development – An Overview
  • Agile Manifesto and Philosophy
  • Agile Methodology
  • Agile Software Development Lifecycle
  • Scrum
  • Managing Sprint Planning, Daily SCRUM, Sprint Review & Sprint Retrospectives
  • Three Roles in Scrum : Scum Master, Product Owner and Development Team
  • Preparing Product Backlog, Sprint Burn Down Charts
  • Preparing Agile Project Charter
  • Xterme Programming, Kanban
  • Writing User Stories
  • Story Points and Estimation on SCRUM projects 
  • A. C.
  • Requirement gathering
  • Strategy analysis
  • System design 
  • Diagramming 
  • Defining DoD 
  • Delivery to team     
  • UX/UI Design
  • Camunda 
  • BA Career Path 
  • BA Certification 
  • SRE&Release management
  • Agile
  • Risk management        
  • IT Audit        
  • HR Interview