Cristian Leon presents six techniques that business analysts can use to better perform their role: (1) Planning, such as using a requirements management plan and RACI matrix; (2) Listening actively to stakeholders; (3) Mind mapping and brainstorming to map concepts; (4) Analyzing requirements using techniques like MoSCoW prioritization; (5) Creating artifacts like user stories with details like acceptance criteria; and (6) Keeping requirements visible and understood by stakeholders through ongoing communication. The presentation aims to help business analysts and those wanting to be analysts exercise their "6-pack" of analysis skills.

1. Business Analysis
Techniques:
Exercise Your 6-pack
Cristian Leon | BA | Yonder
125th April 2015
#CodeCampIasi

3. who works as a BA?
who wants to be a BA?
3
BA= Business Analyst

4. Who is the speaker?
Cristian | BA | biking fan
I'm a BA that likes to drill into details and ask
questions.
A good life is a happy life and BAs can make
your life better.
4
email: Leon.Cristian@yahoo.com

5. Why this presentation?
KEY in 2015
Keep Educating Yourself
5

6. The 6-pack
6
1. Plan 2. Listen
3. Map 4. Analyse
5. Create
6. Keep in
contact

7. 1ST technique:
Planning
7
1. Plan

8. Requirements management
(REQM)
8

9. 9
Example: The REQM plan that I use

10. Requirements management
The RACI matrix
10
Actions
SMEs Me (BA)
Client
(PO)
Team
Analyze customer needs C R, A C I
Define High Level Requirements C R A I
Create user stories C R, A C I
Get user stories reviewed, validated,
prioritized
C R A I
Obtain commitment of the team R I A
Perform traceability R,A I
Manage requirements changes I R, A C C

11. 2nd technique:
Listen (actively)
11
2. Listen

12. Listen. Observe. Record.
12

13. 3rd technique:
mapping concepts
13
3. Map

14. Mind mapping, brainstorming
14

15. 4th technique:
analyse
15
4. Analyse

16. “Much of business or technical
requirements is not documented
anywhere—it resides in the minds of
stakeholders, in feedback that has yet to
be obtained from end users”
ModernAnalyst.com
16

17. 17
Suggestion: use MoSCoW analysis

18. Output
example:
Prioritized
Backlog
18

19. 5th technique:
Elicitate, write, detail
19
5. Create

20. Template for an User Story
1.Title
2.Description
3.Goal
4.Current functionality
5.Acceptance criteria
6.Wireframe / Mockup / Prototype / Diagram
7.Technical info
8.Clarifications
20

21. 21
How about
visualizing
the stories on
a digital
strip?

22. The 6-pack
22
6. Keep in
contact

23. “One of the key objectives of business
analysis is to ensure that requirements
are visible to and understood by all
stakeholders.”
IIBA BABOK 2.0
23

24. Keep in mind: Pareto principle
24
80% of your users will mostly use 20% of your application.
20% of your user stories will bring 80% of the total customer value.
80% of the technical development complexity will be in 20% of your stories.

25. Questions? | Answers.
25
1. Plan 2. Listen
3. Map 4. Analyse
5. Create
6. Keep in
contact

26. References + images sources
1. http://www.iiba.org/babok-guide.aspx
2. http://www.modernanalyst.com/Resources/Articles/tabid/115/ID/1427/An-
Overview-of-Requirements-Elicitation.aspx
3. http://www.batimes.com/articles/beyond-use-cases-with-storyboarding.html
4. http://mariolucero.cl/agile/how-can-we-use-pareto-principle-on-agile-
methodology/
5. https://msdn.microsoft.com/en-us/library/jj159334.aspx
6. http://blogs.atlassian.com/2012/08/unlock-the-power-of-agile-introducing-
greenhopper-6/
7. http://justiniskandar.empowernetwork.com/blog/applying-pareto-principle-
and-parkinsons-law
26

27. 27
Thank you
Cristian Leon | BA | Yonder
25th April 2015
#CodeCampIasi