All Tasks and Elements Flashcards

1
Q

Trace Requirements

A
  1. Level of Formality
  2. Relationships
    • Derive (stakeholder -> solution req)
    • Depends (necessity / effort dependency)
    • Satisfy (functional req and solution component)
    • Validate (requirement and test case)
  3. Traceability Repository
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Define Design Options

A
  1. Define Solution Approaches
    • Create, Purchase, or Combination of both
  2. Identify Improvement Opportunities
    • Increase Efficiencies, Improve Access to Information, Identify Additional Capabilities
  3. Requirements Allocation
    • Allocating requirements to solution components and releases supported by assessing trade-offs between alternatives
  4. Describe Design Options
    • Business processes, opperational decisions, organizational structures, software applications
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Confirm Elicitation Results

A
  1. Compare Elicitation Results Against Source Information
  2. Compare Elicitation Results Against Other Elicitation Results
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Plan Business Analysis Governance

A
  1. Decision Making
  2. Change Control Process
  3. Plan Prioritization Approach
  4. Plan for Approvals
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Identify Business Analysis Performance Improvements

A
  1. Performance Analysis
  2. Assessment Measures
  3. Analyze Results
  4. Recommend Actions for Improvement
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Analyze Performance Measures

A
  1. Solution Performance versus Desired Value
    • Reconciling the degree of solution performance and the degree of solution value
  2. Risks
    • Managing newly discovered risks
  3. Trends
    • Identifying trends over time to reveal anomalies and ensure accurate performance results
  4. Accuracy
    • Testing and analyzing the information collected to ensure accuracy; results are reproducible / repeatable
  5. Performance Variations
    • Identifying differences between expected and actual performance through analysis
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Plan Stakeholder Engagement

A
  1. Perform Stakeholder Analysis:
    1. Roles
    2. Attitudes
    3. Decision Making Authority
    4. Level of Power or Influence
  2. Define Stakeholder Collaboration
  3. Stakeholder Communication Needs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Approve Requirements

A
  1. Understand Stakeholder Roles
  2. Conflict and Issue Management
  3. Gain Consensus
  4. Track and Communicate Approval
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Plan Business Analysis Information Management

A
  1. Organization of Business Analysis Information
  2. Level of Abstraction
  3. Plan Traceability Approach
  4. Plan for Requirements Reuse
  5. Storage and Access
  6. Requirements Attributes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Recommend Actions to Increase Solution Value

A
  1. Adjust Solution Performance Measures
    • An analysis effort to identify and define more appropriate measures when the solution is considered acceptable but may not support the fulfillment of business goals and objectives
  2. Recommendations
    • The BA’s recommendations to increase solution value dependent upon the reason for lower than expected performance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Specify and Model Requirements

A
  1. Model Requirements
  2. Analyze Requirements
  3. Represent Requirements and Attributes
  4. Implement the Appropriate Levels of Abstraction
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Analyze Potential Value and Recommend Solution

A
  1. Expected Benefits
    • Intended positive value of the solution, such as: Benefits, reduces risk, compliance with policies and regulations, improved user experience
  2. Expected Costs
    • Potential negative value of the solution, such as: Timeline, effort, and actual costs
  3. Determine Value
    • Potential value based on the expected benefits and costs considered from stakeholders’ viewpoint
  4. Assess Design Options and Recommend Solution
    • Based on the potential value the solution is expected to deliver
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Conduct Elicitation

A
  1. Guide Elicitation Activity, taking into account:
    • Elicitation Goals and Scope of Change
    • Outputs and integration of Activities
    • Who provides and uses the information
    • How the information will be used
  2. Capture Elicitation Outcomes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Prioritize Requirements

A
  1. Basis for Prioritization
    • Needs agreement by stakeholders as defined in the BA Planning and Monitoring KA
  2. Challenges of Prioritization
    • Conflicts and tradeoffs
  3. Continual Prioritization
    • Shifting priorities, basis for prioritization
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Prepare for Elicitation

A
  1. Understand the Sope of Elicitation
  2. Select Elicitation Techniques
  3. Set up Logistics
  4. Secure Supporting Material
  5. Prepare Stakeholders
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Define Requirements Architecture

A
  1. Requirements Viewpoints and Views
    • A set of conventions that define how requirements will be represented
  2. Template Architectures
    • Standards or templates applied when presenting business analysis information
  3. Completeness
    • Structuring requirements through an architecture ensures that requirements sets are complete
  4. Relate and Verify Requirements Relationships
    • Analyzing requirements against each other to define their relationships
  5. Business Analysis Information Architecture
    • Describes how all of the business analysis information for a change relates
