Techniques vs Tasks (17.5%) Flashcards

1
Q

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.

A

Brainstorming

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

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.

A

Business Cases

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

In Plan Business Analysis Approach:

This technique is Used to review existing organizational assets that might assist in planning the approach.

A

Document Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

In Plan Business Analysis Approach:

This technique is Used to determine how long it may take to perform business analysis activities.

A

Estimation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

In Plan Business Analysis Approach:
This technique is Used to assess how different approaches (and the supported delivery options) affect the value delivered.

A

Financial Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

“In Plan Business Analysis Approach:

This technique is Used to break down complex business analysis processes or approaches into more feasible components.

A

Functional Decomposition

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

In Plan Business Analysis Approach:

This technique is Used to help build the plan with an individual or small group.

A

Interviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

“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.

A

Item Tracking

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

“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.

A

Lessons Learned

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

“In Plan Business Analysis Approach:

This technique is Used to define and document the business analysis approach.

A

Process Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

“In Plan Business Analysis Approach:

This technique is Used to validate the selected business analysis approach with stakeholders.

A

Reviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

“In Plan Business Analysis Approach:

This technique is used to assess risks in order to select the proper business analysis approach.

A

Risk Analysis and Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

“In Plan Business Analysis Approach:

This technique is Used to determine the boundaries of the solution as an input to planning and to estimating.

A

Scope Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

“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.

A

Survey or Questionnaire

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

“In Plan Business Analysis Approach:

This technique is Used to help build the plan in a team setting.

A

Workshops

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

In Plan Stakeholder Engagement:

This technique is Used to produce the stakeholder list and identify stakeholder roles and responsibilities.

A

Brainstorming

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

In Plan Stakeholder Engagement:

This technique is Used to identify stakeholders who were the source of the business rules.

A

Business Rules Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

In Plan Stakeholder Engagement:

This technique is Used to review existing organizational assets that might assist in planning stakeholder engagement.

A

Document Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

In Plan Stakeholder Engagement:
This technique is Used to interact with specific stakeholders to gain more information or knowledge about stakeholder groups.

A

Interviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

In Plan Stakeholder Engagement:
This technique is Used to identify an enterprise’s previous experience (both successes and challenges) with planning stakeholder engagement.

A

Lessons Learned

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

In Plan Stakeholder Engagement:

This technique is Used to identify potential stakeholders and help understand the relationships between them.

A

Mind Mapping

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

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.

A

Organizational Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

In Plan Stakeholder Engagement:

This technique is Used to categorize stakeholders by the systems that support their business processes.

A

Process Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

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.

A

Risk Analysis and Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

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.

A

Scope Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

In Plan Stakeholder Engagement:

This technique is Used to depict the relationship of stakeholders to the solution and to one another.

A

Stakeholder List, Map, or Personas

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

In Plan Stakeholder Engagement:

This technique is Used to identify shared characteristics of a stakeholder group.

A

Survey or Questionnaire

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

In Plan Stakeholder Engagement:

This technique is Used to interact with groups of stakeholders to gain more information about stakeholder groups.

A

Workshops

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

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.

A

Brainstorming

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

In Plan Business Analysis Governance:

This technique is Used to evaluate existing governance processes or templates.

A

Document Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

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.

A

Interviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

In Plan Business Analysis Governance:

This technique is Used to track any issues that arise when planning a governance approach.

A

Item Tracking

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

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.

A

Lessons Learned

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

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.

A

Organizational Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

In Plan Business Analysis Governance:

This technique is Used to document the process or method for governing business analysis.

A

Process Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

In Plan Business Analysis Governance:

This technique is Used to review the proposed governance plan with key stakeholders.

A

Reviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
37
Q

In Plan Business Analysis Governance:
This technique is Used to identify possible decision-making, change control, approval, or prioritization approaches and participants.

A

Survey or Questionnaire

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
38
Q

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.

A

Workshops

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
39
Q

In Plan Business Information Management:

This technique is Used to help stakeholders uncover their business analysis information management needs.

A

Brainstorming

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
40
Q

In Plan Business Information Management:

This technique is Used to help specific stakeholders uncover their business analysis information management needs.

A

Interviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
41
Q

In Plan Business Information Management:

This technique is Used to track issues with current information management processes.

A

Item Tracking

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
42
Q

In Plan Business Information Management:
This technique is Used to create a source of information for analyzing approaches for efficiently managing business analysis information.

A

Lessons Learned

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
43
Q

In Plan Business Information Management:

This technique is Used to identify and categorize the kinds of information that need to be managed.

A

Mind Mapping

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
44
Q

In Plan Business Information Management:

This technique is Used to document the process or method for managing business analysis information.

A

Process Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
45
Q

In Plan Business Information Management:

This technique is Used to ask stakeholders to provide input into defining business analysis information management.

A

Survey or Questionnaire

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
46
Q

In Plan Business Information Management:

This technique is Used to uncover business analysis information management needs in a group setting.

A

Workshops

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
47
Q

In Identify Business Analysis Performance Improvements:

This technique is Used to generate ideas for improvement opportunities.

A

Brainstorming

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
48
Q

In Identify Business Analysis Performance Improvements:

This technique is Used to gather assessments of business analysis performance.

A

Interviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
49
Q

In Identify Business Analysis Performance Improvements:

This technique is Used to track issues that occur during the performance of business analysis for later resolution.

A

Item Tracking

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
50
Q

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.

A

Lessons Learned

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
51
Q

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.

A

Metrics and KPIs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
52
Q

In Identify Business Analysis Performance Improvements:

This technique is Used to witness business analysis performance.

A

