babok Flashcards
Business Analysis Planning and Monitoring
3.1 Plan Business Analysis Approach
3.2 Plan Stakeholder Engagement
3.3 Plan Business Analysis Governance
3.4 Plan Business Analysis Information Management
3.5 Identify Business Analysis Performance Improvements
Elicitation and Collaboration
4.1 Prepare for Elicitation
4.2 Conduct Elicitation
4.3 Confirm Elicitation Results
4.4 Communicate Business Analysis Information
4.5 Manage Stakeholder Collaboration
Requirements Life Cycle Management
5.1 Trace Requirements 79
5.2 Maintain Requirements 83
5.3 Prioritize Requirements 86
5.4 Assess Requirements Changes 91
5.5 Approve Requirements 95
Strategy Analysis
6.1 Analyze Current State 103
6.2 Define Future State 110
6.3 Assess Risks 120
6.4 Define Change Strategy 124
Requirements Analysis and Design Definition
7.1 Specify and Model Requirements 136
7.2 Verify Requirements 141
7.3 Validate Requirements 144
7.4 Define Requirements Architecture 148
7.5 Define Design Options 152
7.6 Analyze Potential Value and Recommend Solution 157
Solution Evaluation
8.1 Measure Solution Performance 166
8.2 Analyze Performance Measures 170
8.3 Assess Solution Limitations 173
8.4 Assess Enterprise Limitations 177
8.5 Recommend Actions to Increase Solution Value 182
Core Concept
Change
Need
Solution
Stakeholder
Value
Context
classification schema describes requirements:
Business requirements:
Stakeholder requirements:
Solution requirements:
* functional requirements:
* non-functional requirements or quality of service requirements:
* Transition requirements:
Specify and Model Requirements
analyze, synthesize, and refine elicitation results into requirements and designs.
Model Requirements
Matrices: complex but uniform structure, which can be broken down into elements that apply to every entry in the table. Matrices may be used for data dictionaries, requirements traceability, or for gap analysis. Matrices are also used for prioritizing
requirements and recording other requirements attributes and metadata.
Diagrams: a diagram is a visual, often pictorial, representation of arequirement or set of requirements. A diagram is especially useful to depict complexity in a way that would be difficult to do with words. Diagrams can also be used to define boundaries for business domains, to categorize and create hierarchies of items, and to show components of objects such as data and their relationships.
Using one or more of the model formats, business analysts determine specific categories and specific models within categories to be used. Model categories can include:
People and Roles
rationale
activity flow
capability
data and information
element of Specify and Model Requirements
Model Requirements
Analyze Requirements
Represent Requirements and Attributes
Implement the Appropriate Levels of Abstraction
Business analysis information is decomposed into components to further examine for:
- anything that must change to meet the business need,
- anything that should stay the same to meet the business need,
- missing components,
- unnecessary components, and
- any constraints or assumptions that impact the components.
Guidelines and Tools verify re quirement
Modelling Notations/Standards:
Modelling Tools
Requirements Architecture
Requirements Life Cycle Management Tools
Solution Scope:
Verify Requirements p&d
ensure that requirements and designs specifications and models meet quality standards and are usable for the purpose they serve.
check by the business analyst and key stakeholders
Verify Requirements input
Requirements (specified and modelled)
Characteristics of Requirements and Designs Quality
Atomic
complete
concise
understandable
consistent
unambiguous
prioritized
testable
Verification Activities
- checking for compliance with organizational performance standards for business analysis, such as using the right tools and methods,
- checking for correct use of modelling notation, templates, or forms,
- checking for completeness within each model,
- comparing each model against other relevant models, checking for elements that are mentioned in one model but are missing in other models,
and verifying that the elements are referenced consistently, - ensuring the terminology used in expressing the requirement is understandable to stakeholders and consistent with the use of those terms
within the organization, and - adding examples where appropriate for clarification
Verify requirement element
Characteristics of Requirements and Designs Quality
Verification Activities
Checklists
Guidelines and Tools Verify requirement
Requirements Life Cycle Management Tools:
Validate Requirements
ensure that all requirements and designs align to the business requirements and support the delivery of needed value
ensure that stakeholder,
solution, and transition requirements align to the business requirements and that the designs satisfy the requirements.
In many cases, stakeholders have different,
conflicting needs and expectations that may be exposed through the validation process.
Validate Requirements input
Requirements (specified and modelled):
Validation activities may begin before requirements are completely verified. However, validation activities cannot be completed before requirements are completely verified
Validate Requirements element
Identify Assumptions
Define Measurable Evaluation Criteria
Evaluate Alignment with Solution Scope
Guidelines and Tools Validate Requirements
Business Objectives:
Future State Description
Potential Value:
Solution Scope:
Define Requirements Architecture p&d
ensure that the requirements collectively support one another to fully achieve the objectives
* understand which models are appropriate for the domain, solution scope, and audience,
* organize requirements into structures relevant to different stakeholders,
* illustrate how requirements and models interact with and relate to each other, and show how the parts fit together into a meaningful whole,
* ensure the requirements work together to achieve the overall objectives,
* make trade-off decisions about requirements while considering the overall objectives.
work in harmony with one another
Define Requirements Architecture input
Information Management Approach:
Requirements (any state):
Solution Scope
Define Requirements Architecture element
Requirements Viewpoints and Views
Template Architectures
Completeness
Relate and Verify Requirements Relationships
Business Analysis Information Architecture
Requirements Viewpoints and Views
Viewpoints provide templates for addressing the concerns of particular stakeholder groups
* model types used for requirements,
* attributes that are included and consistently used in different models,
* model notations that are used, and
* analytical approaches used to identify and maintain relevant relationships among models.
viewpoints tell business analysts what information they should provide for each stakeholder group to address their concerns, while views describe the actual requirements and designs that are produced
Business analysts examine each relationship to ensure that the relationships
satisfy the following quality criteria:
- Defined: there is a relationship and the type of the relationship is described.
- Necessary: the relationship is necessary for understanding the requirements holistically.
- Correct: the elements do have the relationship described.
- Unambiguous: there are no relationships that link elements in two different and conflicting ways.
- Consistent: relationships are described in the same way, using the same set of standard descriptions as defined in the viewpoints.
Define Design Options p&d
define the solution approach, identify opportunities to improve the business, allocate requirements across solution components, and represent design options that achieve the desired future state.
Define Design Options input
Change Strategy:
Requirements (validated, prioritized):
Requirements Architecture:
Define Design Options elements
Define Solution Approaches
Identify Improvement Opportunities
Requirements Allocation
Describe Design Options
Solution approaches include
Create
purchase
Combination of both
Some common examples of opportunities include:
Increase Efficiencies:
Improve Access to Information
Identify Additional Capabilities:
Define Design Options Guidelines and Tools
Existing Solutions:
Future State Description:
Requirements (traced):
Solution Scope:
Analyze Potential Value and Recommend Solution p&d
estimate the potential value for each design option and to establish which one is most appropriate to meet the enterprise’s requirements.
Analyze Potential Value and Recommend Solution input
Potential Value:
Design Options:
Analyze Potential Value and Recommend Solution element
Expected Benefits
Expected Costs
Determine Value
Assess Design Options and Recommend Solution
Assess Design Options and Recommend Solution
Available Resources:
Constraints on the Solution:
Dependencies between Requirements:
Analyze Potential Value and Recommend Solution g&t
Business Objectives:
Current State Description
Future State Description
Risk Analysis Results
Solution Scope:
Solution Evaluation tasks can be performed on solution components in varying
stages of development:
Prototypes or Proofs of Concept:
Pilot or Beta releases
Operational releases:
Measure Solution Performance p&d
define performance measures
and use the data collected to evaluate the effectiveness of a solution
Measure Solution Performance input
Business Objectives:
Implemented Solution (external)
Define Solution Performance Measures
Quantitative Measures:
Qualitative Measures:
Measure Solution Performance element
Define Solution Performance Measures
Validate Performance Measures
Collect Performance Measures
When collecting performance measures, business analysts consider:
Volume or Sample Size
Frequency and Timing:
Currency:
Measure Solution Performance g&t
Change Strategy:
Future State Description:
Requirements (validated)
Solution Scope
Analyze Performance Measures element
Solution Performance versus Desired Value
Risks
Trends
Accuracy
Performance Variances
Analyze Performance Measures
input
Potential Value
Solution Performance Measures
Analyze Performance Measures g&t
- Change Strategy:
- Future State Description:
- Risk Analysis Results:
- Solution Scope:
Assess Solution Limitations input
Implemented Solution (external):
Solution Performance Analysis:
Assess Solution Limitations element
Identify Internal Solution Component Dependencies
Investigate Solution Problems
Impact Assessment
Assess Solution Limitations g&t
Change Strategy
Risks Analysis Results
Solution Scope
Assess Enterprise Limitations p&d
determine how factors external
to the solution are restricting value realization: culture, operations, technical components,
stakeholder interests, or reporting structures.
Assess Enterprise Limitations input
Current State Description:
Implemented Solution (external)
Solution Performance Analysis
Assess Enterprise Limitations element
Enterprise Culture Assessment
Stakeholder Impact Analysis
Organizational Structure Changes
Operational Assessment
Guidelines and Tools Assess Enterprise Limitations
Business Objectives
Change Strategy
Future State Descriptions
Risk Analysis Results
Solution Scope
Recommend Actions to Increase Solution Value p&d
understand the factors that create differences between potential value and actual value, and to recommend a course of action to align them.
Recommend Actions to Increase Solution Value input
Enterprise Limitation
Solution Limitation
Some common examples of recommendations that a business analyst may make
include:
Do Nothing:
Organizational Change
Reduce Complexity of Interfaces:
Eliminate Redundancy:
Avoid Waste:
Identify Additional Capabilities
Retire the Solution
ongoing cost versus initial investment:
opportunity cost
necessity:
sunk cost:
Guidelines and Tools Recommend Actions to Increase Solution Value
Business Objectives:
Current State Description
Solution Scope:
Plan Business Analysis Approach p&d
define an appropriate method to conduct business analysis activities
* align to the overall goals of the change,
* coordinate the business analysis tasks with the activities and deliverables of the overall change,
* include tasks to manage any risks that could reduce the quality of business analysis deliverables or impede task efficiency, and
* leverage approaches and select techniques and tools that have historically worked well.
Plan Business Analysis Approach input
Needs
Plan Business Analysis Approach element
Planning Approach
Formality and Level of Detail of Business Analysis Deliverables
Business Analysis Activities
Timing of Business Analysis Work
Complexity and Risk
Acceptance
Plan Business Analysis Approach g&t
Business Analysis Performance Assessment
Business Policies
Expert Judgment:
Methodologies and Frameworks:
Stakeholder Engagement Approach:
Plan Stakeholder Engagement p&d
plan an approach for establishing and maintaining effective working relationships with the stakeholders
Plan Stakeholder Engagement input
Needs
Business Analysis Approach:
Plan Stakeholder Engagement element
- Perform Stakeholder Analysis
Roles
Attitudes
Decision Making Authority
Level of Power or Influence - Define Stakeholder Collaboration
- Stakeholder Communication Needs
Guidelines and Tools Plan Stakeholder Engagement
Business Analysis Performance Assessment
Change Strategy:
Current State Description:
Plan Stakeholder Engagement stakeholder
Customers: ex
Supplier: ex
Domain Subject Matter Expert:
End User: in
Project Manager:
Regulator
Sponsor:
Plan Business Analysis Governance p&d
define how decisions are made about requirements and designs, including reviews, change control, approvals, and prioritization.
Plan Business Analysis Governance input
Business Analysis Approach
Stakeholder Engagement Approach:
Plan Business Analysis Governance
element
Decision Making
Change Control Process
Plan Prioritization Approach
Plan for Approvals
Plan Business Analysis Governance g&t
Business Analysis Performance Assessment
Business Policies
Current State Description:
Legal/Regulatory Information
Plan Business Analysis Information Management p&d
develop an approach for how business analysis information will be stored and accessed.
Plan Business Analysis Information Management input
Business Analysis Approach:
Governance Approach
Stakeholder Engagement Approach
Plan Business Analysis Information Management element
Organization of Business Analysis Information
Level of Abstraction
Plan Traceability Approach
Plan for Requirements Reuse
Storage and Access
Requirements Attributes
Some commonly used requirements attributes include:
Absolute reference:
Author
Complexity:
Ownership
Priority
Risks
Source
Stability
Status
Urgency
Plan Business Analysis Information Management g&t
Plan Business Analysis Information Management
Information Management Tools:
Business Policies:
Legal/Regulatory Information:
Plan Business Analysis Information Management stakeholder
Domain Subject Matter Expert:
Regulator:
Sponsor:
Identify Business Analysis Performance Improvements p&d
assess business analysis work and to plan to improve processes where required.
Inputs Identify Business Analysis Performance Improvements
Business Analysis Approach:
Business Analysis Approach:
Identify Business Analysis Performance Improvements element
Performance Analysis
Assessment Measures
Analyze Results
recommend Actions for Improvement
Some possible Assessment measures are:
Accuracy and Completeness
Knowledge
Effectiveness:
Organizational Support:
Significance
Strategic:
Timeliness:
Once the analysis of performance results is complete, the business analyst engages the appropriate stakeholders to identify the following actions:
Preventive:
Preventive:
Preventive:
Guidelines and Tools
