Professional Documents
Culture Documents
Geet Sehgal Business Analysis Notes
Geet Sehgal Business Analysis Notes
Geet Sehgal Business Analysis Notes
Business Analysis
Geet Sehgal
1. REQUIREMENTS :
1
- JRP’s
- Workshops
- Interviews
- Limit premature technology requirements
2
Solution requirements :
- Legal requirements
- SLA
- Corporate standards
- Reliability/Availability/Maintainability/flexibility/useability
Transition requirements
3
Examples: Sales personnel must attend xyz before using xyz solution
If you ignore one that becomes a gap. The volume of the requirements have to be
right at the right size.
As late as possible
3 levels :
Operational : Initiative, themes, business epics, arch. Epics, user epics, user stories.
Work on specific business analysis.
Very few use this bifurcation. Not necessarily a BA does what a BA should and vice
versa
4
Tools -
1. Brainstorming
2. Change requests
3. Interviewing skills
4. Acceptance testing
5. Visual diagrams : process model, data models
6. Issue tracking
7. Workshops
BOTTOM LINE:
5
Levels of intensity : Timings, form in which things are documented, ad-hoc aka
chaotic approach.
Manage change by m
aintaining communications between the developer and
business community.
BA you will not be able to pick the ideal methodology but you can significantly
improve the methodology at place
WATERFALL METHODOLOGY :
6
Role :
The BA :
> Each phase is similar to your role in Waterfall process : Mission statement and
high level business objectives
AGILE
7
2. Face to face conversations for most effective and efficient way to transferring
knowledge
3. The BA as product owner, the BA as developer and the BA (overall)
4. With any communication about the product, some degree of information
about the following required
- The Vision
- The Strategy
- High level stakeholders requirements
5. Sufficient solution as per the need of XP, Crystal, DSDM, Kanban, FDD, SCRUM
Approach or scrum/XP hybrid
6. Each small chunk is a known as sprint : goes through the following iterative steps
- Analysis
- Design
- Coding
- Testing
- IN XP (User story is developed) : Estimate and c oordinate individual work
Essentialities of AGILE:
8
- Kanban board
- Feature set or something similar
- Product owner maintains the backlog and BA is tasked with it
- Contain Business epics, requirement, user story formats used to elicit
- Backlog lives : Agile team prioritizes the log : Mostly informal
Scrum and scrum XP hybrids : THe role of anyone in an agile team is fluid and can
change at any moment as per the requirement of the project based on the user
story.
The BA needs a versatile set of tools to satisfy the agile premise. Decomposing or
flushing out :
True balancing act to find the requirements are good. The BA facilitates the
requirements for the sprint. The team may have to intervene.
The responsibility :
2. Future :
Likely scenarios :
9
Actual Duties vary from one to next organization. Sometimes it’s very senior
positions. Recognize the importance of these.
Mostly these are super users of applications and find suitable solutions to
problems from users perspective.
2. Writing
3. Arithmetic
4. Speaking
Connect with G
eet Sehgal below:
10
11