Observation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
53
Q

In Identify Business Analysis Performance Improvements:

This technique is Used to analyze existing business analysis processes and identify opportunities for improvement.

A

Process Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
54
Q

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.

A

Process Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
55
Q

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.

A

Reviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
56
Q

In Identify Business Analysis Performance Improvements:
This technique is Used to identify and manage potential conditions or events that may impact business analysis performance.

A

Risk Analysis and Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
57
Q

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.

A

Root Cause Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
58
Q

In Identify Business Analysis Performance Improvements:
This technique is Used to gather feedback from stakeholders about their satisfaction with business analysis activities and deliverables.

A

Survey or Questionnaire

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
59
Q

In Identify Business Analysis Performance Improvements:
This technique is Used to gather assessments of business analysis performance and generate ideas for improvement opportunities.

A

Workshops

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
60
Q

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.

A

Brainstorming

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
61
Q

In Prepare for Elicitation:

This technique is Used to identify information or patterns that require further investigation.

A

Data Mining

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
62
Q

In Prepare for Elicitation:

This technique is Used to identify and assess candidate sources of supporting materials.

A

Document Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
63
Q

In Prepare for Elicitation:

This technique is Used to estimate the time and effort required for the elicitation and the associated cost.

A

Estimation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
64
Q

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.

A

Interviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
65
Q

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.

A

Mind Mapping

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
66
Q

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.

A

Risk Analysis and Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
67
Q

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.

A

Stakeholder List, Map, or Personas

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
68
Q

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.

A

Benchmarking and Market Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
69
Q

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.

A

Brainstorming

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
70
Q

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.

A

Business Rules Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
71
Q

In Conduct Elicitation:

This technique is Used to develop a better understanding of a problem or to stimulate creative solutions.

A

Collaborative Games

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
72
Q

In Conduct Elicitation:

This technique is Used to identify key terms and ideas of importance and define the relationships between them.

A

Concept Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
73
Q

In Conduct Elicitation:

This technique is Used to identify relevant information and patterns.

A

Data Mining

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
74
Q

In Conduct Elicitation:

This technique is Used to understand entity relationships during elicitation.

A

Data Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
75
Q

In Conduct Elicitation:
This technique is Used to review existing systems, contracts, business procedures and policies, standards, and regulations.

A

Document Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
76
Q

In Conduct Elicitation:

This technique is Used to identify and understand ideas and attitudes from a group.

A

Focus Groups

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
77
Q

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.

A

Interface Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
78
Q

In Conduct Elicitation:

This technique is Used to ask questions of stakeholders to uncover needs, identify problems, or discover opportunities.

A

Interviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
79
Q

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.

A

Mind Mapping

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
80
Q

In Conduct Elicitation:
This technique is Used to gain insight about how work is currently done, possibly in different locations and in different circumstances.

A

Observation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
81
Q

In Conduct Elicitation:

This technique is Used to understand current processes and to identify opportunities for improvement in those processes.

A

Process Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
82
Q

In Conduct Elicitation:

This technique is Used to elicit processes with stakeholders during elicitation activities.

A

Process Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
83
Q

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.

A

Prototyping

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
84
Q

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.

A

Survey or Questionnaire

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
85
Q

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.

A

Workshops

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
86
Q

In Confirm Elicitation Results:

This technique is Used to confirm elicitation results against source information or other existing documents.

A

Document Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
87
Q

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.

A

Interviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
88
Q

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.

A

Reviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
89
Q

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.

A

Workshops

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
90
Q

In Communicate Business Analysis Information:

This technique is Used to individually communicate information to stakeholders.

A

Interviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
91
Q

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.

A

Reviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
92
Q

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.

A

Workshops

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
93
Q

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.

A

Collaborative Games

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
94
Q

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.

A

Lessons Learned

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
95
Q

In Manage Stakeholder Collaboration:
This technique is Used to identify and manage risks as they relate to stakeholder involvement, participation, and engagement.

A

Risk Analysis and Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
96
Q

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.

A

Stakeholder List, Map, or Personas

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
97
Q

In Trace Requirements:

This technique is Used to trace business rules to requirements that they support, or rules that support requirements.

A

Business Rules Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
98
Q

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.

A

Functional Decomposition

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
99
Q

In Trace Requirements:
This technique is Used to visually show the future state process, as well as tracing requirements to the future state process.

A

Process Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
100
Q

In Trace Requirements:
This technique is Used to visually depict scope, as well as trace requirements to the area of scope the requirement supports.

A

Scope Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
101
Q

In Maintain Requirements:
This technique is Used to identify business rules that may be similar across the enterprise in order to facilitate reuse.

A

Business Rules Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
102
Q

In Maintain Requirements:
This technique is Used to identify information flow that may be similar across the enterprise in order to facilitate reuse.

A

Data Flow Diagrams

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
103
Q

In Maintain Requirements:
This technique is Used to identify data structure that may be similar across the enterprise in order to facilitate reuse.

A

Data Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
104
Q

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.

A

Document Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
105
Q

In Maintain Requirements:

This technique is Used to identify requirements associated with the components and available for reuse.

A

Functional Decomposition

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
106
Q

In Maintain Requirements:

This technique is Used to identify requirements associated with the processes that may be available for reuse.

A

Process Modelling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
107
Q

In Maintain Requirements:

This technique is Used to identify a solution component that may be utilized by more than one solution.

A

Use Cases and Scenarios

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
108
Q

In Maintain Requirements:

This technique is Used to identify requirements associated with the story that may be available for reuse.

A

User Stories

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
109
Q

In Prioritize Requirements:

This technique is Used to assess requirements against identified business goals and objectives to determine importance.

