Techniques vs Tasks (17.5%) Flashcards
In Plan Business Analysis Approach:
This technique is Used to identify possible business analysis activities, techniques, risks and other relevant items to help build the business analysis approach.
Brainstorming
In Plan Business Analysis Approach:
This technique is used to understand whether elements of the problem or opportunity are especially time-sensitive, high-value, or whether there is any particular uncertainty around elements of the possible need or solution.
Business Cases
In Plan Business Analysis Approach:
This technique is Used to review existing organizational assets that might assist in planning the approach.
Document Analysis
In Plan Business Analysis Approach:
This technique is Used to determine how long it may take to perform business analysis activities.
Estimation
In Plan Business Analysis Approach:
This technique is Used to assess how different approaches (and the supported delivery options) affect the value delivered.
Financial Analysis
“In Plan Business Analysis Approach:
This technique is Used to break down complex business analysis processes or approaches into more feasible components.
Functional Decomposition
In Plan Business Analysis Approach:
This technique is Used to help build the plan with an individual or small group.
Interviews
“In Plan Business Analysis Approach:
This technique is Used to track any issues raised during planning activities with stakeholders. Can also track risk related items raised during discussions when building the approach.
Item Tracking
“In Plan Business Analysis Approach:
This technique is Used to identify an enterprise’s previous experience (both successes and challenges) with planning business analysis approach.
Lessons Learned
“In Plan Business Analysis Approach:
This technique is Used to define and document the business analysis approach.
Process Modelling
“In Plan Business Analysis Approach:
This technique is Used to validate the selected business analysis approach with stakeholders.
Reviews
“In Plan Business Analysis Approach:
This technique is used to assess risks in order to select the proper business analysis approach.
Risk Analysis and Management
“In Plan Business Analysis Approach:
This technique is Used to determine the boundaries of the solution as an input to planning and to estimating.
Scope Modelling
“In Plan Business Analysis Approach:
This technique is Used to identify possible business analysis activities, techniques, risks and other relevant items to help build the business analysis approach.
Survey or Questionnaire
“In Plan Business Analysis Approach:
This technique is Used to help build the plan in a team setting.
Workshops
In Plan Stakeholder Engagement:
This technique is Used to produce the stakeholder list and identify stakeholder roles and responsibilities.
Brainstorming
In Plan Stakeholder Engagement:
This technique is Used to identify stakeholders who were the source of the business rules.
Business Rules Analysis
In Plan Stakeholder Engagement:
This technique is Used to review existing organizational assets that might assist in planning stakeholder engagement.
Document Analysis
In Plan Stakeholder Engagement:
This technique is Used to interact with specific stakeholders to gain more information or knowledge about stakeholder groups.
Interviews
In Plan Stakeholder Engagement:
This technique is Used to identify an enterprise’s previous experience (both successes and challenges) with planning stakeholder engagement.
Lessons Learned
In Plan Stakeholder Engagement:
This technique is Used to identify potential stakeholders and help understand the relationships between them.
Mind Mapping
In Plan Stakeholder Engagement:
This technique is Used to determine if the organizational units or people listed have any unique needs and interests that should be considered.
Organizational Modelling
In Plan Stakeholder Engagement:
This technique is Used to categorize stakeholders by the systems that support their business processes.
Process Modelling
In Plan Stakeholder Engagement:
This technique is Used to identify risks to the initiative resulting from stakeholder attitudes or the inability of key stakeholders to participate in the initiative.
Risk Analysis and Management
In Plan Stakeholder Engagement:
This technique is Used to develop scope models to show stakeholders that fall outside the scope of the solution but still interact with it in some way.
Scope Modelling
In Plan Stakeholder Engagement:
This technique is Used to depict the relationship of stakeholders to the solution and to one another.
Stakeholder List, Map, or Personas
In Plan Stakeholder Engagement:
This technique is Used to identify shared characteristics of a stakeholder group.
Survey or Questionnaire
In Plan Stakeholder Engagement:
This technique is Used to interact with groups of stakeholders to gain more information about stakeholder groups.
Workshops
In Plan Business Analysis Governance:
This technique is Used to generate an initial list of potential stakeholder names who may need approval roles in the defined governance process.
Brainstorming
In Plan Business Analysis Governance:
This technique is Used to evaluate existing governance processes or templates.
Document Analysis
In Plan Business Analysis Governance:
This technique is Used to identify possible decision-making, change control, approval, or prioritization approaches and participants with an individual or small group.
Interviews
In Plan Business Analysis Governance:
This technique is Used to track any issues that arise when planning a governance approach.
Item Tracking
In Plan Business Analysis Governance:
This technique is Used to find if past initiatives have identified valuable experiences with governance that can be leveraged on current or future initiatives.
Lessons Learned
In Plan Business Analysis Governance:
This technique is Used to understand roles and responsibilities within the organizationt to define a governance approach that involves the right stakeholders.
Organizational Modelling
In Plan Business Analysis Governance:
This technique is Used to document the process or method for governing business analysis.
Process Modelling
In Plan Business Analysis Governance:
This technique is Used to review the proposed governance plan with key stakeholders.
Reviews
In Plan Business Analysis Governance:
This technique is Used to identify possible decision-making, change control, approval, or prioritization approaches and participants.
Survey or Questionnaire
In Plan Business Analysis Governance:
This technique is Used to identify possible decision-making, change control, approval, or prioritization approaches and participants within a team setting.
Workshops
In Plan Business Information Management:
This technique is Used to help stakeholders uncover their business analysis information management needs.
Brainstorming
In Plan Business Information Management:
This technique is Used to help specific stakeholders uncover their business analysis information management needs.
Interviews
In Plan Business Information Management:
This technique is Used to track issues with current information management processes.
Item Tracking
In Plan Business Information Management:
This technique is Used to create a source of information for analyzing approaches for efficiently managing business analysis information.
Lessons Learned
In Plan Business Information Management:
This technique is Used to identify and categorize the kinds of information that need to be managed.
Mind Mapping
In Plan Business Information Management:
This technique is Used to document the process or method for managing business analysis information.
Process Modelling
In Plan Business Information Management:
This technique is Used to ask stakeholders to provide input into defining business analysis information management.
Survey or Questionnaire
In Plan Business Information Management:
This technique is Used to uncover business analysis information management needs in a group setting.
Workshops
In Identify Business Analysis Performance Improvements:
This technique is Used to generate ideas for improvement opportunities.
Brainstorming
In Identify Business Analysis Performance Improvements:
This technique is Used to gather assessments of business analysis performance.
Interviews
In Identify Business Analysis Performance Improvements:
This technique is Used to track issues that occur during the performance of business analysis for later resolution.
Item Tracking
In Identify Business Analysis Performance Improvements:
This technique is Used to identify recommended changes to business analysis processes, deliverables, templates, and other organizational process assets that can be incorporated into the current initiative and future work.
Lessons Learned
In Identify Business Analysis Performance Improvements:
This technique is Used to determine what metrics are appropriate for assessing business analysis performance and how they may be tracked.
Metrics and KPIs
In Identify Business Analysis Performance Improvements:
This technique is Used to witness business analysis performance.
Observation
In Identify Business Analysis Performance Improvements:
This technique is Used to analyze existing business analysis processes and identify opportunities for improvement.
Process Analysis
In Identify Business Analysis Performance Improvements:
This technique is Used to define business analysis processes and understand how to improve those processes to reduce problems from hand-offs, improve cycle times, or alter how business analysis work is performed to support improvements in downstream processes.
Process Modelling
In Identify Business Analysis Performance Improvements:
This technique is Used to identify changes to business analysis processes and deliverables that can be incorporated into future work.
Reviews
In Identify Business Analysis Performance Improvements:
This technique is Used to identify and manage potential conditions or events that may impact business analysis performance.
Risk Analysis and Management
In Identify Business Analysis Performance Improvements:
This technique is Used to help identify the underlying cause of failures or difficulties in accomplishing business analysis work.
Root Cause Analysis
In Identify Business Analysis Performance Improvements:
This technique is Used to gather feedback from stakeholders about their satisfaction with business analysis activities and deliverables.
Survey or Questionnaire
In Identify Business Analysis Performance Improvements:
This technique is Used to gather assessments of business analysis performance and generate ideas for improvement opportunities.
Workshops
In Prepare for Elicitation:
This technique is Used to collaboratively identify and reach consensus about which sources of business analysis information should be consulted and which elicitation techniques might be most effective.
Brainstorming
In Prepare for Elicitation:
This technique is Used to identify information or patterns that require further investigation.
Data Mining
In Prepare for Elicitation:
This technique is Used to identify and assess candidate sources of supporting materials.
Document Analysis
In Prepare for Elicitation:
This technique is Used to estimate the time and effort required for the elicitation and the associated cost.
Estimation
In Prepare for Elicitation:
This technique is Used to identify concerns about the planned elicitation, and can be used to seek authority to proceed with specific options.
Interviews
In Prepare for Elicitation:
This technique is Used to collaboratively identify and reach consensus about which sources of business analysis information should be consulted and which elicitation techniques might be most effective.
Mind Mapping
In Prepare for Elicitation:
This technique is Used to identify, assess, and manage conditions or situations that could disrupt the elicitation, or affect the quality and validity of the elicitation results. The plans for the elicitation should be adjusted to avoid, transfer, or mitigate the most serious risks.
Risk Analysis and Management
In Prepare for Elicitation:
This technique is Used to determine who should be consulted while preparing for the elicitation, who should participate in the event, and the appropriate roles for each stakeholder.
Stakeholder List, Map, or Personas
In Conduct Elicitation:
This technique is Used as a source of business analysis information by comparing a specific process, system, product, service, or structure with some external baseline, such as a similar organization or baseline provided by an industry association. Market analysis is used to determine what customers want and what competitors provide.
Benchmarking and Market Analysis
In Conduct Elicitation:
This technique is Used to generate many ideas from a group of stakeholders in a short period, and to organize and prioritize those ideas.
Brainstorming
In Conduct Elicitation:
This technique is Used to identify the rules that govern decisions in an organization and that define, constrain, or enable organizational operations.
Business Rules Analysis
In Conduct Elicitation:
This technique is Used to develop a better understanding of a problem or to stimulate creative solutions.
Collaborative Games
In Conduct Elicitation:
This technique is Used to identify key terms and ideas of importance and define the relationships between them.
Concept Modelling
In Conduct Elicitation:
This technique is Used to identify relevant information and patterns.
Data Mining
In Conduct Elicitation:
This technique is Used to understand entity relationships during elicitation.
Data Modelling
In Conduct Elicitation:
This technique is Used to review existing systems, contracts, business procedures and policies, standards, and regulations.
Document Analysis
In Conduct Elicitation:
This technique is Used to identify and understand ideas and attitudes from a group.
Focus Groups
In Conduct Elicitation:
This technique is Used to understand the interaction, and characteristics of that interaction, between two entities, such as two systems, two organizations, or two people or roles.
Interface Analysis
In Conduct Elicitation:
This technique is Used to ask questions of stakeholders to uncover needs, identify problems, or discover opportunities.
Interviews
In Conduct Elicitation:
This technique is Used to generate many ideas from a group of stakeholders in a short period, and to organize and prioritize those ideas.
Mind Mapping
In Conduct Elicitation:
This technique is Used to gain insight about how work is currently done, possibly in different locations and in different circumstances.
Observation
In Conduct Elicitation:
This technique is Used to understand current processes and to identify opportunities for improvement in those processes.
Process Analysis
In Conduct Elicitation:
This technique is Used to elicit processes with stakeholders during elicitation activities.
Process Modelling
In Conduct Elicitation:
This technique is Used to elicit and validate stakeholders’ needs through an iterative process that creates a model of requirements or designs.
Prototyping
In Conduct Elicitation:
This technique is Used to elicit business analysis information, including information about customers, products, work practices, and attitudes, from a group of people in a structured way and in a relatively short period of time.
Survey or Questionnaire
In Conduct Elicitation:
This technique is Used to elicit business analysis information, including information about customers, products, work practices, and attitudes, from a group of people in a collaborative, facilitated way.
Workshops
In Confirm Elicitation Results:
This technique is Used to confirm elicitation results against source information or other existing documents.
Document Analysis
In Confirm Elicitation Results:
This technique is Used to confirm the business analysis information and to confirm that the integration of that information is correct.
Interviews
In Confirm Elicitation Results:
This technique is Used to confirm a set of elicitation results. It could be informal or formal depending on the risks of not having correct, useful, and relevant information.
Reviews
In Confirm Elicitation Results:
This technique is Used to conduct reviews of the drafted elicitation results using any level of formality. A predetermined agenda, scripts, or scenario tests may be used to walk through the elicitation results, and feedback is requested from the participants and recorded.
Workshops
In Communicate Business Analysis Information:
This technique is Used to individually communicate information to stakeholders.
Interviews
In Communicate Business Analysis Information:
This technique is Used to provide stakeholders with an opportunity to express feedback, request required adjustments, understand required responses and actions, and agree or provide approvals.
Reviews
In Communicate Business Analysis Information:
This technique is Used to provide stakeholders with an opportunity to express feedback and to understand required adjustments, responses, and actions. They are also useful for gaining consensus and providing approvals. Typically used during group collaboration.
Workshops
In Manage Stakeholder Collaboration:
This technique is Used to stimulate teamwork and collaboration by temporarily immersing participants in a safe and fun situation in which they can share their knowledge and experience on a given topic, identify hidden assumptions, and explore that knowledge in ways that may not occur during the course of normal interactions.
Collaborative Games
In Manage Stakeholder Collaboration:
This technique is Used to understand stakeholders’ satisfaction or dissatisfaction, and offer them an opportunity to help improve the working relationships.
Lessons Learned
In Manage Stakeholder Collaboration:
This technique is Used to identify and manage risks as they relate to stakeholder involvement, participation, and engagement.
Risk Analysis and Management
In Manage Stakeholder Collaboration:
This technique is Used to determine who is available to participate in the business analysis work, show the informal relationships between stakeholders, and understand which stakeholders should be consulted about different kinds of business analysis information.
Stakeholder List, Map, or Personas
In Trace Requirements:
This technique is Used to trace business rules to requirements that they support, or rules that support requirements.
Business Rules Analysis
In Trace Requirements:
This technique is Used to break down solution scope into smaller components for allocation, as well as to trace high-level concepts to low-level concepts.
Functional Decomposition
In Trace Requirements:
This technique is Used to visually show the future state process, as well as tracing requirements to the future state process.
Process Modelling
In Trace Requirements:
This technique is Used to visually depict scope, as well as trace requirements to the area of scope the requirement supports.
Scope Modelling
In Maintain Requirements:
This technique is Used to identify business rules that may be similar across the enterprise in order to facilitate reuse.
Business Rules Analysis
In Maintain Requirements:
This technique is Used to identify information flow that may be similar across the enterprise in order to facilitate reuse.
Data Flow Diagrams
In Maintain Requirements:
This technique is Used to identify data structure that may be similar across the enterprise in order to facilitate reuse.
Data Modelling
In Maintain Requirements:
This technique is Used to analyze existing documentation about an enterprise that can serve as the basis for maintaining and reusing requirements.
Document Analysis
In Maintain Requirements:
This technique is Used to identify requirements associated with the components and available for reuse.
Functional Decomposition
In Maintain Requirements:
This technique is Used to identify requirements associated with the processes that may be available for reuse.
Process Modelling
In Maintain Requirements:
This technique is Used to identify a solution component that may be utilized by more than one solution.
Use Cases and Scenarios
In Maintain Requirements:
This technique is Used to identify requirements associated with the story that may be available for reuse.
User Stories
In Prioritize Requirements:
This technique is Used to assess requirements against identified business goals and objectives to determine importance.
Business Cases
In Prioritize Requirements:
This technique is Used to identify high-value requirements.
Decision Analysis
In Prioritize Requirements:
This technique is Used to produce estimates for the basis of prioritization.
Estimation
In Prioritize Requirements:
This technique is Used to assess the financial value of a set of requirements and how the timing of delivery will affect that value.used to assess the financial value of a set of requirements and how the timing of delivery will affect that value.
Financial Analysis
In Prioritize Requirements:
This technique is Used to gain an understanding of a single or small group of stakeholders’ basis of prioritization or priorities.
Interviews
In Prioritize Requirements:
This technique is Used to track issues raised by stakeholders during prioritization.
Item Tracking
In Prioritize Requirements:
This technique is Used to facilitate the process of prioritization.
Prioritization
In Prioritize Requirements:
This technique is Used to understand the risks for the basis of prioritization.
Risk Analysis and Management
In Prioritize Requirements:
This technique is Used to gain an understanding of stakeholders’ basis of prioritization or priorities in a facilitated group setting.
Workshops
In Assess Requirements Changes:
This technique is Used to justify a proposed change.
Business Cases
In Assess Requirements Changes:
This technique is Used to assess changes to business policies and business rules, and develop revised guidance.
Business Rules Analysis
In Assess Requirements Changes:
This technique is Used to facilitate the change assessment process.
Decision Analysis
In Assess Requirements Changes:
This technique is Used to determine the size of the change.
Estimation
In Assess Requirements Changes:
This technique is Used to estimate the financial consequences of a proposed change.
Financial Analysis
In Assess Requirements Changes:
This technique is Used to help business analysts identify interfaces that can be affected by the change.
Interface Analysis
In Assess Requirements Changes:
This technique is Used to gain an understanding of the impact on the organization or its assets from a single or small group of stakeholders.
Interviews
In Assess Requirements Changes:
This technique is Used to track any issues or conflicts discovered during impact analysis.
Item Tracking
In Assess Requirements Changes:
This technique is Used to determine the level of risk associated with the change.
Risk Analysis and Management
In Assess Requirements Changes:
This technique is Used to gain an understanding of the impact or to resolve changes in a group setting.
Workshops
In Approve Requirements:
This technique is Used to resolve issues and gain agreement.
Decision Analysis
In Approve Requirements:
This technique is Used to track issues identified during the agreement process.
Item Tracking
In Approve Requirements:
This technique is Used to evaluate requirements.
Reviews
In Approve Requirements:
This technique is Used to facilitate obtaining approval.
Workshops
In Specify and Model Requirements:
This technique is Used to represent the acceptance and evaluation criteria attributes of requirements.
Acceptance and Evaluation Criteria
In Specify and Model Requirements:
This technique is Used to represent features or functions of an enterprise.
Business Capability Analysis
In Specify and Model Requirements:
This technique is Used to describe the rationale for requirements.
Business Model Canvas