knowledge area + Purpose + Elements

3. Business Analysis Planning and Monitoring 4. Elicitation and Collaboration

organize and coordinate the efforts of business analysts and stakeholders. business analysts perform to obtain information from stakeholders and
confirm the results. It also describes the communication with stakeholders
once the business analysis information is assembled.
✓ Elicitation is the drawing forth or receiving of information from
stakeholders or other sources.
✓ Collaboration is the act of two or more people working together
towards a common goal.
3.1 Plan Business Analysis Approach define an appropriate method to 4.1 Prepare for Elicitation understand the scope of the elicitation activity,
conduct business analysis activities. select appropriate techniques, and plan for (or procure) appropriate
1. Planning Approach supporting materials and resources.
• Predictive approaches 1. Understand the Scope of Elicitation
• Adaptive approaches 2. Select Elicitation Techniques
2. Formality and Level of Detail of Business Analysis Deliverables 3. Set Up Logistics
3. Business Analysis Activities 4. Secure Supporting Material
4. Timing of Business Analysis Work 5. Prepare Stakeholders
5. Complexity and Risk 4.2 Conduct Elicitation draw out, explore, and identify information
6. Acceptance relevant to the change.
3.2 Plan Stakeholder Engagement plan an approach for establishing and • Collaborative
maintaining effective working relationships with the stakeholders. • Research
1. Perform Stakeholder Analysis • Experiments
2. Define Stakeholder Collaboration 1. Guide Elicitation Activity
3. Stakeholder Communication Needs 2. Capture Elicitation Outcomes
3.3 Plan Business Analysis Governance define how decisions are made 4.3 Confirm Elicitation Results check the information gathered during an
about requirements and designs, including reviews, change control, elicitation session for accuracy and consistency with other information.
approvals, and prioritization. 1. Compare Elicitation Results Against Source Information
1. Decision Making 2. Compare Elicitation Results Against Other Elicitation Results
2. Change Control Process 4.4 Communicate Business Analysis Information ensure stakeholders have
3. Plan Prioritization Approach a shared understanding of business analysis information.
4. Plan for Approvals 1. Determine Objectives and Format of Communication
3.4 Plan Business Analysis Information Management develop an 2. Communicate Business Analysis Package
approach for how business analysis information will be stored and 4.5 Manage Stakeholder Collaboration encourage stakeholders to work
accessed. towards a common goal.
1. Organization of Business Analysis Information 1. Gain Agreement on Commitments
2. Level of Abstraction 2. Monitor Stakeholder Engagement
3. Plan Traceability Approach 3. Collaboration
4. Plan for Requirements Reuse
5. Storage and Access
• who must access the information
• how often they need to access it
• what conditions must be present for access.
6. Requirements Attributes
3.5 Identify Business Analysis Performance Improvements assess
business analysis work and to plan to improve processes where required.
1. Performance Analysis
2. Assessment Measures
3. Analyze Results
4. Recommend Actions for Improvement
• Preventive
• Corrective Raghad Aldossari
• Improvement
 5. Requirements Life Cycle Management 7. Requirements Analysis and Design Definition
manage and maintain requirements and design information from structure and organize requirements discovered during elicitation activities,
inception to retirement. specify and model requirements and designs, validate and verify
information, identify solution options that meet business needs, and
estimate the potential value that could be realized for each solution option.
5.1 Trace Requirements ensure that requirements and designs at 7.1 Specify and Model Requirements analyze, synthesize, and refine
different levels are aligned to one another, and to manage the effects of elicitation results into requirements and designs.
change to one level on related requirements. 1. Model Requirements
1. Level of Formality • Model Formats
2. Relationships • Model Categories
• Derive 2. Analyze Requirements
• Depends 3. Represent Requirements and Attributes
o Necessity 4. Implement the Appropriate Levels of Abstraction
o Effort 7.2 Verify Requirements ensure that requirements and designs
• Satisfy specifications and models meet quality standards and are usable for the
• Validate purpose they serve.
3. Traceability Repository 1. Characteristics of Requirements and Designs Quality
5.2 Maintain Requirements retain requirement accuracy and consistency • Atomic
throughout and beyond the change during the entire requirements life • Complete
cycle, and to support reuse of requirements in other solutions. • Consistent
1. Maintain Requirements • Concise
2. Maintain Attributes • Feasible
3. Reusing Requirements • Unambiguous
5.3 Prioritize Requirements rank requirements in the order of relative • Testable
importance.
• Prioritized
1. Basis for Prioritization
• Understandable
• Benefit
2. Verification Activities
• Penalty
• Comparison Check
• Cost
• Correctness Check
• Risk
• Completeness Check
• Dependencies
• Terminology Check
• Time Sensitivity
• Checking for Compliance
• Stability
• Examples to Clarify
• Regulatory or Policy Compliance
3. Checklists
2. Challenges of Prioritization
7.3 Validate Requirements ensure that all requirements and designs align
3. Continual Prioritization to the business requirements and support the delivery of needed value.
5.4 Assess Requirements Changes evaluate the implications of proposed 1. Identify Assumptions
changes to requirements and designs. 2. Define Measurable Evaluation Criteria
1. Assessment Formality
3. Evaluate Alignment with Solution Scope
• Predictive approaches 7.4 Define Requirements Architecture ensure that the requirements
• Adaptive approaches collectively support one another to fully achieve the objectives.
2. Impact Analysis 1. Requirements Viewpoints and Views
3. Impact Resolution 2. Template Architectures
5.5 Approve Requirements obtain agreement on and approval of 3. Completeness
requirements and designs for business analysis work to continue and/or 4. Relate and Verify Requirements Relationships
solution construction to proceed. • Defined
1. Understand Stakeholder Roles • Necessary
2. Conflict and Issue Management • Correct
3. Gain Consensus • Unambiguous
4. Track and Communicate Approval • Consistent
5. Business Analysis Information Architecture
7.5 Define Design Options 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.
1. Define Solution Approaches
• Create
• Purchase
• Combination of both
2. Identify Improvement Opportunities
• Increase Efficiencies
• Improve Access to Information
• Identify Additional Capabilities
3. Requirements Allocation
4. Describe Design Options
7.6 Analyze Potential Value and Recommend Solution estimate the
potential value for each design option and to establish which one is most
appropriate to meet the enterprise’s requirements.
1. Expected Benefits
2. Expected Costs
3. Determine Value
Raghad Aldossari 4. Assess Design Options and Recommend Solution