A

Business Cases

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
110
Q

In Prioritize Requirements:

This technique is Used to identify high-value requirements.

A

Decision Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
111
Q

In Prioritize Requirements:

This technique is Used to produce estimates for the basis of prioritization.

A

Estimation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
112
Q

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.

A

Financial Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
113
Q

In Prioritize Requirements:
This technique is Used to gain an understanding of a single or small group of stakeholders’ basis of prioritization or priorities.

A

Interviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
114
Q

In Prioritize Requirements:

This technique is Used to track issues raised by stakeholders during prioritization.

A

Item Tracking

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
115
Q

In Prioritize Requirements:

This technique is Used to facilitate the process of prioritization.

A

Prioritization

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
116
Q

In Prioritize Requirements:

This technique is Used to understand the risks for the basis of prioritization.

A

Risk Analysis and Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
117
Q

In Prioritize Requirements:
This technique is Used to gain an understanding of stakeholders’ basis of prioritization or priorities in a facilitated group setting.

A

Workshops

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
118
Q

In Assess Requirements Changes:

This technique is Used to justify a proposed change.

A

Business Cases

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
119
Q

In Assess Requirements Changes:

This technique is Used to assess changes to business policies and business rules, and develop revised guidance.

A

Business Rules Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
120
Q

In Assess Requirements Changes:

This technique is Used to facilitate the change assessment process.

A

Decision Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
121
Q

In Assess Requirements Changes:

This technique is Used to determine the size of the change.

A

Estimation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
122
Q

In Assess Requirements Changes:

This technique is Used to estimate the financial consequences of a proposed change.

A

Financial Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
123
Q

In Assess Requirements Changes:

This technique is Used to help business analysts identify interfaces that can be affected by the change.

A

Interface Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
124
Q

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.

A

Interviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
125
Q

In Assess Requirements Changes:

This technique is Used to track any issues or conflicts discovered during impact analysis.

A

Item Tracking

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
126
Q

In Assess Requirements Changes:

This technique is Used to determine the level of risk associated with the change.

A

Risk Analysis and Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
127
Q

In Assess Requirements Changes:

This technique is Used to gain an understanding of the impact or to resolve changes in a group setting.

A

Workshops

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
128
Q

In Approve Requirements:

This technique is Used to resolve issues and gain agreement.

A

Decision Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
129
Q

In Approve Requirements:

This technique is Used to track issues identified during the agreement process.

A

Item Tracking

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
130
Q

In Approve Requirements:

This technique is Used to evaluate requirements.

A

Reviews

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
131
Q

In Approve Requirements:

This technique is Used to facilitate obtaining approval.

A

Workshops

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
132
Q

In Specify and Model Requirements:

This technique is Used to represent the acceptance and evaluation criteria attributes of requirements.

A

Acceptance and Evaluation Criteria

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
133
Q

In Specify and Model Requirements:

This technique is Used to represent features or functions of an enterprise.

A

Business Capability Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
134
Q

In Specify and Model Requirements:

This technique is Used to describe the rationale for requirements.

A

Business Model Canvas

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
135
Q

In Specify and Model Requirements:

This technique is Used to analyze business rules so that they can be specified and modelled alongside requirements.

A

Business Rules Analysis

136
Q

In Specify and Model Requirements:

This technique is Used to define terms and relationships relevant to the change and the enterprise.

A

Concept Modelling

137
Q

In Specify and Model Requirements:
This technique is “Used to record details about the data involved in the change.
Details may include definitions, relationships with other data, origin, format, and usage.”

A

Data Dictionary

138
Q

In Specify and Model Requirements:

This technique is Used to visualize data flow requirements.

A

Data Flow Diagrams

139
Q

In Specify and Model Requirements:

This technique is Used to model requirements to show how data will be used to meet stakeholder information needs.

A

Data Modelling

140
Q

In Specify and Model Requirements:

This technique is Used to represent decisions in a model in order to show the elements of decision making required.

A

Decision Modelling

141
Q

In Specify and Model Requirements:
This technique is Used to model requirements in order to identify constituent parts of an overall complex business function.

A

Functional Decomposition

142
Q

In Specify and Model Requirements:

This technique is Used to record the meaning of relevant business terms while analyzing requirements.

A

Glossary

143
Q

In Specify and Model Requirements:
This technique is Used to model requirements in order to identify and validate inputs and outputs of the solution they are modelling.

A

Interface Analysis

144
Q

In Specify and Model Requirements:

This technique is Used to define and analyze the quality of service attributes.

A

Non-Functional Requirements Analysis

145
Q

In Specify and Model Requirements:
This technique is Used to allow business analysts to model the roles, responsibilities, and communications within an organization.

A

Organizational Modelling

146
Q

In Specify and Model Requirements:
This technique is Used to show the steps or activities that are performed in the organization, or that must be performed to meet the desired change.

A

Process Modelling

147
Q

In Specify and Model Requirements:

This technique is Used to assist the stakeholders in visualizing the appearance and capabilities of a planned solution.

A

Prototyping

148
Q

In Specify and Model Requirements:
This technique is Used to specify and model requirements concerned with the separation of duties among users and external interfaces in utilizing a solution.

A

Roles and Permissions Matrix

149
Q

In Specify and Model Requirements:

This technique is Used to model the root causes of a problem as part of rationale.

A

Root Cause Analysis

150
Q

In Specify and Model Requirements:

This technique is Used to visually show a scope boundary.

A

Scope Modelling

151
Q

In Specify and Model Requirements:
This technique is Used to specify and model requirements to show how processes operate and interact with one another, and in what order.

