1. Real time Practices
Agile Vs Standard
Presenting by
KVN Pavan Kumar
989385640
Connect me through..

2. Challenges in Project Management
1. Lack of Shared Vision / Understanding
2. Getting time with Product management /
Business Needs
3. Forward Looking
4. Building Relationship
5. Requirement failure fear
6. Lack of Techniques and Tools
1. Set expectation and get time commitment
during inception
2. Acceptance of New technology and
Process Updation
3. Recommendation gap while Requirement
Development
4. Requirement Feasibility
5. Iteration & Coverage on Shared
Understanding
6. Everyone is moving on Same direction…

3. Where BA can
involve with a focus
Collaborative Activities of BA
Supporting roles of
•Project Manager
•Organizational Developer
•QA
•Technical Designer

4. BA Activity Scope
Under different Stages
Standard Functions of BA

5. Project Documentation Levels

6. BA ROLE IN….
SDLC PRACTICE AGILE PRACTICE
 Define Business Requirements
 Identify Project Stakeholders and User Classes
 Elicit Requirements
 Analyze Requirements
 Write Requirement Specification
 Model the Requirements
 Lead Requirements Validation
 Facilitate Requirements Prioritization
 Manage Requirements
 Validate Requirements
 Produce and explore requirements in
collaboration with users, at a different level of
detail than we’re used to
 Identify missing requirements
 Work with users to develop acceptance criteria
or test cases for the system
 Mentor developers on how things work in the
business domain
 Assume the role of “Product Owners”
 Work ahead of the team to get clarity on some
(not all) requirements before the next iteration
 Stand-in for users only when they're unavailable
(as opposed to being the “permanent“ bridge
between developers and users)
 Wear different hats: designer, tester, facilitator,
product owner, etc
 Create a shared understanding of what the
product is supposed to do

7. Challenges of BA to enter into Agile Environment
The Agile Requirements model differs from our traditional approach for IT
project management.
Agile requires that the BA produce requirements faster by analyzing
through observation or trial-and-error instead of attempting to find out all
the facts before development begins
Lengthy Business Requirement Documents are not required;
The level of detail is different.
Less has become more

8. How BA fit to Agile Environment
Communication
 User stories
 Active feedback loops
 Integrating the customer’s perspective
Setting the Roadmap
 Systems Perspective
 Concurrent Phases
 Testing
Keeping the team on course
 Speaking the same language
 Asking the same questions
 Moving towards the same end-game
Business Analysts provide significant value, all
team members have a responsibility to do
“business analysis.”
With the increasing prevalence of Agile, this
function will be even more valuable to a
successful deployment.
In an Agile environment, the Business Analysts
provides this input early on.
Even as the business needs are identified, the
analysts should be providing the information
within the context of the technological
capabilities, both the functional and non-
functional aspects.

9. Day life of a….
Business Analyst Project Manager
Daylife_BA DayLifeofPM

10. Day life of a….
Business Analyst Project Manager
Daylife_BA DayLifeofPM