Business Analyst (BA), Role Based On My Experience Is Not Confined To Requirements Gathering

Business Analyst (BA), role based on my experience is not confined to requirements gathering
and project documentation. There are numerous other ways that a BA can contribute to the team
and the project and play a critical role in successful implementation. The other roles people
expect BA to handle are:
1. Process Improvement within the team and organization – Defining process standards,
documentation standards and streamlining the process of project implementation.
2. Project Management (PM) – Many a times, BA is also expected to handle the role of PM
in the project and drive the project to successful implementation within the given timelines
and constraints (project scope, resources, etc...)
3. Quality Lead and Quality Analyst (QA) – In smaller to medium projects, BA is expected to
lead the QA team or perform Quality analysis (testing) for the project
4. Business Analysis (BA) – Last but not the least. This is the critical role we perform. This
ranges from defining/identifying the scope of the project in business requirements
document (BRD), gathering the details of the requirements and creating functional design
documents (FDD), handling change requests, etc…
The course outline below is designed in such a way that you will have all the knowledge and skills
sets to play any role successfully as indicated above and have the confidence level required to
perform the job with ease.
The course is designed based on the waterfall model. The details provided below will introduce
you to course content in brief and give you an overview
Different Models of SDP (Agile Methodology, Scrum, RUP, Staged Delivery) --

Now you are aware of project basics, the next couple of sessions are designed to provide you
details about different development models, process within each model, and the advantages of
each model.
 Staged Delivery
 Iteration / Incremental Development
o Agile / Scrum (Define Sprint, Development Sprint, Stabilization Sprint)
o RUP (Inception, Elaboration, Construction, Transition)
SDLC
1. Traditional Development Model

a. Waterfall Model
2. Iterative Models
a. Agile / Scrum
b. Staged Delivery Model
c. Rational Unified Process
d. Extreme Programming (XP)
e. Rapid Application Development (RAD)
f. Etc…
Agile Model -- Refer to attached PPT.
Agile SDLC Overview –

 Provides the clear high-level view of agile software development. Including different kinds
of sprints, activities during each sprint, meetings during each sprint and the approach to
each sprint, people involved etc...
Agile Development –
 This document provides an instance of company research and the factors they
determined during their research which helped them to make a decision to use agile
model over the traditional waterfall model, to suite their business needs.
 This document also provides basics concepts on agile development.
1. Agile (Iteration) / Scrum (Sprint) – A period of 2 – 4 weeks is considered as iteration in

agile development model. E.g. Project of 4 months – 2 Week iterations – 8 Iterations)
Types of Sprints / Iterations –

2. Define Sprint –
o For any given project in Agile, you will only 1 or 2 define sprints. All the activities
we perform during the Planning/Definition phase of SDLC are performed during
the define sprint.
o Product Backlog – This is the document that contains the list of requirements /
functionalities that should be implemented in the system. This is similar to BRD in
SDLC model.
3. Development Sprint
o For any give project in Agile, you can have 1… N development sprints.
o All the activities that we perform from Analysis phase to Testing phase of SDLC
model are done in parallel during development sprints / iterations
4. Deployment (Stabilization) Sprint
o For any give project in Agile, you can have 1 or 2 of deployment sprints.
o All the activities that we perform during Implementation of SDLC model are
performed during this iteration.
5. Scrum Master –
o A project manager in scrum model is called as Scrum Master.
o A project manager in agile model is called as Servant Leader.
6. Stand-up Meeting (Daily Standup Meeting) –

o This is the daily meeting that is conducted early in the morning. The business
day in agile starts with this meeting.
o Purpose – Each team members defines the tasks that he/she is going to perform
for the day. Also provides the list issues or road blocks that one has to complete
their tasks as scheduled, if any.
 Issues – Normally becomes a road blocks if it cannot be addressed with
a 2 – 3 days
 Road Blocks – Issues that some one is waiting to be resolved to