A

Sequence Diagrams

152
Q

In Specify and Model Requirements:

This technique is Used to identify the stakeholders and their characteristics.

A

Stakeholder List, Map, or Personas

153
Q

In Specify and Model Requirements:
This technique is Used to specify the different states of a part of the solution throughout a life cycle, in terms of the events that occur.

A

State Modelling

154
Q

In Specify and Model Requirements:
This technique is Used to model the desired behaviour of a solution, by showing user interactions with the solution, to achieve a specific goal or accomplish a particular task.

A

Use Cases and Scenarios

155
Q

In Specify and Model Requirements:
This technique is Used to specify requirements as a brief statement about what people do or need to do when using the solution.

A

User Stories

156
Q

In Verify Requirements:
This technique is Used to ensure that requirements are stated clearly enough to devise a set of tests that can prove that the requirements have been met.

A

Acceptance and Evaluation Criteria

157
Q

In Verify Requirements:

This technique is Used to ensure that any problems or issues identified during verification are managed and resolved.

A

Item Tracking

158
Q

In Verify Requirements:

This technique is Used to identify how to evaluate the quality of the requirements.

A

Metrics and KPIs

159
Q

In Verify Requirements:
This technique is Used to inspect requirements documentation to identify requirements that are not of acceptable quality.

A

Reviews

160
Q

In Validate Requirements:

This technique is Used to define the quality metrics that must be met to achieve acceptance by a stakeholder.

A

Acceptance and Evaluation Criteria

161
Q

In Validate Requirements:

This technique is Used to identify previously documented business needs in order to validate requirements.

A

Document Analysis

162
Q

In Validate Requirements:

This technique is Used to define the financial benefits associated with requirements.

A

Financial Analysis

163
Q

In Validate Requirements:

This technique is Used to ensure that any problems or issues identified during validation are managed and resolved.

A

Item Tracking

164
Q

In Validate Requirements:

This technique is Used to select appropriate performance measures for a solution, solution component, or requirement.

A

Metrics and KPIs

165
Q

In Validate Requirements:

This technique is Used to confirm whether or not the stakeholder agrees that their needs are met.

A

Reviews

166
Q

In Validate Requirements:

This technique is Used to identify possible scenarios that would alter the benefit delivered by a requirement.

A

Risk Analysis and Management

167
Q

In Define Requirements Architecture:

This technique is Used to describe the requirements structure as it relates to data.

A

Data Modelling

168
Q

In Define Requirements Architecture:

This technique is Used to break down an organizational unit, product scope, or other elements into its component parts.

A

Functional Decomposition

169
Q

In Define Requirements Architecture:

This technique is Used to define the requirements structure collaboratively.

A

Interviews

170
Q

In Define Requirements Architecture:
This technique is Used to understand the various organizational units, stakeholders, and their relationships which might help define relevant viewpoints.

A

Organizational Modelling

171
Q

In Define Requirements Architecture:

This technique is Used to dentify the elements and boundaries of the requirements architecture.

A

Scope Modelling

172
Q

In Define Requirements Architecture:

This technique is Used to define the requirements structure collaboratively.

A

Workshops

173
Q

In Define Design Options:

This technique is Used to identify and analyze existing solutions and market trends.

A

Benchmarking and Market Analysis

174
Q

In Define Design Options:

This technique is Used to help identify improvement opportunities and design options.

A

Brainstorming

175
Q

In Define Design Options:

This technique is Used to provide information needed to describe design options and design elements.

A

Document Analysis

176
Q

In Define Design Options:

This technique is Used to help identify improvement opportunities and design options.

A

Interviews

177
Q

In Define Design Options:

This technique is Used to help identify improvement opportunities.

A

Lessons Learned

178
Q

In Define Design Options:

This technique is Used to identify and explore possible design options.

A

Mind Mapping

179
Q

In Define Design Options:
This technique is Used to understand the underlying cause of the problems being addressed in the change to propose solutions to address them.

A

Root Cause Analysis

180
Q

In Define Design Options:

This technique is Used to help identify improvement opportunities and design options.

A

Survey or Questionnaire

181
Q

In Define Design Options:
This technique is Used to couple the assessment of a third party solution with an assessment of the vendor to ensure that the solution is viable and all parties will be able to develop and maintain a healthy working relationship.

A

Vendor Assessment

182
Q

In Define Design Options:

This technique is Used to help identify improvement opportunities and design options.

A

Workshops

183
Q

In Analyze Potential Value and Recommend Solution:
This technique is Used to express requirements in the form of acceptance criteria to make them most useful when assessing proposed solutions and determining whether a solution meets the defined business needs.

A

Acceptance and Evaluation Criteria

184
Q

In Analyze Potential Value and Recommend Solution:

This technique is used to sequence the potential value.

A

Backlog Management

185
Q

In Analyze Potential Value and Recommend Solution:

This technique is Used to identify potential benefits of the requirements in a collaborative manner.

A

Brainstorming

186
Q

In Analyze Potential Value and Recommend Solution:

This technique is Used to assess recommendations against business goals and objectives.

A

Business Cases

187
Q

In Analyze Potential Value and Recommend Solution:

This technique is Used as a tool to help understand strategy and initiatives.

A

Business Model Canvas

188
Q

In Analyze Potential Value and Recommend Solution:

This technique is Used to support the assessment and ranking of design options.

A

Decision Analysis

189
Q

In Analyze Potential Value and Recommend Solution:
This technique is Used to forecast the costs and efforts of meeting the requirements as a step towards estimating their value.

A

Estimation

190
Q

