Session 01: Introduction
R2S Academy – Internal Use – Author: TUAN NGO

Table of Content
My contact / Introduction
Course Content
BA Introduction
2
R2S Academy – Internal Use – Author: TUAN NGO
1
2
3
Objectives

Ngo Anh Tuan
Master of Science – Dayeh University, Taiwan
12+ years experiences in Software Development
Career Path: Software Developer, BA, PM, Project Director, VP
Working oversea: US, Malaysia, Brunei, Singapore, Mexico
Contact:
ü Email: arcngoanhtuan@gmail.com
ü Phone: 0905576046
3
My Contact

4
SELF-INTRODUCTION
ü Name
ü Age
ü Career / University / Department
ü IT background
ü English background
ü Why BA?

Syllabus
ü 20 Sessions
ü 01 Team presentation
ü 01 Final presentation
5
Course Content
Sessions
1. BA Introduction
2. Software Development Lifecycle
3. Requirements
4. Requirement Engineering
5. Requirement Elicitation – Techniques
6. Q&A for Topics
7. Diagrams (Activity & Use Case Diagrams)
8. Req Specification (Documents)
9. Document Versions Management
10. Teams presentation
11. Course Review 1
12. Sequence Diagram
13. Class Diagram
14. Class Diagram
15. Agile / Scrum
16. User Stories
17. User Stories (Con’t)
18. Software Testing
19. Course Review 2
20. Final Presentation & QA

6
WoW
Way of work
1. Class attendance: On-time & sufficient
2. During class: Camera ON and stay focus
3. After class: Do team assignment
4. Teams: 02 members / team
Course evaluation
1. Class attendance (all sessions) – team work (20% of total)
2. Team presentation (sessions #10) – team work (30% of total)
3. Final test (session #20) – individual work (50% of total)

BA - Introduction
7
Business Analysis Process
01
Business Analysis
Techniques
02
Business Analyst Roles
& Responsibility
03

8
Business Analysis - Process
Introduction

9
What is Business Analysis?
• A research discipline that helps you to:
• Find the business needs
• Identify solutions to business problems
• Development of a software or system component
• Improvements in process
• Organizational changes or strategic planning and policy development
• Business analysts help maximize a business's effectiveness through data-driven decisions
Introduction
Business Analysis - Process

Business Analysis terms
o Requirement / Feature / Change request / Enhancement
o Scope of Work (SoW)
o Minimum Value Product (MVP) / Proof of Concept (POC)
o Stakeholders
o Use Case / User Story / Product Backlog / Task / Bug
o Mockups (wireframes) / Flow chart / Diagram / Screen flow
o User Interface (UI) / User Experience (UX) – UI/UX
o User manual / Guidelines / Release
o Man Day (MD) / Man Month (MM)
Introduction
Business Analysis - Process

Introduction
Business Analysis - Process
Business Analysis Process

Introduction
Business Analysis - Process
01. Gather Background Info Info?
ü Whether a project is brand new or
existing?
ü What domain is the project under?
(financial, health, energy, hosting, etc.)
ü Determine the various circumstances
that could potentially affect the business
strategy for the project
ü Understanding the history of a project
and documenting

Introduction
Business Analysis - Process
02. Identify Stakeholders
Output: Stakeholder Matrix Document
Stakeholders?

Introduction
Business Analysis - Process
03. Discover Business Objectives
Output: Business Objectives List Document
ü Stay focused on the vision
ü Narrow down the business objectives
ü Techniques:
• Benchmarking
• Focus groups and brainstorming
• MOST
• SWOT
• SMART
• etc

Introduction
Business Analysis - Process
04. Evaluate Options
Output: Business Case Document
Options:
ü Customize existing solution
ü Purchase an existing service
ü Build a product from scratch
ü Integrate to other systems
Next step:
ü Present the business case options to
stakeholders and have them make a
decision

Introduction
Business Analysis - Process
05. Scope Definition
Output: Scope Definition Document
SoW
ü Development items in scope
ü Development items out of scope
ü Integrations in scope
ü Integrations out of scope

Introduction
Business Analysis - Process
06. BA Delivery Plan
Output: Business Analyst Delivery Plan Document
Plan
ü BA & Project Owner (PO)
ü Detailed timeline for delivering
requirements to dev team
ü Based on factors:
• Stakeholders and their availability
• Project scope
• Project methodology
ü Goal: plan resources & project timelines

Introduction
Business Analysis - Process
07. Define Project Requirements
Output: Functional & Non-functional Reqs Document
Output:
ü Non-functional Requirements (Reqs)
ü Performance
ü Security
ü Scalability
ü Functional Requirements
ü Use case
ü Story board
ü Prototypes / wireframes
Techniques:
ü Interviewing the stakeholders: ask - how,
when, where, what
ü Use case template, storyboard, mockups

Introduction
Business Analysis - Process
08. Support Implementation through SDLC To do:
ü Reviewing deliverables to align w/ reqs
ü Update requirements
ü Engage with Dev & Test teams
ü Manage changes from PO
ü Facilitate user acceptance

Introduction
Business Analysis - Process
09. Evaluate value added by project Questions:
ü Are we on track?
ü Is the solution delivering the value
initially anticipated?
Actions:
ü Evaluate the actual progress across the
timeline and business objectives, and
provide stakeholders updates and
answer questions
ü Based on the progress and feedback,
suggest any modifications or initiatives
required to realign the implementation
phase with business objectives

21
Business Analysis- Techniques
Introduction

Introduction
Business Analysis - Techniques

MOST
o To perform thorough internal analysis of what is
the aim of an organization to achieve and how to
tackles such issues
o To define which direction to follow
o “Objectives” should be SMART (Specific,
Measurable, Achievable, Realistic and Timely)
o Top à Bottom
Introduction
Business Analysis - Techniques

SWOT
• to find areas of both strength and weakness (the
health of organization/ business). It also allows for
the proper allocation of resources
• to make decision
Example 1: I would like to change my career path
from Developer to Business Analyst
Example 2: We would like to build the healthcare
system for hospitals to manage and exchange their
patient records
Introduction
Business Analysis - Techniques

MoSCoW
• Allows prioritization of requirements by presenting a
framework in which every individual requirement should
be evaluated relative to the others.
• To organize to do list
Example: We would like to develop Android application to
notify my grandmother to take pills
Introduction
Business Analysis - Techniques