There are a lot of statements that claim that Business Analysts are not needed in Agile or that there is no planning or documentation. However, this is absolutely not the case! Andrew Thorpe and Ryan McKergow will explain how all the essential Business Analysts competencies are still applicable and important within Agile, what are the values and behaviours that an Agile Business Analyst will need to embody, and what the day in the life of an Agile Business Analyst looks like.

1. 1

2. 2
You don’t have to throw out your old skills
How you behave matters
So what do I actually do day to day?
Overview

3. 3
You don’t have to
throw out your old skills

4. 4
Requirements Analysis

5. 5
Elicitation / Facilitation

6. 6
Requirements Management

7. 7
How you behave matters

8. 8
Agile Manifesto
We are uncovering better ways of developing software by doing it and helping
others do it. Through this we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right,
we value the items on the left more.

9. 9
It starts with you
“Everyone thinks of changing the
world, but no one thinks of changing
themselves.”
Leo Tolstoy

10. 10
Collaboration

11. 11
Transparency & accountability

12. 12
Adaptability

13. 13
So what do I actually do
day to day?

14. 14
Stand Up

15. 15
Story Kick Off

16. 16
Story Card Workshop

17. 17
Story Writing

18. 18
Showcases

19. 19
Retrospectives

20. 20
You don’t have to throw out your old skills
How you behave matters
So what do I actually do day to day?
Recap

21. 21
Thank you!
@awthorpe @rmckergow