In Analyze Potential Value and Recommend Solution:
This technique is Used to evaluate the financial return of different options and choose the best possible return on investment.

A

Financial Analysis

191
Q

In Analyze Potential Value and Recommend Solution:
This technique is Used to get stakeholder input on which design options best meet the requirements, and to evaluate a targeted, small group of stakeholders’ value expectations.

A

Focus Groups

192
Q

In Analyze Potential Value and Recommend Solution:
This technique is Used to get stakeholder input on which design options best meet the requirements, and to evaluate individual stakeholders’ value expectations.

A

Interviews

193
Q

In Analyze Potential Value and Recommend Solution:

This technique is Used to create and evaluate the measurements used in defining value.

A

Metrics and KPIs

194
Q

In Analyze Potential Value and Recommend Solution:

This technique is Used to identify and manage the risks that could affect the potential value of the requirements.

A

Risk Analysis and Management

195
Q

In Analyze Potential Value and Recommend Solution:
This technique is Used to get stakeholder input on which design options best meet the requirements, and to identify stakeholders’ value expectations.

A

Survey or Questionnaire

196
Q

In Analyze Potential Value and Recommend Solution:

This technique is Used to identify areas of strength and weakness that will impact the value of the solutions.

A

SWOT Analysis

197
Q

In Analyze Potential Value and Recommend Solution:
This technique is Used to get stakeholder input on which design options best meet the requirements, and to evaluate stakeholders’ value expectations.

A

Workshops

198
Q

In Analyze Current State:
This technique Provides an understanding of where there are opportunities for improvement in the current state. Specific frameworks that may be useful include 5 Forces analysis, PEST, STEEP, CATWOE, and others.

A

Benchmarking and Market Analysis

199
Q

In Analyze Current State:

This technique identifies gaps and prioritizes them in relation to value and risk.

A

Business Capability Analysis

200
Q

In Analyze Current State:

This technique is Used to capture information regarding the business need and opportunity.

A

Business Cases

201
Q

In Analyze Current State:
This technique Provides an understanding of the value proposition that the enterprise satisfies for its customers, the critical factors in delivering that value, and the resulting cost and revenue streams. Helpful for understanding the context for any change and identifying the problems and opportunities that may have the most significant impact.

A

Business Model Canvas

202
Q

In Analyze Current State:
This technique is Used to capture key terms and concepts in the business domain and define the relationships between them.

A

Concept Modelling

203
Q

In Analyze Current State:

This technique is Used to obtain information on the performance of the enterprise.

A

Data Mining

204
Q

In Analyze Current State:
This technique Analyzes any existing documentation about the current state, including (but not limited to) documents created during the implementation of a solution, training manuals, issue reports, competitor information, supplier agreements, published industry benchmarks, published
technology trends, and performance metrics.

A

Document Analysis

205
Q

In Analyze Current State:
This technique is Used to understand the profitability of the current state and the financial capability to deliver change.

A

Financial Analysis

206
Q

In Analyze Current State:

This technique Soliciets feedback from customers or end users about the current state.

A

Focus Groups

207
Q

In Analyze Current State:

This technique Breaks down complex systems or relationships in the current state.

A

Functional Decomposition

208
Q

In Analyze Current State:
This technique Facilitate dialogue with stakeholders to understand the current state and any needs evolving from the current state.

A

Interviews

209
Q

In Analyze Current State:

This technique Tracks and manages issues discovered about the current state.

A

Item Tracking

210
Q

In Analyze Current State:
This technique Enables the assessment of failures and opportunities for improvement in past initiatives, which may drive a business need for process improvement.

A

Lessons Learned

211
Q

In Analyze Current State:

This technique Assesses performance of the current state of an enterprise.

A

Metrics and KPIs

212
Q

In Analyze Current State:
This technique is Used to explore relevant aspects of the current state and better understand relevant factors affecting the business need.

A

Mind Mapping

213
Q

In Analyze Current State:
This technique May provide opportunities for insights into needs within the current state that have not been identified previously by a stakeholder.

A

Observation

214
Q

In Analyze Current State:
This technique Describes the roles, responsibilities, and reporting structures that exist within the current state organization.

A

Organizational Modelling

215
Q

In Analyze Current State:

This technique Identifies opportunities to improve the current state.

A

Process Analysis

216
Q

In Analyze Current State:

This technique Describes how work occurs within the current solution.

A

Process Modelling

217
Q

In Analyze Current State:

This technique Identifies risks to the current state.

A

Risk Analysis and Management

218
Q

In Analyze Current State:
This technique provides an understanding of the underlying causes of any problems in the current state in order to further clarify a need.

A

Root Cause Analysis

219
Q

In Analyze Current State:

This technique Helps define the boundaries on the current state description.

A

Scope Modelling

220
Q

In Analyze Current State:
This technique Helps to gain an understanding of the current state from a large, varied, or disparate group of stakeholders.

A

Survey or Questionnaire

221
Q

In Analyze Current State:

This technique Evaluates the strengths, weaknesses, opportunities, and threats to the current state enterprise.

A

SWOT Analysis

222
Q

In Analyze Current State:
This technique Determines whether any vendors that are part of the current state are adequately meeting commitments, or if any changes are needed.

A

Vendor Assessment

223
Q

In Analyze Current State:

This technique Engage stakeholders to collaboratively describe the current state and their needs.

A

Workshops

224
Q

In Define Future State:

This technique is Used to identify what may make the future state acceptable and/or how options may be evaluated.

A

Acceptance and Evaluation Criteria

225
Q

In Define Future State:

This technique is Used to set targets for measuring the future state.

A

