Test your basic knowledge |

CBAP Business Analysis And Planning

Subjects : certifications, business-skills

Instructions:

Answer 50 questions in 15 minutes.
If you are not ready to take this test, you can study here.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.

1. Revised process and templates for BA deliverables should be analyzed and documented and lessons learned should be recorded.
Specific - Measurable - Achievable - Relevant - Time-bound Objectives must be SMART.
Share - Enhance - Exploit
Business Analysis Process Assets
Requirements Workshop

2. What is the output of the task Document Elicitation Results?
Requirements Workshop
Requirements (Stated) - Stakeholder Concerns
Document Elicitation Results task
Business Rules Analysis - Data Flow Diagrams - Data Modeling - Functional Decomposition - Organizational Modeling - Process Modeling - Scenarios & Use Cases - Scope Modeling - User Stories

3. Gathering information relevant to a decision - breaking down the information relevant to a decision - making comparisons and tradeoffs between similar and dissimilar options and identifying the option that is most desirable.
Benefits - Costs - Risk Assessment - Results Measurement
Decision Analysis
The Business Analysis Communication Plan
Problem Tracking

4. What is the output of the task - Prioritize Requirements?
Requirements (Prioritized)
Historic Analysis
Lessons Learned Process
Description - Raised by - Date Identified - Impact - Priority - Need by Date - Owner - Status - Action Needed to be Resolved - Responsible for Action - Completion Date of Action - Outcome

5. What techniques are used in the task Manage Requirements Traceability?
Define Transitional Requirements
Visual Learner - Auditory Learner - Kinesthetic Learner
Coverage Matrix - Table or spreadsheet used to manage tracing.
Organizational Knowledge

6. Means of eliciting information from many people - sometimes anonymously - in a relatively short period of time
Survey/Questionnaire
Necessity - Effort - Subset - Cover - Value
Verify Requirements
Analytical Thinking & Problem Solving

7. This technique shows how information is input - processed - stored and output from a system in a visual representation.
Solution Knowledge
Systems Thinking
Data Flow Diagrams
Trustworthiness

8. Describes all the possible outcomes of an attempt to accomplish a particular goal that the solution will support.
Cultural Assessment - Operational or Technical Assessment - Stakeholder Impact Analysis
Use Case
Decision Analysis
Functional Decomposition

9. The goal of this task is to create a set of views of the requirements for the new business solution that are comprehensive - complete - consistent and understood from all stakeholder perspectives.
Assess Organization Readiness
Business Analysis Approach - Business Analysis Plan - Organizational Process Assets - Stakeholder Lists - Roles & Responsibilities
Organize Requirements
Organizational Readiness Assessment

10. The goal of this task is validate that the stated requirements expressed by the stakeholder match the stakeholder's understanding of the problem and the stakeholder's needs. Analyst's understanding conforms to the actual desire or intentions of the s
Acceptance & Evaluation Criteria - Decision Analysis - Vendor Assessment
Term and Fact Model
Confirm Elicitation Results
Requirements (Allocated)

11. What are the techniques used in the task Manage Business Analysis Performance?
Interviews - Lessons Learned Process - Metrics and KPIs - Problem Tracking - Process Modeling - Root Cause Analysis - Survey/Questionnaire - Variance Analysis
Goals
Benchmarking
Business Policy

12. The decomposition of activities and tasks creates?
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements
Activity List
Communicated Requirements
Absolute Reference - Author - Complexity - Ownership - Priority - Risks - Source - Stability - Status - Urgency

13. What techniques are used in the task Prepare for Elicitation?
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshop - Survey/Questionnaire
Stakeholder Lists - Roles & Responsibilities
Business Principles & Practices
Acceptance Criteria

14. What is the output of the task Plan Business Analysis Activities?
Assumptions & Constraints - Business Need - Solution Scope - Stakeholder Concerns
Business Analysis Plan
Ethics
Name - Value/Meanings - Description

15. What are the different types of learning styles?
Benchmarking
Assumptions & Constraints - Required Capabilities - Solution Approach
Visual Learner - Auditory Learner - Kinesthetic Learner
Business Analysis Process Assets

16. What are the tasks for the knowledge area - Requirements Management & Communication?
Solution (Constructed) - Requirements (Prioritized and Validated)
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements
Transition Requirements
Delphi Estimation

17. To identify and manage areas of uncertainty that can impact an initiative - solution - or organization.
Risk Analysis
Parametric Estimation
Sequence Diagrams
Requirements Package

18. What is the output of the task - Validate Requirements?
Business Analysis Approach - BA Performance Assessment - Organizational Process Assets - Stakeholder List - Roles & Responsibilities
Business Principals
Budgeting
Requirements (Validated)

