Business Analysis Planning and Monitoring
CBAP/CCBA (BABOK)
Requirements and Designs
• Business analysis can be complex and recursive. Eliciting, analyzing,
validating, and managing requirements have consistently been
recognized as key activities of business analysis.
• Requirements are focused on the need; designs are focused on the
solution. A requirement leads to a design which in turn may drive the
discovery and analysis of more requirements.
• The classification as a requirement or a design may become less
significant as the business analyst's work progresses to a greater
understanding of and eventual fulfillment of the need
Requirements and Design
Requirements and Design Cycle
Classifying Requirements
• Business Requirements are the highest level of requirements and are developed
during Strategy Analysis activities. They define the high-level goals, objectives,
and needs of the organization.
• Stakeholder Requirements define the needs of stakeholders and how they will
interact with a solution. Stakeholder requirements bridge between the business
requirements and the more detailed solution requirements.
• Solution requirements are the most detailed type of requirements and they
describe the solution characteristics that meet the higher-level business and
stakeholder requirements.
• Transition requirements define the solution capabilities required to transition
from the current state to the future state and are no longer needed once the
transition is complete.
Solution Requirements
• Functional Requirements Functional requirements define the
capabilities that a product or solution must provide to its users. They
are a subset of the solution requirements that the business analyst
develops for the project
• Nonfunctional Requirements Nonfunctional requirements describe
quality attributes, design and implementation constraints, and
external interfaces that the product must have. They are a subset of
the solution requirements that the business analyst develops for the
project, and they are typically paired up with the functional
requirements that they constrain in some way.
BACCM
The Core Concept Model in Business Analysis Planning and
Monitoring
Relationship
between
Knowledge Areas
Business Analysis Planning and
Monitoring
The business analyst has five tasks to perform in the Business Analysis
Planning and Monitoring knowledge area
• Defining the business analysis approach
• Planning for stakeholder engagement
• Setting up business analysis governance
• Outlining the business analysis information management process
• Identifying business analysis performance improvements
Business Analysis Planning and
Monitoring
How Are Knowledge Area Tasks Organized?
• Purpose
• Description
• Inputs
• Elements
• Guidelines and Tools
• Techniques
• Stakeholders
• Outputs
Task summary: Plan Business Analysis Approach
Formality and Level of Detail of Business Analysis
Deliverables
Common estimation techniques
Task summary: Plan stakeholder engagement
Stakeholder Map: Onion Diagram
RACI Matrix
Communication Matrix
Task summary: Plan business analysis governance
Business Analysis Governance
• Who has responsibility and authority to make decisions about
business analysis work?
• Who sets priorities for business analysis information?
• Who approves changes to business analysis information?
• Who defines the change management process for requirements and
designs?
Task summary: Plan business analysis information management
Plan business analysis information management
• Define levels of extraction
• Decide Traceability approach
• Plan for requirements reuse
• SLAs
• Quality Standards
• Regulatory Requirements
• Business Rules
• Select Requirements Attributes
Common requirements attributes
Task summary: Identify business analysis performance
improvements
Identify business analysis performance
improvements
• Performance analysis
• Assessment measures
• Analyze results
• Recommend actions for improvement
• KPIs
• Metrics
Business analysis performance measures
Shewhart cycle: BAPM
Images credited to BABOK documentation