Balanced Scorecard

226
Q

In Define Future State:

This technique is Used to make decisions about future state business objectives.

A

Benchmarking and Market Analysis

227
Q

In Define Future State:

This technique is Used to collaboratively come up with ideas for the future state.

A

Brainstorming

228
Q

In Define Future State:

This technique is Used to prioritize capability gaps in relation to value and risk.

A

Business Capability Analysis

229
Q

In Define Future State:

This technique is Used to capture the desired outcomes of the change initiative.

A

Business Cases

230
Q

In Define Future State:
This technique is Used to plan strategy for the enterprise by mapping out the needed infrastructure, target customer base, financial cost structure, and revenue streams required to fulfill the value proposition to customers in the desired future state.

A

Business Model Canvas

231
Q

In Define Future State:

This technique is Used to compare the different future state options and understand which is the best choice.

A

Decision Analysis

232
Q

In Define Future State:

This technique is Used to model complex decisions regarding future state options.

A

Decision Modelling

233
Q

In Define Future State:

This technique is Used to estimate the potential financial returns to be delivered by a proposed future state.

A

Financial Analysis

234
Q

In Define Future State:

This technique is Used to break down complex systems within the future state for better understanding.

A

Functional Decomposition

235
Q

In Define Future State:
This technique is Used to talk to stakeholders to understand their desired future state, which needs they want to address, and what desired business objectives they want to meet.

A

Interviews

236
Q

In Define Future State:
This technique is Used to determine which opportunities for improvement will be addressed and how the current state can be improved upon.

A

Lessons Learned

237
Q

In Define Future State:

This technique is Used to determine when the organization has succeeded in achieving the business objectives.

A

Metrics and KPIs

238
Q

In Define Future State:

This technique is Used to develop ideas for the future state and understand relationships between them.

A

Mind Mapping

239
Q

In Define Future State:
This technique is Used to describe the roles, responsibilities, and reporting structures that would exist within the future state organization.

A

Organizational Modelling

240
Q

In Define Future State:

This technique is Used to describe how work would occur in the future state.

A

Process Modelling

241
Q

In Define Future State:

This technique is Used to model future state options and could also help determine potential value.

A

Prototyping

242
Q

In Define Future State:

This technique is Used to define the boundaries of the enterprise in the future state.

A

Scope Modelling

243
Q

In Define Future State:
This technique is Used to understand stakeholders’ desired future state, which needs they want to address, and what desired business objectives they want to meet.

A

Survey or Questionnaire

244
Q

In Define Future State:
This technique is Used to evaluate the strengths, weaknesses, opportunities, and threats that may be exploited or mitigated by the future state.

A

SWOT Analysis

245
Q

In Define Future State:

This technique is Used to assess potential value provided by vendor solution options.

A

Vendor Assessment

246
Q

In Define Future State:

This technique is Used to work with stakeholders to collaboratively describe the future state.

A

Workshops

247
Q

In Assess Risks:

This technique is Used to collaboratively identify potential risks for assessment.

A

Brainstorming

248
Q

In Assess Risks:

This technique is Used to capture risks associated with alternative change strategies.

A

Business Cases

249
Q

In Assess Risks:

This technique is Used to assess problems.

A

Decision Analysis

250
Q

In Assess Risks:

This technique is Used to analyze existing documents for potential risks, constraints, assumptions, and dependencies.

A

Document Analysis

251
Q

In Assess Risks:

This technique is Used to understand the potential effect of risks on the financial value of the solution.

A

Financial Analysis

252
Q

In Assess Risks:

This technique is Used to understand what stakeholders think might be risks and the various factors of those risks.

A

Interviews

253
Q

In Assess Risks:

This technique is Used as a foundation of past issues that might be risks.

A

Lessons Learned

254
Q

In Assess Risks:

This technique is Used to identify and categorize potential risks and understand their relationships.

A

Mind Mapping

255
Q

In Assess Risks:

This technique is Used to identify and manage risks.

A

Risk Analysis and Management

256
Q

In Assess Risks:

This technique is Used to identify and address the underlying problem creating a risk.

A

Root Cause Analysis

257
Q

In Assess Risks:

This technique is Used to understand what stakeholders think might be risks and the various factors of those risks.

A

Survey or Questionnaire

258
Q

In Assess Risks:

This technique is Used to understand what stakeholders think might be risks and the various factors of those risks.

A

Workshops

259
Q

In Define Change Strategy:

This technique is Used to define the metrics that will be used to evaluate the effectiveness of the change strategy.

A

Balanced Scorecard

260
Q

In Define Change Strategy:

This technique is Used to make decisions about which change strategy is appropriate.

A

Benchmarking and Market Analysis

261
Q

In Define Change Strategy:

This technique is Used to collaboratively come up with ideas for change strategies.

A

Brainstorming

262
Q

In Define Change Strategy:

This technique is Used to prioritize capability gaps in relation to value and risk.

A

Business Capability Analysis

263
Q

In Define Change Strategy:
This technique is Used to capture information about the recommended change strategy and other potential strategies that were assessed but not recommended.

A

Business Cases

264
Q

In Define Change Strategy:
This technique is Used to define the changes needed in the current infrastructure, customer base, and financial structure of the organization in order to achieve the potential value.

A

Business Model Canvas

265
Q

In Define Change Strategy:

This technique is Used to compare different change strategies and choose which is most appropriate.

A

Decision Analysis

266
Q

In Define Change Strategy:

This technique is Used to determine timelines for activities within the change strategy.

A

Estimation

267
Q

In Define Change Strategy:
This technique is Used to understand the potential value associated with a change strategy, and evaluate strategies against targets set for return on investments.