17
Q

Analyze Current State

A
  1. Business Needs
  2. Organizational Structure and Culture
  3. Capabilities and Processes
  4. Technology and Infrastructure
  5. Policies
  6. Business Architecture
  7. Internal Assets
  8. External Influencers
18
Q

Assess Requirements Changes

A
  1. Assess Formality
    • Available information, apparent importance, governance process
    • Predictive vs Adaptive approach
  2. Impact Analysis
    • Benefit, Cost, Impact, Schedule and Urgency
  3. Impact Resolution
    • Documented and communicated
19
Q

Assess Risks

A
  1. Unknowns
  2. Constraints, Assumptions, and Dependencies
  3. Negative Impact to Value
  4. Risk Tolerance - 3 Types:
    • Risk-Aversion
    • Neutrality
    • Risk-Seeking
  5. Recommendation
20
Q

Define Change Strategy

A
  1. Solution Scope
  2. Gap Analysis
  3. Enterprise Readiness Assessment
  4. Change Strategy
  5. Transition States and Release Planning
21
Q

Measure Solution Performance

A
  1. Define Solution Performance Measures
    • Identify the measures to be applied during solution evaluation
  2. Validate Performance Measures
    • Assess the soundness of the selected measures to ensure the assessment of solution performance is useful
  3. Collect Performance Measures
    • Identify the statistical sampling approach to be applied during solution evaluation and then use them
22
Q

Assess Solution Limitations

A
  1. Identify Internal Solution Component Dependencies
    • Determining if any solution components have dependencies that limit value realization
  2. Investigate Solution Problems
    • Performing problem analysis to identify the source of problem outputs
  3. Impact Assessment
    • Assessing the impact of any solution limitation on organization’s operation or the ability of the solution to deliver value
    • Categories include: Must resolve, can mitigate, or can accept the problem
23
Q

Manage Stakeholder Collaboration

A
  1. Gain Agreement on Commitments
  2. Monitor Stakeholder Engagement
  3. Collaboration
24
Q

Maintain Requirements

A
  1. Maintain Requirements
    • Accuracy
    • Relationships
  2. Maintain Attributes
    • Source
    • Priority
    • Complexity
  3. Reusing Requirements
    • Current or similar initiatives
    • Departments or throughout organization
25
Q

Verify Requirements

A
  1. Characteristics of Requirements and Designs Quality
    • Atomic, Complete, Consistent, Concise, Feasible, Unambiguous, Testable, Prioritized, and Understandable
  2. Verification Activities
    • Compliance with standards, completeness, missing or inaccurate cross-references, clear terminology
  3. Checklists
    • For quality control when verifying requirements / designs
26
Q

Plan Business Analysis Approach

A
  1. Planning Approach
  2. Formality and Level of Detail of BA Deliverables
  3. Business Analysis Activities
  4. Timing of Business Analysis Work
  5. Complexity and Risk
  6. Acceptance
27
Q

Assess Enterprise Limitations

A
  1. Enterprise Culture Assessment
    • Performed to learn if stakeholders understand why solution exists, support and accept the change, and agree with its value and benefit
  2. Stakeholder Impact Analysis
    • Provides insights into how the solution affects a partivular stakeholder group (considers functions, locations, and concerns)
  3. Organizational Structure Changes
    • Determines if the formal and / or informal organizational structure impacts value realization
  4. Operational Assessment
    • Determines if an enterprise is able to adapt to or effectively use a solution given the current operational environment
28
Q

Communicate Business Analysis Information

A
  1. Determine Objectives and Format of Communications
    • Business Analysis Information Packages
  2. Communicate Business Analysis Package
    • Group/individual collaboration, non-verbal methods
29
Q

Validate Requirements

A
  1. Identify Assumptions
    • Factors that are believe to be true but not configured, such as benefits a solution may bring
  2. Define Measurable Evaluation Criteria
    • The criteria for assessing the success of a change after implementation
  3. Evaluate Alighment with Solution Scope
    • Reconciling requirements to the solution in terms of benefit and taking appropriate action (remove or change scope / design)
30
Q

Define Future State

A
  1. Business Goals and Objectives
  2. Scope of Solution Space
  3. Constraints
  4. Organizational Structure and Culture
  5. Capabilities and Processes
  6. Technology and Infrastructure
  7. Policies
  8. Buisness Architecture
  9. Internal Assets
  10. Identify Assumptions
  11. Potential Value