Session 01: Introduction

R2S Academy – Internal Use – Author: TUAN NGO

Table of Content
Objectives

1 My contact / Introduction

2 Course Content

3 BA Introduction

R2S Academy – Internal Use – Author: TUAN NGO 2

 My Contact
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
SELF-INTRODUCTION
ü Name

ü Age

ü Career / University / Department

ü IT background

ü English background

ü Why BA?

4
 Course Content
Syllabus Sessions
ü 20 Sessions 1. BA Introduction 11. Course Review 1

ü 01 Team presentation 2. Software Development Lifecycle 12. Sequence Diagram

ü 01 Final presentation 3. Requirements 13. Class Diagram

4. Requirement Engineering 14. Class Diagram

5. Requirement Elicitation – Techniques 15. Agile / Scrum

6. Q&A for Topics 16. User Stories

7. Diagrams (Activity & Use Case Diagrams) 17. User Stories (Con’t)

8. Req Specification (Documents) 18. Software Testing

9. Document Versions Management 19. Course Review 2

5
10. Teams presentation 20. Final Presentation & QA
 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)

6
 BA - Introduction

01 Business Analysis Process

Business Analysis
02 Techniques

Business Analyst Roles

03 & Responsibility

7
 Introduction

Business Analysis - Process

8
 Introduction
Business Analysis - Process
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

9
 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
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 Stakeholders?

Output: Stakeholder Matrix Document

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

Output: Business Objectives List Document

 Introduction
Business Analysis - Process
04. Evaluate Options 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

Output: Business Case Document

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

Output: Scope Definition Document

 Introduction
Business Analysis - Process
06. BA Delivery Plan 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

Output: Business Analyst Delivery Plan Document

 Introduction
Business Analysis - Process
07. Define Project Requirements 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
Output: Functional & Non-functional Reqs Document ü 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
 Introduction

Business Analysis- Techniques

21
 Introduction
Business Analysis - Techniques
 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