
1. Business Analysis is the practice of enabling change in an organizational context, by defining needs and recommending solutions that deliver value to stakeholders. The set of tasks and techniques that are used to perform business analysis are defined in A Guide to the Business Analysis Body of Knowledge® (BABOK®Guide).
1.1. BABOK v1.6 was published in 2006
1.2. BABOK v2 was published in 2009
1.3. BABOK v3 was published in 2015
2. BABOK®3 consists of: 6 Knowledge Areas, 30 Tasks, 46 Techniques, 6 Underlying Competencies of Business Analyst, 1 Business Analysis Core Concept Model (BACCM), 5 Perspectives.
2.1. Download BABOK®3 Knowledge Areas vs Techniques (PDF)
3. What's new in the upcoming BABOK®3? 25.03.2014, IIBA Austria Chapter Meeting
3.1. https://www.youtube.com/watch?v=F2a5aO_Rxec
4. This freeware, non-commercial mind map (aligned with the newest version of BABOK®) was carefully hand crafted with passion and love for learning and constant improvement as well for promotion the BABOK® and business analysis profession and as a learning tool for candidates wanting to gain CBAP® qualification. (please share, like and give feedback - your feedback and comments are my main motivation for further elaboration. THX!)
4.1. Questions / issues / errors? What do you think about my work? Your comments are highly appreciated. Feel free to visit my website: www.miroslawdabrowski.com
4.1.1. http://www.miroslawdabrowski.com
4.1.2. http://www.linkedin.com/in/miroslawdabrowski
4.1.3. https://www.google.com/+MiroslawDabrowski
4.1.4. https://play.spotify.com/user/miroslawdabrowski/
4.1.5. https://twitter.com/mirodabrowski
4.1.6. miroslaw_dabrowski
5. BABOK V3 Promotional Vide
5.1. https://www.youtube.com/watch?v=tX2hjd-37pw&feature=youtu.be
6. BABOK v3 Demystified
6.1. https://www.youtube.com/watch?v=1OTKAaoK7lE
7. Interactive BABOK®3 Glossary
7.1. Interactive BABOK®3 Glossary
8. Knowledge Areas (6)
8.1. Business Analysis Planning and Monitoring (Chapter 3)
8.2. Elicitation and Collaboration (Chapter 4)
8.3. Requirements Life Cycle Management (Chapter 5)
8.4. Strategy Analysis (Chapter 6)
8.5. Requirements Analysis and Design Definition (Chapter 7)
8.6. Solution Evaluation (Chapter 8)
8.7. Underlying Competencies (Chapter 9)
9. Techniques (46)
9.1. Acceptance and Evaluation Criteria Definition (10.1)
9.2. Backlog Management (10.2)
9.3. Balanced Scorecard (10.3)
9.4. Benchmarking and Market Analysis (10.4)
9.5. Brainstorming (10.5)
9.6. Business Capability Analysis (10.6)
9.7. Business Model Canvas (10.7)
9.8. Business Rules Analysis (10.8)
9.9. Collaborative Game (10.9)
9.10. Data Dictionary (10.10)
9.11. Data Flow Diagrams (10.11)
9.12. Data Modeling (10.12)
9.13. Decision Analysis (10.13)
9.14. Decision Modeling (10.14)
9.15. Document Analysis (10.15)
9.16. Estimation (10.16)
9.17. Focus Groups (10.17)
9.18. Functional Decomposition (10.18)
9.19. Glossary (10.19)
9.20. Interface Analysis (10.20)
9.21. Interviews (10.21)
9.22. Item Tracking (10.22)
9.23. Lessons Learned (10.23)
9.24. Metrics and Key Performance Indicators (KPIs) (10.24)
9.25. Non-functional Requirements Analysis (10.25)
9.26. Observation (10.26)
9.27. Organization Modeling (10.27)
9.28. Priortization (10.28)
9.29. Process Analysis (10.29)
9.30. Process Modeling (10.30)
9.31. Prototyping (10.31)
9.32. Reviews (10.32)
9.33. Risk Analysis and Management (10.33)
9.34. Roles and Permissions Matrix (10.34)
9.35. Root Cause Analysis (10.35)
9.36. Scenarios (10.36)
9.37. Scope Modeling (10.37)
9.38. Sequence Diagrams (10.38)
9.39. Stakeholder List, Map, or Personas (10.39)
9.40. State Modeling (10.40)
9.41. Survey or Questionnaire (9.41)
9.42. SWOT Analysis (10.42)
9.43. User Cases (10.43)
9.44. User Stories (10.44)
9.45. Vendor Assessment (10.45)
9.46. Workshops (10.46)
10. Tasks (30)
10.1. Task characteristics
10.1.1. Has a purpose
10.1.2. Has inputs
10.1.3. Is complete
10.1.4. Uses techniques
10.1.5. Involves stakeholders
10.1.6. Has outputs / results
10.1.7. Tasks may be performed formally or informally.
10.1.8. Tasks may be performed in any order.
10.2. Tasks are grouped into Knowledge Areas (6)
10.2.1. Business Analysis Planning and Monitoring (Chapter 3)
10.2.1.1. 3.1 Plan Business Analysis Approach
10.2.1.2. 3.2 Plan Stakeholder Engagement
10.2.1.3. 3.3 Plan Business Analysis Information Management
10.2.1.4. 3.4 Plan Business Analysis Governance
10.2.1.5. 3.5 Identify Business Analysis Performance Improvements
10.2.2. Elicitation and Collaboration (Chapter 4)
10.2.2.1. 4.1 Prepare for Elicitation
10.2.2.2. 4.2 Conduct Elicitation
10.2.2.3. 4.3 Confirm Elicitation Results
10.2.2.4. 4.4 Communicate Business Analysis Information
10.2.2.5. 4.5 Manage Stakeholder Collaboration
10.2.3. Requirements Life Cycle Management (Chapter 5)
10.2.3.1. 5.1 Trace Requirements
10.2.3.2. 5.2 Maintain Requirements
10.2.3.3. 5.3 Prioritize Requirements
10.2.3.4. 5.4 Assess Requirements Changes
10.2.3.5. 5.5 Gain Consensus
10.2.4. Strategy Analysis (Chapter 6)
10.2.4.1. 6.1 Analyze Current State
10.2.4.2. 6.2 Define Future State
10.2.4.3. 6.3 Assess Risks
10.2.4.4. 6.4 Define Change Strategy
10.2.5. Requirements Analysis and Design Definition (Chapter 7)
10.2.5.1. 7.1 Specify and Model Requirements
10.2.5.2. 7.2 Verify Requirements
10.2.5.3. 7.3 Validate Requirements
10.2.5.4. 7.4 Define Requirements Architecture
10.2.5.5. 7.5 Define Solution Options
10.2.5.6. 7.6 Analyze Potential Value and Recommend Solution
10.2.6. Solution Evaluation (Chapter 8)
10.2.6.1. 8.1 Measure Solution Performance
10.2.6.2. 8.2 Analyze Performance Measures
10.2.6.3. 8.3 Assess Solution Limitations
10.2.6.4. 8.4 Assess Enterprise Limitations
10.2.6.5. 8.5 Recommend Actions to Increase Solution Value
11. Underlying Competencies of Business Analyst (6)
11.1. Analytical Thinking and Problem Solving
11.2. Behavioral Characteristics
11.3. Business Knowledge
11.4. Communication Skills
11.5. Interaction Skills
11.6. Software Applications
12. Perspectives (5)
12.1. What is it?
12.1.1. Perspectives describe specialized disciplines within the practice of business analysis. A Perspective is a set of behaviours, terminology, and attitudes used by a business analyst within their specific type of business analysis work.
12.2. Perspectives have the following structure
12.2.1. Change Scope
12.2.2. Business Analysis Scope
12.2.3. Impact on Knowledge Areas
12.2.4. Methodologies and Techniques
12.2.5. Underlying Competencies
12.3. Agile
12.4. Business Intelligence
12.5. Information Technology
12.6. Business Architecture
12.7. Business Process Management
13. The Business Analysis Core Concept Model™ (BACCM™)
13.1. The Business Analysis Core Concept Model™ (BACCM™) - Business Analysis Framework (a.k.a. The Turtle)
13.1.1. 6 core recurring concepts
13.1.2. Uniting a community of practitioners requires common terminology
13.2. 6 major questions (six Core Concepts) need to be answered (central questions in business analysis)
13.2.1. Change
13.2.1.1. What is the kind of change we're doing?
13.2.1.2. A controlled transformation of the organization / enterprise.
13.2.2. Need
13.2.2.1. What are the need we're trying to satisfy?
13.2.2.2. A problem, opportunity, or constraint with potential value to a stakeholder.
13.2.3. Solution
13.2.3.1. What are the solutions we're trying to satisfy?
13.2.3.2. A specific way of satisfying one or more needs in a context.
13.2.4. Value
13.2.4.1. What do stakeholders consider to be of value?
13.2.4.2. The worth, importance, or usefulness of something to a stakeholder within a context.
13.2.5. Stakeholder
13.2.5.1. Who are the stakeholders involved?
13.2.5.2. A group or individual with a relationship to the change or the solution.
13.2.6. Context
13.2.6.1. What is the context in which we and the solution are in?
13.2.6.2. The circumstances that form the setting for a change and allows for further understanding and assessment of the change.
14. Stakeholders
14.1. Business Analyst
14.2. Change Control Board (CCB)
14.3. Customer
14.4. Domain Subject Matter Expert (SME)
14.5. End User
14.6. Implementation Subject Matter Expert (SME) - examples
14.6.1. Change Manager
14.6.2. Configuration Manager
14.6.3. Database Administrator
14.6.4. Developer / Software Engineer
14.6.5. Information Architect
14.6.6. Organizational Change Management Professionals
14.6.7. Project Librarian
14.6.8. Solution Architect
14.6.9. System Architect
14.6.10. Trainer
14.6.11. Usability Analyst
14.6.12. Usability Professional