The document discusses Agile software development. It defines Agile as an evolutionary and collaborative process that produces potentially shippable working software in regular intervals for review. The document outlines the Agile manifesto and principles, compares Agile to traditional frameworks, and discusses how business analysts can add value to an Agile team by focusing on strategic activities like requirements analysis and product vision while facilitating collaboration between the team and customers.

1. 1

2. Here We are the Team RootKit 2
Going to Show You Something
Interesting About
Agile
Team Member Id
Al-Amin 152-35-1260
Mohammad Ali 152-35-1262
MD Hafizur Rahman 152-35-1258
Noman Sadick 152-35-1267
Tuhin Ahmed 152-35-1256

3. Agenda 3
 What is Agile Software Development ? What are the
Agile Business Objectives?
 Agile Manifesto & Principles.
 Comparison of Agile Project Management Framework.
 Business Analyst when s/he is part of the agile team.
 Conclusion

4. What is Agile Software
Development? 4
 Agile software development key concepts:
Evolutionary
Highly collaborative
Disciplined
Self organizing
Value-driven lifecycle
Active stakeholder participation
Changing needs of stakeholders

5. What is Agile Software
Development?
Where potentially shippable working
software is produced at regular
intervals for review and course
correction.
5

6. Agile Methods
6

7. 7Agile Methods - Manifesto

8. Agile Principles 8

9. Key Drivers for Implementing Agile 9
 Accelerating time-to-market o Enhancing
software quality o Increasing productivity
 Improving alignment between IT and business
objectives
 Improving project visibility
 Reducing cost
 Enhancing the ability to manage changing
priorities
 Reducing project risk o Reducing process
complexity

10. Agile versus Traditional 10

11. Agile Project Management
Framework
11
An Adaptable Approach o
Incremental Implementation
Iterative Development
Complexity and Risk Management
Focus Centered on Working
Software

12. Agile Project Management
Methodology
12
Planning
“Speculate”
Implementation
“Explore”
Close
Retrospectives
“Adapt”
Operations
Initiation
“Envision”

13. Comparison of Agile Project
Management Framework
13

14. 14

15. Agile Requirements by View 15
 Big view – Product
 Gain an overall understanding of what the product will be, and
plan the sequence of delivery.
 Agree on vision, scope, and time line for the entire product
 Pre-view – Release
 Define what product functionality to deliver in a given release
 Obtain agreement on the backlog items to deliver in the first
few iterations in the release
 Now-view – Iteration
 Identify enough requirements to deliver in an iteration to
enable the team to make a commitment for delivery

16. Product Owner and BA Roles
 Product Owner - Strategic
 Is external facing
 Handles product marketing and portfolio analysis
 Is responsible for the product vision, product roadmap, balances the
voice of the “customer” with the voice of the “business”
 Defines and adjusts the roadmap and release plans in response to
market needs o Product Owner - Tactical
16

17. Product Owner and BA Roles
Selects and negotiates backlog items to
deliver for each iteration
Elaborates on requirements for backlog items
(just-in-time)
Defines dependencies, balances value with risk
Defines criteria of acceptance (“doneness”)
for each item
17

18. How a BA Add Value to Agile
Team?
 Focus on the work NOT the role o With agile, value
comes from the customer
 Strategic activities:
Analyzing the market and the business case
Defining the product vision and roadmap
Developing requirements
Adjusting the product backlog • Determining the
delivery plans – Tactical activities:
18

19. How a BA Add Value to Agile
Team?
Specifying the items to be delivered in each
iteration
Determining when each iteration is complete
Analyzing dependencies between items
Helping the team analyze requirements stories
19

20. How A BA Add Value to Agile
Team?
 Working methods change in an agile environment
 Processes, products, and relationships change on an
agile team. How you:
Plan the work
Deliver the product
Represent requirements
Share the knowledge
Interact with your team and customer
Manage changing requirements
Document requirements
20

21. BA in an Agile Team - Summary
 Act as a mentor, not a bridge o Focus on modeling,
not documentation o Focus on Leadership –
facilitation, coaching and team building o Work in
an evolutionary manner
21

22. 22