Front | Back |
What is the purpose of Solution Assessment and Validation KA
|
The Solution Assessment and Validation Knowledge Area describes the tasks that are performed in order to ensure that solutions meet the business need and to facilitate their successful implementation
|
What is the purpose of the following task
7.1 Assess Proposed Solution |
To assess proposed solutions in order to determine how closely they meet stakeholder and solution requirements. business analyst determines whether the solution delivers enough business value to justify its implementation
|
What are inputs / outputs for the following task:
7.1 Assess Proposed Solution |
Inputs:
6.4 - Assumptions and Constraints 4.1 / 6.1 - Requirements (Prioritized and Approved) Solution Options Outputs: Assessment of Proposed Solution - If multiple options are available, a recommendation of the best solution should be made. |
What are techniques used for the following task:
7.1 Assess Proposed Solution |
9.1 - Acceptance and Evaluation Criteria Definition
9.8 - Decision Analysis 9.34 - Vendor Assessment |
What are elements for the following task:
7.1 Assess Proposed Solution |
1. Ranking of Solution Options
2. Identification of Additional Potential Capabilities |
What is the purpose of the following task
7.2 Allocate Requirements |
Allocate stakeholder and solution requirements among solution components and releases in order to maximize the possible business value given the options and alternatives generated by the design team.
|
What are inputs / outputs for the following task:
7.2 Allocate Requirements |
Inputs:
4.1 / 6.1 - Requirements (Prioritized and Approved) Solution [Designed] 5.4 Solution Scope Outputs: Requirements (Allocated) |
What are techniques used for the following task:
7.2 Allocate Requirements |
9.1 - Acceptance and Evaluation Criteria Definition
9.4 - Business Rules Analysis 9.8 - Decision Analysis 9.12 - Functional Decomposition 9.21 - Process Modeling 9.26 - Scenarios and Use Cases |
What are elements for the following task:
7.2 Allocate Requirements |
1. Solution Components
Each component implements a subset of the requirements. The allocation of requirements to solution components will be a primary driver of the cost to implement the solution and the benefits delivered by it. (Available Resources | Constraints on the solution | Dependencies between Requirements) 2. Release planning Facilitate the decisions about which requirements will be included in each release/phase/iteration of the project |
What is purpose of the following task:
7.3 Assess Organizational Readiness |
Assess whether the organization is ready to make effective use of a new solution
|
What are inputs / outputs for the following task:
7.3 Assess Organizational Readiness |
Inputs:
Enterprise Architecture Solution [Designed] 5.4 - Solution Scope 3.3 - Stakeholder concerns Outputs: Organizational Readiness Assessment - Describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively. May lead to revisions in solution or project scope. |
What are techniques used for the following task:
7.3 Assess Organizational Readiness |
9.1 - Acceptance and Evaluation Criteria Definition
9.6 - Data Flow Diagrams | 9.21 - Process Models 9.11 - Focus Groups | 9.14 - Interviews | 9.31 - Survey/Questionnaire 9.19 - Organization Modeling 9.20 - Problem Tracking 9.24 - Risk Analysis 9.32 - SWOT Analysis Force Field analysis |
What are elements for the following task:
7.3 Assess Organizational Readiness |
1. Cultural Assessment
2. Operational or Technical Assessment 3. Stakeholder impact analysis |
What is purpose of the following task:
7.4 - Define Transition Requirements |
To define requirements for capabilities needed to transition from an existing solution to a new solution.
|
What are inputs / outputs for the following task:
7.4 - Define Transition Requirements |
Inputs:
7.3 - Organizational Readiness Assessment 3.3 - Requirements [stated] Solution [deployed] Solution [designed] |