19. Combination of expert judgment and history. Individual estimates - sharing the estimates with experts - and having several rounds until consensus is reached. An average of the three estimates is used
Business Analysis Communication Plan - Requirements - Requirements Package
Delphi Estimation
Stakeholder Matrix - Onion Diagram
Decision Analysis

20. What are the techniques used in the task - Assess Organizational Readiness?
Document Analysis
Scenario
Acceptance & Evaluation Criteria - Data Flow Diagrams - Process Models - Focus Groups - Interviews - Survey/Questionnaire - Organizational Modeling - Problem Tracking - Risk Analysis - SWOT Analysis - Force Field Analysis
Problem or Vision Statement

21. What are the inputs to the task - Organize Requirements?
Organizational Process Assets - Requirements (Stated) - Solution Scope
Requirements Management Plan
Problem Solving
Data - Ongoing Work - Organizational Change

22. The people involved - the interactions between them - the external forces affecting their behavior and all other relevant elements and factors.
Acceptance & Evaluation Criteria Definition - Problem Tracking - Structured Walkthrough - Checklists
Implementation Approach
Formal Documentation - Presentation - Model
System

23. What are the techniques used in the task - Validate Solution?
Document Analysis - SWOT Analysis
Acceptance & Evaluation Criteria - Problem Tracking - Root Cause Analysis
Relationship to Time - Relationship to Task Completion - Relationship to Contracts - Relationships to Formal and Informal Authority
Define Transitional Requirements

24. Business value can be delivered through requirements that support _______________ - alignment with internal standards or policies of the organization - or increased satisfaction for stakeholders - even if those things do not have a direct measurable
Requirements Structure
Responsible - Accountable - Consulted - Informed
Formal requirements presentation to stakeholders
Compliance with regulatory or other standards

25. What are the techniques used in the task - Determine Solution Approach?
Plan Business Analysis Approach - Conduct Stakeholder Analysis - Plan Business Analysis Activities - Plan Business Analysis Communication - Plan Requirements Management Process - Manage BA Performance
Document Elicitation Results task
Benchmarking - Brainstorming - Decision Analysis - Estimation - SWOT Analysis - Feasibility Analysis
Fishbone Diagram - Five Whys

26. Models a shallow - and possibly wide view of the system's functionality. It typically does not have any business logic running behind the visualization.
Implementation SME
Enterprise Analysis - often the starting point for initiating a new project
They describe what a solution must be capable of doing to meet the needs of one or more stakeholder groups
Horizontal Prototype

27. A brief description of functionality that users need from a solution to meet a business objective. The goal they are trying to accomplish - and any additional information that may be critical to understanding the scope of the story.
Business Analysis Performance Assessment - Business Analysis Process Assets - Includes a comparison of planned versus actual performance - understanding the root cause of variances from the plan and other information to help understand the level of
User Story
Organizational Readiness Assessment - Requirements (Stated) - Solution (Deployed) - Solution (Designed)
Enterprise Architecture - Solution Scope - Solution (Designed) - Stakeholder Concerns

28. List 3 possible forms of a requirements packages.
Responsible - Accountable - Consulted - Informed
Formal Documentation - Presentation - Model
Business Principles & Practices
Allocate Requirements

29. When a requirement is changed - the BA can easily review all the related requirements and software components in order to understand the impact of the change.
Personal Organization
Benchmarking - Brainstorming - Decision Analysis - Estimation - SWOT Analysis - Feasibility Analysis
Impact Analysis
Validate Solution

30. What are the techniques used in the task Document Elicitation Results?
Functional Decomposition
Interviews
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Problem Tracking - Prototyping - Requirements Workshop - Survey/Questionnaire
Decision Analysis - Focus Groups - Observation - Survey/Questionnaire

31. What is the output of the task - Define Business Case?
Assess Proposed Solution - Allocate Requirements - Assess Organizational Readiness - Define Transition Requirements - Validate Solution - Evaluate Solution Performance
The Sponsor
Observation
Business Case

32. A formal written specification with possible walk-thru - an informal one is possibly verbal or email Communication
Acceptance & Evaluation Criteria - Data Flow Diagrams - Process Models - Focus Groups - Interviews - Survey/Questionnaire - Organizational Modeling - Problem Tracking - Risk Analysis - SWOT Analysis - Force Field Analysis
Formal requirements presentation to stakeholders
Expert Judgment
Influence on the project - organizational - project health and other stakeholders

33. Prioritizes requirements based on the amount of work that the project team is capable of delivering in a set period of time. Approaches include: All-in - All Out - Selective
Define Business Need - Access Capability Gaps - Determine Solution Approach - Define Solution Scope - Define Business Case
Timeboxing
Benefits - Costs - Risk Assessment - Results Measurement
Decision Analysis - Risk Analysis - MoSCoW Analysis - Timeboxing/Budgeting - Voting