continue their work.
7. Product Backlog Review Meeting ( Monday / Tuesday of Last week of the Sprint) –
o People involved - Entire BA Team, Lead Dev, Lead QA, Scrum Master, All
Business Users
o Purpose – To review the entire product backlog and based on the priority of the
requirements, identify the requirements that should be worked on during the next
sprint.
8. Sprint Backlog Review Meeting (Wednesday / Thursday of Last week of the Sprint)
o People involved - Entire BA Team, Lead Dev, Lead QA, PM, All Business Users
o Purpose – To review the sprint backlog and based on the priority of the
requirements and the estimates, identify the requirements that should be worked
on during the next sprint
o All the requirements that cannot be completed within the next sprint based on the
estimates will be moved back to Product backlog. This will help the team to
review these requirements along with other requirements and determine the
requirements for next sprint during the Product Backlog Review Meeting of next
sprint.
9. Sprint Review and Retrospective (On the last day afternoon of the sprint)
o Used to demo the application features that has been developed and tested to
business users.
o Addressing the tasks team want to Start, Stop and Continue doing from next
iteration/sprint for improvement of team performance.
– Team
• Scrum Master / PM (Servant Leader)
• SA / DA / BA
• Developers
– Backlogs
• Product Backlog
• Sprint Backlog
– Sprints / Iterations
• Define Sprints
• Development Sprints
• Stabilization Sprint
• Task Board
• Showing Product and Sprint backlogs
• Stand Up Meetings
• Product backlog review meeting and sprint planning
• Sprint review and retrospective (start doing, stop doing, continue
doing)
Staged Delivery Model
o Planning and Analysis will be done in waterfall model or traditional model

o Design to Testing will be done in iterative model
The approach to the staged delivery model will be emphasized while talking about Agile
model.
RUP
Refer to document “Why RUP and RUP Basics.pdf” for details.

Refer to document “RUP_bestpractices_TP026B.pdf” for details.
Refer to reference below for additional information:
1. Rational Process Library - http://www-01.ibm.com/software/awdtools/rmc/library/
2. Rational Unified Process - http://www-01.ibm.com/software/awdtools/rup/
3. Rational Method Composer – A tools that helps teams to implement processes effectively
for successful project implementation. - http://www-01.ibm.com/software/awdtools/rmc/
4. Agile using RUP Tools - To understand the relationship between Agile Process and how
RUP framework and tools helps teams to implement Agile Methodology.
http://www-01.ibm.com/software/rational/agile/
Rational Rose Modeler -

http://www-01.ibm.com/software/awdtools/developer/rose/modeler/
Work Out for First 4 Sessions

Assignment to Be Completed before Tomorrow's Session
1. Can you explain various activities as BA that you have performed from project Initiation phase
to Implementation Phase?
Approach - Think about all the tasks as BA you perform in each phase. Organize your thoughts
in a flow that each task will lead to another task.
2. Explain various activities that are performed by the team in each phase of SDLC?
Approach - Think about all the tasks a team will perform in each phase. Organize your thoughts
by each role in the team who perform the tasks, so that you can mention the role name first and
the tasks performed by those personnel within that phase.
3. Can you explain me about your Agile experience and explain the major differences you have
seen between traditional waterfall and Agile. Given a chance, which method you prefer and why?
Approach - Think about Agile methodology and draft the answer about agile first. Refer to the 2
and 3 question answers, determine the when a similar task will be performed in each phase and
think about performing a task early in the project, which will lead you to draft the differences and
preference with right reasons.

Business Analyst (BA), Role Based On My Experience Is Not Confined To Requirements Gathering

Uploaded by

Copyright:

Available Formats

Business Analyst (BA), Role Based On My Experience Is Not Confined To Requirements Gathering

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Business Analyst (BA), Role Based On My Experience Is Not Confined To Requirements Gathering

Uploaded by

Copyright:

Available Formats

Business Analyst (BA), role based on my experience is not confined to requirements gathering

Different Models of SDP (Agile Methodology, Scrum, RUP, Staged Delivery) --

1. Traditional Development Model

Agile Model -- Refer to attached PPT.

Agile SDLC Overview –

1. Agile (Iteration) / Scrum (Sprint) – A period of 2 – 4 weeks is considered as iteration in

Types of Sprints / Iterations –

6. Stand-up Meeting (Daily Standup Meeting) –

Staged Delivery Model

o Planning and Analysis will be done in waterfall model or traditional model

Refer to document “Why RUP and RUP Basics.pdf” for details.

Refer to reference below for additional information:

1. Rational Process Library - http://www-01.ibm.com/software/awdtools/rmc/library/

2. Rational Unified Process - http://www-01.ibm.com/software/awdtools/rup/

Rational Rose Modeler -

Work Out for First 4 Sessions

You might also like