A

Financial Analysis

268
Q

In Define Change Strategy:
This technique is Used to bring customers or end users together to solicit their input on the solution and change strategy.

A

Focus Groups

269
Q

In Define Change Strategy:

This technique is Used to break down the components of the solution into parts when developing a change strategy.

A

Functional Decomposition

270
Q

In Define Change Strategy:
This technique is Used to talk to stakeholders in order to fully describe the solution scope and change scope, and to understand their suggestions for a change strategy.

A

Interviews

271
Q

In Define Change Strategy:

This technique is Used to understand what went wrong in past changes in order to improve this change strategy.

A

Lessons Learned

272
Q

In Define Change Strategy:

This technique is Used to develop and explore ideas for change strategies.

A

Mind Mapping

273
Q

In Define Change Strategy:
This technique is Used to describe the roles, responsibilities, and reporting structures that are necessary during the change and are part of the solution scope.

A

Organizational Modelling

274
Q

In Define Change Strategy:

This technique is Used to describe how work would occur in the solution scope or during the change.

A

Process Modelling

275
Q

In Define Change Strategy:

This technique is Used to define the boundaries on the solution scope and change scope descriptions.

A

Scope Modelling

276
Q

In Define Change Strategy:

This technique is Used to make decisions about which change strategy is appropriate.

A

SWOT Analysis

277
Q

In Define Change Strategy:
This technique is Used to determine whether any vendors are part of the change strategy, either to implement the change or to be part of the solution.

A

Vendor Assessment

278
Q

In Define Change Strategy:

This technique is Used in work with stakeholders to collaboratively develop change strategies.

A

Workshops

279
Q

In Measure Solution Performance:

This technique is Used to define business objectives and performance measures for a proposed solution.

A

Business Cases

280
Q

In Measure Solution Performance:

This technique is Used to collect and analyze large amounts of data regarding solution performance.

A

Data Mining

281
Q

In Measure Solution Performance:
This technique is Used to assist stakeholders in deciding on suitable ways to measure solution performance and acceptable levels of performance.

A

Decision Analysis

281
Q

In Measure Solution Performance:

This technique is Used to provide subjective assessments, insights, and impressions of a solution’s performance.

A

Focus Groups

283
Q

In Measure Solution Performance:

This technique is Used to measure solution performance.

A

Metrics and KPIs

284
Q

In Measure Solution Performance:

This technique is Used to define expected characteristics of a solution.

A

Non-Functional Requirements Analysis

285
Q

In Measure Solution Performance:
This technique is Used either to provide feedback on perceptions of solution performance or to reconcile contradictory results.

A

Observation

286
Q

In Measure Solution Performance:

This technique is Used to define measures and their acceptable levels.

A

Benchmarking and Market Analysis

287
Q

In Measure Solution Performance:

This technique is Used to define acceptable solution performance.

A

Acceptance and Evaluation Criteria

288
Q

In Measure Solution Performance:

This technique is Used to simulate a new solution so that performance measures can be determined and collected.

A

Prototyping

289
Q

In Measure Solution Performance:
This technique is Used to gather opinions and attitudes about solution performance. Surveys and questionnaires can be effective when large or disparate groups need to be polled.

A

Survey or Questionnaire

290
Q

In Measure Solution Performance:

This technique is Used to define the expected outcomes of a solution.

A

Use Cases and Scenarios

291
Q

In Measure Solution Performance:
This technique is Used to assess which of the vendor’s performance measures should be included in the solution’s performance assessment.

A

Vendor Assessment

292
Q

In Analyze Performance Measures:
This technique is Used to define acceptable solution performance through acceptance criteria. The degree of variance from these criteria will guide the analysis of that performance.

A

Acceptance and Evaluation Criteria

293
Q

In Analyze Performance Measures:
This technique is Used to observe the results of other organizations employing similar solutions when assessing risks, trends, and variances.

A

Benchmarking and Market Analysis

294
Q

In Analyze Performance Measures:
This technique is Used to collect data regarding performance, trends, common issues, and variances from expected performance levels and understand patterns and meaning in that data.

A

Data Mining

295
Q

In Analyze Performance Measures:
This technique is Used to determine expected value of a solution and its perceived performance from an individual or small group’s perspective.

A

Interviews

296
Q

In Analyze Performance Measures:
This technique is Used to analyze solution performance, especially when judging how well a solution contributes to achieving goals.

A

Metrics and KPIs

297
Q

In Analyze Performance Measures:

This technique is Used to observe a solution in action if the data collected does not provide definitive conclusions.

A

Observation

298
Q

In Analyze Performance Measures:
This technique is Used to identify, analyze, develop plans to modify the risks, and to manage the risks on an ongoing basis.

A

Risk Analysis and Management

299
Q

In Analyze Performance Measures:

This technique is Used to determine the underlying cause of performance variance.

A

Root Cause Analysis

300
Q

In Analyze Performance Measures:

This technique is Used to determine expected value of a solution and its perceived performance.

A

Survey or Questionnaire

301
Q

In Assess Solution Limitations:
This technique is Used to indicate the level at which acceptance criteria are met or anticipated to be met by the solution and to identify any criteria that are not met by the solution.

A

Acceptance and Evaluation Criteria

302
Q

In Assess Solution Limitations:
This technique is Used to assess if other organizations are experiencing the same solution challenges and, if possible, determine how they are addressing it.

A

Benchmarking and Market Analysis

303
Q

In Assess Solution Limitations:
This technique is Used to illustrate the current business rules and the changes required to achieve the potential value of the change.