34. What are the techniques used in Plan Business Analysis Approach?
Primary stakeholders in the Organize Requirements task
Decision Analysis - Process Modeling - Structured Walkthrough
Interviews - Lessons Learned Process - Metrics and KPIs - Problem Tracking - Process Modeling - Root Cause Analysis - Survey/Questionnaire - Variance Analysis
Formal requirements presentation to stakeholders

35. This knowledge area describes the tasks that are performed in order to ensure that solutions meet the business need and to facilitate successful implementation.
Goals
Document Elicitation Results task
Solution Assessment & Validation
Horizontal Prototype

36. What are the techniques used in the task Conduct Stakeholder Analysis?
Assumptions & Constraints - Required Capabilities - Solution Approach
Requirements (Maintained and Reusable)
Cultural Assessment - Operational or Technical Assessment - Stakeholder Impact Analysis
Acceptance & Evaluation Criteria Definition - Brainstorming - Interviews - Organizational Modeling - Process Modeling - Requirements Workshop - Risk Analysis - Scenarios & Use Cases - User Stories - Scope Modeling - Survey/Questionnaire - RACI Matrix

37. What is the output of the task Prepare for Elicitation?
Business Analysis Communication Plan
Assessment of Proposed Solution
Delphi Estimation
Scheduled Resources - Supporting Materials

38. What are the classifications used to describe requirements
Prioritize Requirements - Organize Requirements - Specify & Model Requirements - Define Assumptions & Constraints - Verify Requirements - Validate Requirements
Acceptance & Evaluation Technique
Business Requirements - Stakeholder Requirements - Solution Requirements - Transition Requirements
Bottom-up Estimation

39. Ability to find information - on-time completion of tasks - efficiency in the completion of work - ability to easily identify all outstanding work and the status of each work item.
Historic Analysis
Assumptions & Constraints - Business Need - Solution Scope - Stakeholder Concerns
Opportunity Cost
Personal Organization

40. The goal of this task is to ensure that all requirements support the delivery of value to the business - fulfill its goal and objectives and meet a stakeholder need.
Validate Requirements
Reliability - Validity - Timeliness
Requirements - Requirements Management Plan
Stakeholder Matrix - Onion Diagram

41. What is the output of the task - Manage Requirements Traceability?
Requirements (Traced)
Risk Analysis
Throw-away Prototype
Tracing Requirements

42. Are used to describe the scope of analysis or the scope of a solution. Serve as a basis for defining and delimiting the scope of business analysis and project work. Allow the definition of a "complete" scope—that is - the boundaries of the scope corr
Timeboxing
Risk - assumptions - constraints - etc.
Scope Modeling
Business Rule

43. Use of parameters - multiplied by the number of hours. (COCOMO II - Function Point Counting - Use Case Points - and Story Points)
Problem Tracking - Risk Analysis
Parametric Estimation
Problem or Vision Statement
Define Business Need - Access Capability Gaps - Determine Solution Approach - Define Solution Scope - Define Business Case

44. Benefits that could have been achieved with an alternative investment rather than this one.
Opportunity Cost
The Business Analysis Communication Plan
Industry Knowledge
Business Analysis Communication Plan

45. What are some of the commonly used requirement attributes?
Monitoring
Absolute Reference - Author - Complexity - Ownership - Priority - Risks - Source - Stability - Status - Urgency
Cohesive - Complete - Consistent - Correct - Feasible - Modifiable - Unambiguous - Testable
Solution Approach

46. What are the techniques used in the task - Prioritize Requirements?
Strengths - Weaknesses
Decision Analysis - Risk Analysis - MoSCoW Analysis - Timeboxing/Budgeting - Voting
Perform tailoring exercises
Vertical Prototype

47. The purpose of _______________ is to ensure that a stakeholder's actual underlying needs are understood - rather than the their stated or superficial desires.
Elicitation
Metrics & KPIs
Problem Solving
Assumptions & Constraints

48. What are the strategies for a positive risk?
Acceptance & Evaluation Criteria Definition - Metrics & KPIs - Prototyping - Risk Analysis - Structured Walkthrough
Business Policy
Focus Group
Share - Enhance - Exploit

49. A means to elicit requirements by studying available documentation on existing and comparable solutions and identifying relevant information. - Not starting from a blank page.- Leveraging existing materials to discover and/or confirm requirements. -
Elimination
Problem or Vision Statement
Document Analysis
Benchmarking - Brainstorming - Decision Analysis - Estimation - SWOT Analysis - Feasibility Analysis

50. What is the output of the task - Communicate Requirements?
Fishbone Diagram - Five Whys
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements
Strengths - Weaknesses
Communicated Requirements