3 Key Concepts Business Analysis Core Concept Model™ (BACCM™) Key Terms Requirements Classification SchemaStakeholdersRequirements and Design
4 Business Analysis Core Concept Model™ Change – the act of transformation in response to a needNeed – a problem or opportunity to be addressedSolution – a specific way of satisfying a need(s) in a contextStakeholder (same 11 as in v2.0) – a group or individual with a relationship to the change, the need, or the solutionValue – the worth, importance, or usefulness of something to a stakeholder within a contextContext – the circumstances that influence, are influenced by, and provide understanding of the changeWithin each KA description there are examples of how the core concepts may be used and/or applied during the tasks within the KA. If any of the core concepts experience a change, it should cause us to re-evaluate these core concepts and their relationships to value delivery.
5 Key Terms What is business analysis? Who is A BUSINESS ANALYST? Business analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders.Any person performs business analysis tasks described in the BABOK® Guide, no matter their job title or organizational role.
6 BUSINESS ANALYSIS INFORMATION Key TermsBUSINESS ANALYSIS INFORMATIONDESIGNBroad and diverse sets of information that business analysts analyze, transform, and report. It is information of any kind – at any level of detail – that is used as an input to, or is an output of, business analysis workA design is a usable representation of a solution. Design focuses on understanding of value might be realized by a solution if it is built.
7 Key Terms ENTERPRISE ORGANIZATION An enterprise is a system of one or more organizations and the solutions they use to pursue a shared set of common goals.An autonomous group of people under the management of a single individual or board, that works toward common goals and objectives.
8 Key Terms PLAN REQUIREMENT A plan is a proposal for doing or achieving something. Plans describe a set of events, the dependencies among the events, the expected sequence, the schedule, the results or outcomes, the materials or resources needed, and the stakeholders involved.A requirement is a usable representation of a need.
9 Requirements Classification Schema Business RequirementsStakeholder RequirementsSolution RequirementsFunctional RequirementsNon-Functional (or Quality of Service) RequirementsTransition Requirements
10 Stakeholders Business Analyst Domain SME Project Manager End User Implementation SMESupplierCustomerSponsorOperational SupportUserTester
11 Requirements and Design Requirements focus on the needDesign focuses on the solution
12 Perspectives Used within business analysis work to provide focus to tasks and techniques specific to the context of the initiatives. Most initiatives are likely to engage one or more perspectives.AgileBusiness IntelligenceInformation TechnologyBusiness ArchitectureBusiness Process Management
13 Perspectives Structure Change Scope – what parts of the enterprise the change encompasses when viewed from this perspective and to what extent it impacts the objectives and operations of the enterprise . Also – type of problems solved, solutions considered, approach, and valueBusiness Analysis Scope – describes key stakeholders and the BA role within the initiative. Also defines likely outcomes of BA workMethodologies, Approaches and Techniques – specific to those that are unique to each perspectiveUnderlying Competencies – those that are most prevalent to that perspectiveImpact on Knowledge Areas– describes how knowledge areas are applied or modified. Also explains how specific activities within a perspective are mapped to tasks
14 Updated (from 2.0) Task Structure V 3.0V 2.0PurposeDescriptionInputsElementsTechniquesStakeholdersOutputsPurposeDescriptionInputsElementsGuidelines and ToolsTechniquesStakeholdersOutputs
16 Knowledge Areas Business Analysis Planning and Monitoring Elicitation and CollaborationRequirements Life Cycle ManagementStrategy AnalysisRequirements Analysis and Design DefinitionSolution Evaluation
17 Business Analysis Planning and Monitoring Renamed TasksOne new TaskElements moved around within the KAVersion 3 continues to address the BA role in defining the work andapproach for the initiative.
18 Elicitation and Collaboration (2.0 Elicitation) More guidance for practitionersUnplanned ElicitationBA information referenced throughout (not just requirements as theobject of elicitationOne renamed taskOne new taskThe focus remains similar but has expanded to include the new topic ofCollaboration.
19 Requirements Life Cycle Management (2.0 Requirements Management and Communication)Communication activities now in Elicitation and Collaboration KARequirements Business Analysis InformationUpdated to recognize the fact that requirements have their own life cycle andRequirements management is an ongoing activity.
20 Strategy Analysis (2.0 Enterprise Analysis) Expanded purpose and a new nameStrategy Analysis is broaderNot only involves the upfront work, but current state research, definingthe future (desired) state, developing the change strategy to achieve thedesired business outcomes and assess the risks inherent in the changeStrategy.
21 Requirements Analysis and Design Definition BAs have involvement with design activitiesIncorporates Tasks from 2.0 KA Solution Assessment and ValidationActivities involved with the proposed solution are part of this KA.
22 (2.0 Solution Assessment and Validation) Solution Evaluation(2.0 Solution Assessment and Validation)More focus on evaluating solutions (less on implementation)Is value being delivered by a solution?Anything hindering the organization from receiving full valuefrom a solution?
23 Underlying Competencies Analytical Thinking and Problem SolvingCreative ThinkingDecision MakingLearningProblem SolvingSystems ThinkingConceptual ThinkingVisual ThinkingBehavioral CharacteristicsEthicsPersonal AccountabilityTrustworthiness