13522368
Description
Flashcards by Giovanni Basso, updated more than 1 year ago
More
| Question | Answer |
| Define an appropriate method to conduct business analysis activities. | 3. Business Analysis Planning and Monitoring 3.1 Plan Business Analysis Approach |
| Plan an approach for establishing and maintaining effective working relationships with the stakeholders. | 3. Business Analysis Planning and Monitoring 3.2 Plan Stakeholder Engagement |
| Define how decisions are made about requirements and designs. | 3. Business Analysis Planning and Monitoring 3.3 Plan Business Analysis Governance |
| Develop an approach for how business analysis information will be stored and accessed. | 3. Business Analysis Planning and Monitoring 3.4 Plan Business Analysis Information Management |
| Assess business analysis work and plan to improve processes where required. | 3. Business Analysis Planning and Monitoring 3.5 Identify Business Analysis Performance Improvements |
| Understand the scope of the elicitation activity, select appropriate techniques, and plan for (or procure) appropriate supporting materials and resources. | 4. Elicitation and Collaboration 4.1 Prepare for Elicitation |
| Draw out, explore, and identify information relevant to the change. | 4. Elicitation and Collaboration 4.2 Conduct Elicitation |
| Check the information gathered for accuracy and consistency with other information. | 4. Elicitation and Collaboration 4.3 Confirm Elicitation Results |
| Ensure stakeholders have a shared understanding of business analysis information. | 4. Elicitation and Collaboration 4.4 Communicate Business Analysis Information |
| Encourage stakeholders to work towards a common goal. | 4. Elicitation and Collaboration 4.5 Manage Stakeholder Collaboration |
| Ensure that requirements and designs at different levels are aligned to one another, and manage the effects of change to one level on related requirements. | 5. Requirements Life Cycle Management 5.1 Trace Requirements |
| Retain requirement accuracy and consistency throughout and beyond the change during the entire life cycle, and support reuse of requirements in other solutions requirements. | 5. Requirements Life Cycle Management 5.2 Maintain Requirements |
| Rank requirements in the order of relative importance. | 5. Requirements Life Cycle Management 5.3 Prioritize Requirements |
| Evaluate the implications of proposed changes to requirements and designs. | 5. Requirements Life Cycle Management 5.4 Assess Requirements Changes |
| Obtain agreement on and approval of requirements and designs for business analysis work to continue and/or solution construction to proceed. | 5. Requirements Life Cycle Management 5.5 Approve Requirements |
| Understand the reasons why an enterprise needs to change some aspect of how it operates and what would be directly or indirectly affected by the change. | 6. Strategy Analysis 6.1 Analyze Current State |
| Determine the set of necessary conditions to meet the business need. | 6. Strategy Analysis 6.2 Define Future State |
| Understand the undesirable consequences of internal and external forces on the enterprise during a transition to, or once in, the future state. An understanding of the potential impact of those forces can be used to make a recommendation about a course of action. | 6. Strategy Analysis 6.3 Assess Risks |
| Develop and assess alternative approaches to the change, and then select the recommended approach. | 6. Strategy Analysis 6.4 Define Change Strategy |
| Analyze, synthesize, and refine elicitation results into requirements and designs. | 7. Requirements Analysis and Design Definition 7.1 Specify and Model Requirements |
| Ensure that requirements and designs specifications and models meet quality standards and are usable for the purpose they serve. | 7. Requirements Analysis and Design Definition 7.2 Verify Requirements |
| Ensure that all requirements and designs align to the business requirements and support the delivery of needed value. | 7. Requirements Analysis and Design Definition 7.3 Validate Requirements |
| Ensure that the requirements collectively support one another to fully achieve the objectives. | 7. Requirements Analysis and Design Definition 7.4 Define Requirements Architecture |
| Define the solution approach, identify opportunities to improve the business, allocate requirements across solution components, and represent design options that achieve the desired future state. | 7. Requirements Analysis and Design Definition 7.5 Define Design Options |
| Estimate the potential value for each design option and to establish which one is most appropriate to meet the enterprise’s requirements. | 7. Requirements Analysis and Design Definition 7.6 Analyze Potential Value and Recommend Solution |
| Define performance measures and use the data collected to evaluate the effectiveness of a solution in relation to the value it brings. | 8. Solution Evaluation 8.1 Measure Solution Performance |
| Provide insights into the performance of a solution in relation to the value it brings. | 8. Solution Evaluation 8.2 Analyze Performance Measures |
| Determine the factors internal to the solution that restrict the full realization of value. | 8. Solution Evaluation 8.3 Assess Solution Limitations |
| Determine how factors external to the solution are restricting value realization. | 8. Solution Evaluation 8.4 Assess Enterprise Limitations |
| Understand the factors that create differences between potential value and actual value, and recommend a course of action to align them. | 8. Solution Evaluation 8.5 Recommend Actions to Increase Solution Value |
Want to create your own Flashcards for free with GoConqr? Learn more.