A

Business Rules Analysis

304
Q

In Assess Solution Limitations:

This technique is Used to identify factors constraining performance of the solution.

A

Data Mining

305
Q

In Assess Solution Limitations:
This technique is Used to illustrate the current business decisions and the changes required to achieve the potential value of the change.

A

Decision Analysis

306
Q

In Assess Solution Limitations:

This technique is Used to help perform problem analysis.

A

Interviews

307
Q

In Assess Solution Limitations:
This technique is Used to record and manage stakeholder issues related to why the solution is not meeting the potential value.

A

Item Tracking

308
Q

In Assess Solution Limitations:
This technique is Used to determine what can be learned from the inception, definition, and construction of the solution to have potentially impacted its ability to deliver value.

A

Lessons Learned

309
Q

In Assess Solution Limitations:
This technique is Used to identify, analyze, and manage risks, as they relate to the solution and its potential limitations, that may impede the realization of potential value.

A

Risk Analysis and Management

310
Q

In Assess Solution Limitations:
This technique is Used to identify and understand the combination of factors and their underlying causes that led to the solution being unable to deliver its potential value.

A

Root Cause Analysis

311
Q

In Assess Solution Limitations:

This technique is Used to help perform problem analysis.

A

Survey or Questionnaire

312
Q

In Assess Enterprise Limitations:

This technique is Used to identify existing solutions and enterprise interactions.

A

Benchmarking and Market Analysis

313
Q

In Assess Enterprise Limitations:

This technique is Used to identify organizational gaps or stakeholder concerns.

A

Brainstorming

314
Q

In Assess Enterprise Limitations:

This technique is Used to identify factors constraining performance of the solution.

A

Data Mining

315
Q

In Assess Enterprise Limitations:
This technique is Used to assist in making an optimal decision under conditions of uncertainty and may be Used in the assessment to make decisions about functional, technical, or procedural gaps.

A

Decision Analysis

316
Q

In Assess Enterprise Limitations:

This technique is Used to gain an understanding of the culture, operations, and structure of the organization.

A

Document Analysis

317
Q

In Assess Enterprise Limitations:

This technique is Used to identify organizational gaps or stakeholder concerns .

A

Interviews

318
Q

In Assess Enterprise Limitations:
This technique is Used to ensure that issues are not neglected or lost and that issues identified by assessment are resolved.

A

Item Tracking

319
Q

In Assess Enterprise Limitations:

This technique is Used to analyze previous initiatives and the enterprise interactions with the solutions.

A

Lessons Learned

320
Q

In Assess Enterprise Limitations:

This technique is Used to witness the enterprise and solution interactions to identify impacts.

A

Observation

321
Q

In Assess Enterprise Limitations:
This technique is Used to ensure the identification of any required changes to the organizational structure that may have to be addressed.

A

Organizational Modelling

322
Q

In Assess Enterprise Limitations:

This technique is Used to identify possible opportunities to improve performance.

A

Process Analysis

323
Q

In Assess Enterprise Limitations:
This technique is Used to illustrate the current business processes and/or changes that must be made in order to achieve the potential value of the solution.

A

Process Modelling

324
Q

In Assess Enterprise Limitations:
This technique is Used to consider risk in the areas of technology (if the selected technological resources provide required functionality), finance (if costs could exceed levels that make the change salvageable), and business (if the organization will be able to make the changes necessary to attain potential value from the solution).

A

Risk Analysis and Management

325
Q

In Assess Enterprise Limitations:
This technique is Used to determine roles and associated permissions for stakeholders, as well as stability of end users.

A

Roles and Permissions Matrix

326
Q

In Assess Enterprise Limitations:

This technique is Used to determine if the underlying cause may be related to enterprise limitations.

A

Root Cause Analysis

327
Q

In Assess Enterprise Limitations:

This technique is Used to identify organizational gaps or stakeholder concerns.

A

Survey or Questionnaire

328
Q

In Assess Enterprise Limitations:
This technique is Used to demonstrate how a change will help the organization maximize strengths and minimize weaknesses, and to assess strategies developed to respond to identified issues.

A

SWOT Analysis

329
Q

In Assess Enterprise Limitations:

This technique is Used to identify organizational gaps or stakeholder concerns.

A

Workshops

330
Q

In Recommend Actions to Increase Solution Value:

This technique is Used to generate predictive estimates of solution performance.

A

Data Mining

331
Q

In Recommend Actions to Increase Solution Value:

This technique is Used to determine the impact of acting on any of the potential value or performance issues.

A

Decision Analysis

332
Q

In Recommend Actions to Increase Solution Value:

This technique is Used to assess the potential costs and benefits of a change.

A

Financial Analysis

333
Q

In Recommend Actions to Increase Solution Value:
This technique is Used to determine if solution performance measures need to be adjusted and Used to identify potential opportunities to improve performance.

A

Focus Groups

334
Q

In Recommend Actions to Increase Solution Value:

This technique is Used to demonstrate potential change within the organization’s structure.

A

Organizational Modelling

335
Q

In Recommend Actions to Increase Solution Value:

This technique is Used to identify relative value of different actions to improve solution performance.

A

Prioritization

336
Q

In Recommend Actions to Increase Solution Value:

This technique is Used to evaluate different outcomes under specific conditions.

A

Risk Analysis and Management

337
Q

In Recommend Actions to Increase Solution Value:
This technique is Used to gather feedback from a wide variety of stakeholders to determine if value has been met or exceeded, if the metrics are still valid or relevant in the current context, and what actions might be taken to improve the solution.

A

Survey or Questionnaire