BABOK Framework Overview - Aotea Studios

1 BABOK Framework Overview . BA Plans Stakeholder list Identified Needs Plan Requirements Plan, Report & Monitor Stakeholder roles/responsibility Plan BA Approach Conduct Stakeholder Plan BA Activities Plan, Monitor & Report BA communication plan Stakeholders List IN. OUT. Organisational Standards Analysis on Performance Management BA Communication Requirements management plan Actual Performance Metrics Identify/document team roles Define/create requirements process BA performance assessment Where the BA work occurs Identify BA deliverables Define metrics Identify communication needs Requirements Management Plan Assist in identifying stakeholders Plan requirements traceability Process improvement Formality/level of details of BA Define scope of work for BA Collect metrics Assess communication formats Organisational Performance

2 Standards Categorise stakeholders Structure requirements traceability Recommendations Requirements prioritisation Define tasks for BA in KAs Report on BA work progress Determine appropriate content Stakeholder Roles/Responsibility Analyze stakeholder influence Determine requirements attributes Lessons learned How change is handled Develop estimates for BA work Take preventive/corrective actions Determine frequency Define authority levels for BA work Plan requirements prioritisation BA Plan Communication with stakeholders Plan requirements prioritisation Assess the formality Business Analyst SelectIon of BA approach Select BA approach Plan a process for handling changes Plan a process for handling changes Expert judgement Domain Subject Matter Expert Stakeholder analysis End User Customer BA Planning & Monitoring Data collection methods Estimating techniques Implementation Subject Matter Expert Communications Requirements Analysis Operational Support Performance measurement Project Manager Configuration management Regulator Traceability System Quality Assurance Documentation Based on Technique Time & Cost Reporting Business

3 Goals Sponsor Stated Requirements Process analysis Business Objectives IN. OUT. Enterprise Architecture Validated Stated Requirements Variance Analysis Business Analysis Plans Supporting Materials Re-planning Assumptions, Constraints, Risks, Issues Change Control System Business Analyst Elicitation Analysis Results Lessons Learned Prepare for Elicitation Domain Subject Matter Expert Business Analyst Implementation Subject Matter Expert Domain Subject Matter Expert Customer/User Business Users Clarify scope for techniques used Confirm Results Technical Team Gather supporting materials Schedule all resources Confirm results of interviews Business Case Operational Support Project Manager Quality Assurance Solution Scope Regulator IN.

4 Notify appropriate parties Confirm results of observations BA Plan Quality Assurance Business Need/Problem/Opportunity Stakeholder Analysis Stated Requirements Sponsor Solution & Added Value Brainstorming Conduct Elicitation Document Results Document Analysis Focus Group Trace requirements Document stated requirements Interface Identification Capture requirement attributes Prioritise Interview Use glossary of domain terms Validate Requirements Requirements Observation Prototyping Use performance metrics Requirements Basis for prioritisation Define desired outcomes Business Goals Business Requirements Business Objectives Requirements Workshop Elicitation Identify challenges (risks) Identify assumptions Organisational RFI/RFQ/RFP Standards IN.

5 Define evaluation criteria Enterprise Architecture Reverse Engineering Deployed Solution Performance Metrics Define dependencies for benefit Business Analysis Plans Survey/Questionnaire Prioritised Approved Business Requirements Organise IN. realisation QA Plans Requirements Report on BA work progress Business Analyst Solution (Constructed/Deployed). Confirm alignment with Business Case Domain Subject Matter Expert Domain Subject Matter Expert Solution Design Follow organisational standards Technical Subject Matter Expert Business Users (line management) Solution Options Define Business Need Define level of granularity Operational Support Business Process Owners Validated Requirements Business Unit Managers Develop Business Case Use simple.

6 Consistent definitions Verify Requirements Project Manager Confirm strategic intent Document relationships Quality Assurance IT Managers Define problem/opportunity Business Rules Document dependencies Determine requirements quality Regulator End Users Identify & qualify Benefits Data Analysis Specify verification activity Validate Solution Sponsor Customers/Suppliers Identify & quantify Costs Assess Proposed Security Personnel Hierarchical Decomposition Specify & Model Determine Gap in Conduct initial risk assessment Networks Solution Performance Stakeholders with Governing Authority Requirements Project & Operational Teams Capabilities Set metrics for Costs & Benefits Event and State Modeling Determine Assumptions Solution selection Assess benefits delivered Business Rules Compile results Metrics and Reporting Solution recommendations Cost/Benefit Analysis Government/Regulatory Bodies Present results to Project Sponsor Specify using natural language & Constraints Assess solution metrics Coverage Matrix Sponsor Conduct internal Gap analysis Acceptance Criteria Models Assess solution providers Solution replacement or

7 Elimination Non-Functional Requirements Modelling formats Business constraints Data Model Conduct external Gap analysis Define Solution Scope Organisational Modeling Improvement opportunities Technical constraints Allocate Defect and Issue Reporting Develop target state of EA. Brainstorming Process Modeling Capture requirement metadata Assumptions Validate Solution Focus Group Conduct Gap analysis Requirements Competitive Analysis Matrix Documentation Force Field Analysis Draft the Solution scope statement Benchmark Studies Decisions Analysis Determine Solution Identify deliverables Describe Project approach Decision Tables/Trees Checklists Requirements Analysis Stakeholders Solution components Define user acceptance criteria Investigate defective solution outputs Observation Organisational Model Decomposition Approach Structured

8 Walkthrough Solution releases Assess business impact of defects Prioritization Techniques Define assumptions Document analysis Scenarios and Use Cases Recommend measures to mitigate impact Process Model Define constraints & dependencies Enterprise Architecture Development MoSCoW Analysis (Must, Should, Could, Won't) Prioritised Requirements Retrospective Validate drivers for Feasibility Analysis Verified Requirements Assess Org. OUT. Estimating techniques Kano Analysis RFI, RFQ, RFP. Identify possible solution approaches Validated Requirements Readiness Feasibility Studies/Analysis Timeboxing/Budgeting (constraints) Determine Transition Root Cause Analysis Gap Analysis Conduct Feasibility option analysis Determine Solution approach Enterprise Voting Assumptions Dependencies Requirements Stakeholder Impact Analysis Interface Identification Constraints Survey Integration Analysis Prepare Feasibility study report Analysis Sequencing External considerations Data migration Traceability Interviewing Key user training UAT.

9 Organisational change Opportunity Analysis (potential benefits) End user training Structured Walkthrough Transition support Problem Analysis (causes of problems) Solution support Business Need Retirement of legacy components Scope Models (envision of deployment). SWOT Analysis Gaps in Capabilities vs Business Need Assessment of proposed solution OUT. Recommended Solution Approach Allocated Requirements Solution Assessment & Validation OUT. Solution Scope Transition Requirements Business Case Solution Performance Assessment Identified Defects Organisational Readiness Assessment Business Analyst Mitigating Actions Domain Subject Matter Expert Approved Requirements Business Users Decisions Made Customers/Suppliers OUT.

10 Modified Requirements Implementation Subject Matter Expert Approved change to Solution/Scope Requirements Manage Solution Scope & Manage Requirements Maintain Requirements Security Personnel List of actions for a BA. Solution components Prepare Requirements Package Communicate Requirements Governing Agencies/bodies Requirements Traceability for Re-Use Maintained-Reusable Requirements Communication format/style Technical Team IN Inputs Requirements Presentation/Package IN. Test Cases/Procedures Define requirements management system Communicate requirements Quality Assurance Define traceability structure Select requir