Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Business Analysis
Techniques:
Exercise Your 6-pack
Cristian Leon | BA | Yonder
125th April 2015
#CodeCampIasi
who works as a BA?
who wants to be a BA?
3
BA= Business Analyst
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...
Why this presentation?
KEY in 2015
Keep Educating Yourself
5
The 6-pack
6
1. Plan 2. Listen
3. Map 4. Analyse
5. Create
6. Keep in
contact
1ST technique:
Planning
7
1. Plan
Requirements management
(REQM)
8
9
Example: The REQM plan that I use
Requirements management
The RACI matrix
10
Actions
SMEs Me (BA)
Client
(PO)
Team
Analyze customer needs C R, A C I
Define ...
2nd technique:
Listen (actively)
11
2. Listen
Listen. Observe. Record.
12
3rd technique:
mapping concepts
13
3. Map
Mind mapping, brainstorming
14
4th technique:
analyse
15
4. Analyse
“Much of business or technical
requirements is not documented
anywhere—it resides in the minds of
stakeholders, in feedbac...
17
Suggestion: use MoSCoW analysis
Output
example:
Prioritized
Backlog
18
5th technique:
Elicitate, write, detail
19
5. Create
Template for an User Story
1.Title
2.Description
3.Goal
4.Current functionality
5.Acceptance criteria
6.Wireframe / Mockup...
21
How about
visualizing
the stories on
a digital
strip?
The 6-pack
22
6. Keep in
contact
“One of the key objectives of business
analysis is to ensure that requirements
are visible to and understood by all
stakeh...
Keep in mind: Pareto principle
24
80% of your users will mostly use 20% of your application.
20% of your user stories will...
Questions? | Answers.
25
1. Plan 2. Listen
3. Map 4. Analyse
5. Create
6. Keep in
contact
References + images sources
1. http://www.iiba.org/babok-guide.aspx
2. http://www.modernanalyst.com/Resources/Articles/tab...
27
Thank you
Cristian Leon | BA | Yonder
25th April 2015
#CodeCampIasi
Business analysis techniques   exercise your 6-pack
Upcoming SlideShare
Loading in …5
×

Business analysis techniques exercise your 6-pack

808 views

Published on

Business analysis techniques exercise your 6-pack

Published in: Technology
  • Be the first to comment

Business analysis techniques exercise your 6-pack

  1. 1. Business Analysis Techniques: Exercise Your 6-pack Cristian Leon | BA | Yonder 125th April 2015 #CodeCampIasi
  2. 2. who works as a BA? who wants to be a BA? 3 BA= Business Analyst
  3. 3. 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
  4. 4. Why this presentation? KEY in 2015 Keep Educating Yourself 5
  5. 5. The 6-pack 6 1. Plan 2. Listen 3. Map 4. Analyse 5. Create 6. Keep in contact
  6. 6. 1ST technique: Planning 7 1. Plan
  7. 7. Requirements management (REQM) 8
  8. 8. 9 Example: The REQM plan that I use
  9. 9. 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
  10. 10. 2nd technique: Listen (actively) 11 2. Listen
  11. 11. Listen. Observe. Record. 12
  12. 12. 3rd technique: mapping concepts 13 3. Map
  13. 13. Mind mapping, brainstorming 14
  14. 14. 4th technique: analyse 15 4. Analyse
  15. 15. “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
  16. 16. 17 Suggestion: use MoSCoW analysis
  17. 17. Output example: Prioritized Backlog 18
  18. 18. 5th technique: Elicitate, write, detail 19 5. Create
  19. 19. 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
  20. 20. 21 How about visualizing the stories on a digital strip?
  21. 21. The 6-pack 22 6. Keep in contact
  22. 22. “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
  23. 23. 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.
  24. 24. Questions? | Answers. 25 1. Plan 2. Listen 3. Map 4. Analyse 5. Create 6. Keep in contact
  25. 25. 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
  26. 26. 27 Thank you Cristian Leon | BA | Yonder 25th April 2015 #CodeCampIasi

×