Scribd
Upload
9 views3 pages

Session Notes - IT BA

The document discusses the importance of understanding the Software Development Life Cycle (SDLC) for Business Analysts (BAs) as they collaborate with technical teams throughout various stages of application development. It outlines the roles involved in each phase of the SDLC, including analysis, planning, implementation, testing, deployment, and maintenance. Additionally, it touches on methodologies like Waterfall, V Model, and Agile, as well as stakeholder engagement strategies and the roles of product owners and scrum teams.

Uploaded by

cloarde
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9 views3 pages

Session Notes - IT BA

The document discusses the importance of understanding the Software Development Life Cycle (SDLC) for Business Analysts (BAs) as they collaborate with technical teams throughout various stages of application development. It outlines the roles involved in each phase of the SDLC, including analysis, planning, implementation, testing, deployment, and maintenance. Additionally, it touches on methodologies like Waterfall, V Model, and Agile, as well as stakeholder engagement strategies and the roles of product owners and scrum teams.

Uploaded by

cloarde
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

1) Why being a Business analyst to learn about SDLC ?

Because Being a BA we work with technical team ( Development team ) , when we develop
the project there is a process of application development

2) What SDLC stands for ?

Software development life cycle – it explains us about the stages of application development

3) Is it really needed to know what SDLC and how it works ?

Yes it requires because there are different stages are there when we want to develop the project

Analysis – BA

Planning and Design – Project Management ( Project planning ) , Business analyst – ( translate
Business requirements to technical requirements ) , architect – ( develop solution architecture for
the project )

Implementation – Developers

Testing – Testers

Deployment and delivery – here we deploy the application followed by that we deliver the
project to the client

Maintenance - there will be support team who takes care of the problem arised to an end users
while they are working

4) Then what are all these i.e waterfall, V Model , Agile ?


Product owner :-

 Defining the Product vision and goal


 Epic – Large scale of solution
 User story - short description of requirement
 Product backlog – it’s a repository to store all the user stories

Scrum team :-

Scrum Master

Scrum ceremonies :-

 Sprint Planning
 Daily scrum
 Sprint Review
 Sprint Retrospection

Stakeholder Engagement :-

 Stakeholder Identification – power / Interest


o High Power High Interest – Manage closely
 Business owners, Technical owners, PM, BA, Architect
o High Power Low Interest – Keep satisfied
 SME, shareholders
o Low Power High Interest – Keep Informed
 Developers, testing team , End Users etc
o Low Power Low Interest – Minimum Effort
 Other stakeholders

 Stakeholder Analysis and Management


o RASCI Matrix

You might also like