All Tasks and Elements Flashcards
Trace Requirements
- Level of Formality
- Relationships
- Derive (stakeholder -> solution req)
- Depends (necessity / effort dependency)
- Satisfy (functional req and solution component)
- Validate (requirement and test case)
- Traceability Repository
Define Design Options
- Define Solution Approaches
- Create, Purchase, or Combination of both
- Identify Improvement Opportunities
- Increase Efficiencies, Improve Access to Information, Identify Additional Capabilities
- Requirements Allocation
- Allocating requirements to solution components and releases supported by assessing trade-offs between alternatives
- Describe Design Options
- Business processes, opperational decisions, organizational structures, software applications
Confirm Elicitation Results
- Compare Elicitation Results Against Source Information
- Compare Elicitation Results Against Other Elicitation Results
Plan Business Analysis Governance
- Decision Making
- Change Control Process
- Plan Prioritization Approach
- Plan for Approvals
Identify Business Analysis Performance Improvements
- Performance Analysis
- Assessment Measures
- Analyze Results
- Recommend Actions for Improvement
Analyze Performance Measures
- Solution Performance versus Desired Value
- Reconciling the degree of solution performance and the degree of solution value
- Risks
- Managing newly discovered risks
- Trends
- Identifying trends over time to reveal anomalies and ensure accurate performance results
- Accuracy
- Testing and analyzing the information collected to ensure accuracy; results are reproducible / repeatable
- Performance Variations
- Identifying differences between expected and actual performance through analysis
Plan Stakeholder Engagement
- Perform Stakeholder Analysis:
- Roles
- Attitudes
- Decision Making Authority
- Level of Power or Influence
- Define Stakeholder Collaboration
- Stakeholder Communication Needs
Approve Requirements
- Understand Stakeholder Roles
- Conflict and Issue Management
- Gain Consensus
- Track and Communicate Approval
Plan Business Analysis Information Management
- Organization of Business Analysis Information
- Level of Abstraction
- Plan Traceability Approach
- Plan for Requirements Reuse
- Storage and Access
- Requirements Attributes
Recommend Actions to Increase Solution Value
- 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
- Recommendations
- The BA’s recommendations to increase solution value dependent upon the reason for lower than expected performance
Specify and Model Requirements
- Model Requirements
- Analyze Requirements
- Represent Requirements and Attributes
- Implement the Appropriate Levels of Abstraction
Analyze Potential Value and Recommend Solution
- Expected Benefits
- Intended positive value of the solution, such as: Benefits, reduces risk, compliance with policies and regulations, improved user experience
- Expected Costs
- Potential negative value of the solution, such as: Timeline, effort, and actual costs
- Determine Value
- Potential value based on the expected benefits and costs considered from stakeholders’ viewpoint
- Assess Design Options and Recommend Solution
- Based on the potential value the solution is expected to deliver
Conduct Elicitation
- 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
- Capture Elicitation Outcomes
Prioritize Requirements
- Basis for Prioritization
- Needs agreement by stakeholders as defined in the BA Planning and Monitoring KA
- Challenges of Prioritization
- Conflicts and tradeoffs
- Continual Prioritization
- Shifting priorities, basis for prioritization
Prepare for Elicitation
- Understand the Sope of Elicitation
- Select Elicitation Techniques
- Set up Logistics
- Secure Supporting Material
- Prepare Stakeholders
Define Requirements Architecture
- Requirements Viewpoints and Views
- A set of conventions that define how requirements will be represented
- Template Architectures
- Standards or templates applied when presenting business analysis information
- Completeness
- Structuring requirements through an architecture ensures that requirements sets are complete
- Relate and Verify Requirements Relationships
- Analyzing requirements against each other to define their relationships
- Business Analysis Information Architecture
- Describes how all of the business analysis information for a change relates
Analyze Current State
- Business Needs
- Organizational Structure and Culture
- Capabilities and Processes
- Technology and Infrastructure
- Policies
- Business Architecture
- Internal Assets
- External Influencers
Assess Requirements Changes
- Assess Formality
- Available information, apparent importance, governance process
- Predictive vs Adaptive approach
- Impact Analysis
- Benefit, Cost, Impact, Schedule and Urgency
- Impact Resolution
- Documented and communicated
Assess Risks
- Unknowns
- Constraints, Assumptions, and Dependencies
- Negative Impact to Value
- Risk Tolerance - 3 Types:
- Risk-Aversion
- Neutrality
- Risk-Seeking
- Recommendation
Define Change Strategy
- Solution Scope
- Gap Analysis
- Enterprise Readiness Assessment
- Change Strategy
- Transition States and Release Planning
Measure Solution Performance
- Define Solution Performance Measures
- Identify the measures to be applied during solution evaluation
- Validate Performance Measures
- Assess the soundness of the selected measures to ensure the assessment of solution performance is useful
- Collect Performance Measures
- Identify the statistical sampling approach to be applied during solution evaluation and then use them
Assess Solution Limitations
- Identify Internal Solution Component Dependencies
- Determining if any solution components have dependencies that limit value realization
- Investigate Solution Problems
- Performing problem analysis to identify the source of problem outputs
- 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
Manage Stakeholder Collaboration
- Gain Agreement on Commitments
- Monitor Stakeholder Engagement
- Collaboration
Maintain Requirements
- Maintain Requirements
- Accuracy
- Relationships
- Maintain Attributes
- Source
- Priority
- Complexity
- Reusing Requirements
- Current or similar initiatives
- Departments or throughout organization
Verify Requirements
- Characteristics of Requirements and Designs Quality
- Atomic, Complete, Consistent, Concise, Feasible, Unambiguous, Testable, Prioritized, and Understandable
- Verification Activities
- Compliance with standards, completeness, missing or inaccurate cross-references, clear terminology
- Checklists
- For quality control when verifying requirements / designs
Plan Business Analysis Approach
- Planning Approach
- Formality and Level of Detail of BA Deliverables
- Business Analysis Activities
- Timing of Business Analysis Work
- Complexity and Risk
- Acceptance
Assess Enterprise Limitations
- Enterprise Culture Assessment
- Performed to learn if stakeholders understand why solution exists, support and accept the change, and agree with its value and benefit
- Stakeholder Impact Analysis
- Provides insights into how the solution affects a partivular stakeholder group (considers functions, locations, and concerns)
- Organizational Structure Changes
- Determines if the formal and / or informal organizational structure impacts value realization
- Operational Assessment
- Determines if an enterprise is able to adapt to or effectively use a solution given the current operational environment
Communicate Business Analysis Information
- Determine Objectives and Format of Communications
- Business Analysis Information Packages
- Communicate Business Analysis Package
- Group/individual collaboration, non-verbal methods
Validate Requirements
- Identify Assumptions
- Factors that are believe to be true but not configured, such as benefits a solution may bring
- Define Measurable Evaluation Criteria
- The criteria for assessing the success of a change after implementation
- Evaluate Alighment with Solution Scope
- Reconciling requirements to the solution in terms of benefit and taking appropriate action (remove or change scope / design)
Define Future State
- Business Goals and Objectives
- Scope of Solution Space
- Constraints
- Organizational Structure and Culture
- Capabilities and Processes
- Technology and Infrastructure
- Policies
- Buisness Architecture
- Internal Assets
- Identify Assumptions
- Potential Value