a BA's role in an agile environment

1. Agile Methods and the Business Analyst Mark Foley

3. Top 10 Reasons for Success – why are we here ?

6. The other view

8. Manifesto for Agile Software Development That is, while there is value in the items on the right, we value the items on the left more.” http://www.agilemanifesto.org Individuals & Interactions over Processes & Tools Working Software over Comprehensive Documentation Customer Collaboration over Contract Negotiation Responding to Change over Following a Plan

9. Bad Ideas?

10. Agile Today

12. Scrum, FDD, XP Agile Methodologies Project Management Engineering FDD XP Scrum

13. Scrum: Lifecycle 8. Product Increment (potentially shippable) 6. Day 5. Sprint (2-4 weeks) 4. Tasks detailed by the team 1. Vision (ROI, milestones, releases) 2. Product Backlog, with features prioritized by the Product Owner 3. Sprint Backlog 7. Daily Standup Meeting 9. Inspect and Adapt

19. Stories “ A User Story is a story, told by the user, specifying how the system is supposed to work , written on a card, and of a complexity permitting estimation of how long it will take to implement. The User Story promises as much subsequent conversation as necessary to fill in the details of what is wanted . The cards themselves are used as tokens in the planning process after assessment of business value and [possibly] risk. The customer prioritizes the stories and schedules them for implementation.”

22. Traditional RM Functional Nonfunctional Business Requirements Vision and Scope Document User Requirements Business Rules Quality Attributes Use Cases System Requirements Functional Requirements Constraints External Interfaces Software Requirements Specification

23. Large Scale Agile Functional Nonfunctional Business Requirements Vision and Scope Document User Requirements Business Rules Quality Attributes Use Cases System Requirements Story Constraints External Interfaces Backlog

25. The Agile Lifecycle BA Effort Time Project Duration

27. Cost to Change Curve Cost of Change Lifecycle Stage $ $ $ $ $ ‘ What if we got good at reducing the costs of ongoing changes? Kent Beck, 1999

29. Embrace Change That is, while there is value in the items on the right, we value the items on the left more.” http://www.agilemanifesto.org Individuals & Interactions over Processes & Tools Working Software over Comprehensive Documentation Customer Collaboration over Contract Negotiation Responding to Change over Following a Plan