BUSINESS
ANALYSIS
FOUNDATION
Lesson 2 – Business Analysis in Projects
CONTENT
Software Development
01 Life Cycle
Project Management
02 Model
03 How to work in Scrum
CONTENT
Software Development
01 Life Cycle
Project Management
02 Model
03 How to work in Scrum
Software Development Life Cycle (SDLC)
Software Development Life Cycle (SDLC) is a process used by the software industry to
design, develop and test high quality softwares. The SDLC aims to produce a high-quality
software that meets or exceeds customer expectations, reaches completion within times and
cost estimates.
Copyright © by Hai Lúa 4
Software Development Life Cycle (SDLC)
Software Development Life Cycle (SDLC) is a process used by the software industry to
design, develop and test high quality softwares. The SDLC aims to produce a high-quality
software that meets or exceeds customer expectations, reaches completion within times and
cost estimates.
Planning
Deployment &
Requirement
Maintenace
Testing Design
Development
Copyright © by Hai Lúa 5
SDLC BA’S ACTIVITIES
1 PLANNING Deployment
Planning
& Requirement
Maintenace
• Reach out to project, find out more about project background, client’s objective;
• Detemine the project and product scope, project type.
• Identify business analysis deliverables; SDLC
• Determine the scope of work for the business analysis activities;
• Determine which activities the business analyst will perform and when;
• Develop estimates for business analysis work.
Testing Design
• => Output: BA’s plan
Development
Copyright © by Hai Lúa 6
SDLC BA’S ACTIVITIES
2 Requirement Deployment
Planning
& Requirement
• Requirement Elicitation: Maintenace
• Interact with client to gather, elicit requirement from customer (via meeting,
document,..);
• Determine the operational and problem context; SDLC
• Identify business organization structure, technical and legal environment, user
characteristics, business processes, work flows, data flows, information entities…
• Document gathered requirements => BRD – Business Requirement Document
Testing Design
• Requirement Analysis:
• Analyses key business objects and high level business requirements;
• Decompose from a high level requirement to lower requirements;
Development
• Derives customer’s requirements into product requirements in technical terms
necessary for product design => SRS – Software Requirement Specification
• Establish the internal & external review of SRS and get final confirmation;
• Conduct meeting to transfer requirement to development team…
Copyright © by Hai Lúa 7
SDLC BA’S ACTIVITIES
3 Design Deployment
Planning
& Requirement
Maintenace
• Support Designer in UI/UX design process;
• Facilitate the design process with business stakeholders, internal team;
• Support Technical team in system design process: database diagram, solution,
SDLC
system structure.
Testing Design
Development
Copyright © by Hai Lúa 8
SDLC BA’S ACTIVITIES
4 Development Deployment
Planning
& Requirement
Maintenace
• Works with finishing and polisting the requirements
• Support the development process by clarifying requirements much deeper;
• Gathering remaining user requirements and managing change requests.
SDLC
• Update change requirements if any.
Testing Design
Development
Copyright © by Hai Lúa 9
SDLC BA’S ACTIVITIES
5 Testing Deployment
Planning
& Requirement
Maintenace
• Assists QA team with review test plans and scripts,
• Sign-off of functional and non-functional test results;
• Takes part in planning and conducting the UAT and assess the results;
SDLC
• Plans further user trainings.
Testing Design
Development
Copyright © by Hai Lúa 10
SDLC BA’S ACTIVITIES
Deployment &
6 Maintenance
Deployment
Planning
& Requirement
Maintenace
• Coordinates the processes of the production deployment and integration in
customer’s business environment;
• Take part in pre-implementation readiness review and post-implementation SDLC
review;
Testing Design
Development
Copyright © by Hai Lúa 11
Life cycle of e-wallet?
Copyright © by Hai Lúa 12
Copyright © by Hai Lúa 13
CONTENT
Software Development
01 Life Cycle
Project Management
02 Model
03 How to work in Scrum
PROJECT MANAGEMENT METHODOLOGY
Waterfall RUP
Spiral Incremental
Agile Others
Copyright © by Hai Lúa 15
WATERFALL MODEL
Copyright © by Hai Lúa 16
WATERFALL MODEL
Waterfall Model is a sequential model that
divides software development into pre-
defined phases.
Each phase must be completed before the
next phase can begin with no overlap
between the phases.
Non-IT BA
Each phase is designed for performing
specific activity during the SDLC phase.
It was introduced in 1970 by Winston Royce.
Copyright © by Hai Lúa 17
AGILE METHODOLOGY
The Agile methodology is a way to manage a project by breaking it up
into several phases.
Non-IT BA
Copyright © by Hai Lúa 18
AGILE METHODOLOGY
Agile Software Development is
a set of methods and practices
where solutions evolve through
collaboration between self-
organizing, cross-functional
teams
Non-IT BA
Copyright © by Hai Lúa 19
AGILE FRAMEWORKS
Non-IT BA
Copyright © by Hai Lúa 20
AGILE VALUES
Copyright © by Hai Lúa 21
12 AGILE PRINCIPLES
Copyright © by Hai Lúa 22
AGILE VS WATERFALL
Copyright © by Hai Lúa 23
CONTENT
Software Development
01 Life Cycle
Project Management
02 Model
03 How to work in Scrum
SCRUM FRAMEWORK
Scrum (n): A framework
within which people can
address complex
adaptive problems,
while productively and
creatively delivering
products of the highest
possible value.
Scrum is:
• Lightweight
• Simple to understand
• Difficult to master
Copyright © by Hai Lúa 25
SCRUM’S RULES
Copyright © by Hai Lúa 26
SCRUM TEAM
The Scrum team includes the:
• Product Owner
• Scrum Master
• The Development Team
➢ Scrum Teams are self-organizing
and cross-functional.
The Scrum framework encourages a high level
of communication among team members, so
that the team can:
✓ Follow a common goal
✓ adhere the same norms and rules
✓ show respect to each other
Copyright © by Hai Lúa 27
SCRUM TEAM
Copyright © by Hai Lúa 28
SCRUM TEAM
The Product Owner: is responsible for maximizing the value of the product
resulting from work of the Development team.
The Development Team: consist of professionals who do the work
delivering a potentially releasable Increment of the “Done” product at the
end of each Sprint. Only members of the Development Team create the
Increment.
The Scrum Master: is responsible for promoting and supporting Scrum as
defined in the Scrum Guide. Scrum Masters do this by helping everyone
understand Scrum theory, practices, rules, and values. He helps everyone to
maximize the value created by the Scrum team.
Copyright © by Hai Lúa 29
SCRUM ARTIFACTS
Agile scrum artifacts
are information that a scrum
team and stakeholders use to
detail the product being
developed, actions to produce
it, and the actions performed
during the project. The main
agile scrum artifacts are
product backlog, sprint
backlog, and increments
Copyright © by Hai Lúa 30
SCRUM ARTIFACTS
• Product backlog: is an ordered list of verything that is known to be
needed in the product
• Sprint backlog: the set of Product Backlog items selected for the
Sprint, plus a plan for delivering the product Increment and
realizing the Sprint Goal.
• Increment: The Increment is the sum of all the Product Backlog
items completed during a Sprint and the value of the increments of
all previous Sprints
Copyright © by Hai Lúa 31
SCRUM EVENTS
Copyright © by Hai Lúa 32
SCRUM EVENTS
A sprint (2-4 weeks): is a short, time-boxed period when a scrum team works to
complete a set amount of work.
Sprint planning (4-8h): is an event in scrum that kicks off the sprint. The purpose
of sprint planning is to define what can be delivered in the sprint and how that
work will be achieved. Sprint planning is done in collaboration with the whole
scrum team.
Daily scrum (15p’): to review the Sprint progress and to synchronize activities and
create a plan for the next 24 hours to ensure Sprint goal.
Sprint review (4h): to inspect the Increment and adapt the Product Backlog if
needed.
Sprint retrospective (3h): is an opportunity for the Scrum Team to inspect itself
and create a plan for improvements to be enacted during the next Sprint.
Copyright © by Hai Lúa 33
Copyright © by Hai Lúa 34
