Question 1. Glen is carrying out strategy analysis tasks and at the point of deciding which techniques he would use. He came across the following definitions of the likely techniques: 1) to understand the scope of work and break the solution scope into smaller work products or deliverables. 2) It depicts the scope of work required to integrate the new solution into business and technical environments. 3) Identifies appropriate boundaries for the solution scope 4) describes the stakeholders and the goals the system support and as such can also be used to define the solution scope. As an experienced BA, give the correct order of these definitions:
A. User stories, scope modeling, interface analysis, functional decomposition
B. Functional decomposition, Interface analysis, scope modeling, user stories
C. User stories, scope modeling, functional decomposition, interface analysis,
D. Functional decomposition, scope modeling, Interface analysis, user stories
The correct order is:
D. Functional decomposition, scope modeling, interface analysis, user stories
Here’s the reasoning for each definition:
1. Functional decomposition: This technique involves breaking the solution scope into smaller work products or deliverables. It’s a method for understanding the scope of work in detail, which fits the definition of “understanding the scope of work and breaking it into smaller work products.”
2. Scope modeling: This technique identifies appropriate boundaries for the solution scope. It helps define what is included and excluded, aligning with the third definition of “identifying appropriate boundaries.”
3. Interface analysis: This technique focuses on the scope of work required to integrate the new solution into business and technical environments, which matches the second definition of “depicting the scope of work required for integration.”
4. User stories: These describe the stakeholders and the goals the system supports, and are often used to define the solution scope in an agile environment. This aligns with the fourth definition, where stakeholders and goals are emphasized.
Thus, the order “Functional decomposition, scope modeling, interface analysis, user stories” is the correct match.
Question 2. Melissa is the Business analyst assigned to perform the define solution scope task, she however could not complete the task as one of the input was not ready. Which of the following could be what she was waiting for?
A. Business Case
B. Solution Approach
C. Transition requirements
D. Organization Process Assets
Let’s break down the question step by step.
Part 1: Ordering the Techniques Based on Definitions
Glen is trying to decide which techniques to use for strategy analysis, and the question presents four definitions. Let’s match these definitions with commonly known strategy analysis techniques:
1. Definition 1: “to understand the scope of work and break the solution scope into smaller work products or deliverables.”
• This aligns with Work Breakdown Structure (WBS), which is used to break down the project into manageable parts.
2. Definition 2: “It depicts the scope of work required to integrate the new solution into business and technical environments.”
• This matches with the Transition Requirements. Transition requirements define what is needed to integrate a solution into business processes.
3. Definition 3: “Identifies appropriate boundaries for the solution scope.”
• This correlates with Scope Modeling. Scope modeling techniques, such as context diagrams, are used to identify boundaries for a project.
4. Definition 4: “describes the stakeholders and the goals the system supports and as such can also be used to define the solution scope.”
• This sounds like a Stakeholder Map or Stakeholder Analysis, which helps identify stakeholders and their needs to define the scope.
Part 2: The Input Melissa is Waiting For
Melissa is unable to complete the “define solution scope” task because one of the inputs is not ready. Let’s evaluate each option:
• A. Business Case: A business case provides justification for a project and is often an input into defining the solution scope.
• B. Solution Approach: The solution approach describes how the solution will be implemented, and is a critical input into the solution scope definition.
• C. Transition Requirements: These come into play after the solution scope has been defined, as they help integrate the solution. So, it’s unlikely this is what she’s waiting for.
• D. Organization Process Assets: These are helpful guidelines or processes from the organization, but not a direct input required for defining the solution scope.
The most likely input that Melissa is waiting for is B. Solution Approach, since it directly impacts how the solution scope is defined.
Final Answer:
1. Correct order of techniques:
1. Work Breakdown Structure (WBS)
2. Transition Requirements
3. Scope Modeling
4. Stakeholder Map or Stakeholder Analysis
2. Melissa is waiting for: B. Solution Approach.
Question 3. An organization’s business objective should fulfill the following criteria except?
A. It should be related to the organization’s mission, vision and values
B. It should be feasible
C. It should be competitive
D. It should have an observable outcome
The correct answer is C. It should be competitive.
Explanation:
When setting business objectives, the following are key criteria:
1. Related to the organization’s mission, vision, and values (A): Business objectives should align with the core purpose, long-term vision, and guiding principles of the organization. This ensures that the objectives are meaningful and consistent with the organization’s overall direction.
2. Feasibility (B): Objectives must be realistic and achievable. If they are not feasible, it can demoralize employees and waste resources.
3. Observable outcome (D): Business objectives should have measurable outcomes to track progress and determine whether the objective has been achieved. This helps in assessment and accountability.
However, competitiveness (C) is not a required criterion for a business objective. While being competitive is important for the organization’s overall strategy, individual business objectives do not necessarily need to focus on competition. They can be centered around internal improvements, customer satisfaction, or other non-competitive aspects.
Question 4. Business need is not an input to any of the tasks in one of the following knowledge areas.
A. Strategy Analysis
B. Elicitation
C. Requirements Analysis
D. Requirement Management and Communication
The correct answer is B. Elicitation.
Explanation:
Let’s go through each knowledge area to understand why “Business need” is or isn’t an input to their tasks:
1. A. Strategy Analysis:
• Strategy Analysis involves understanding the business need, setting the business goals, and creating strategies to address those needs. Business need is a critical input in this area, as it guides the strategic initiatives and solutions to be developed.
2. B. Elicitation:
• Elicitation is the process of gathering information and requirements from stakeholders. While the business need might be important for understanding the context of the project, it is not directly an input to the elicitation tasks themselves. Elicitation focuses on collecting requirements, which may be influenced by the business need but do not necessarily use it as an explicit input in the tasks.
3. C. Requirements Analysis:
• Requirements analysis involves evaluating and prioritizing the requirements. The business need is a critical input here because requirements are typically assessed in terms of how well they address the business need and objectives.
4. D. Requirement Management and Communication:
• In this area, managing and communicating requirements are key activities. The business need plays an important role in ensuring that requirements are aligned with business objectives and that stakeholders are kept informed of how the requirements meet those needs.
Thus, “B. Elicitation” is the knowledge area where business need is not a direct input to the tasks.
Question 5. Cara the project sponsor reviewed the business case and stated that the business case was inadequate and could not make a decision. What type of information could have been missing in the business case?
A. Information to support prioritizing requirements
B. Information stating how the requirements would be verified
C. Information to support a go/no go decision
D. List and roles of Stakeholders
The correct answer is C. Information to support a go/no go decision.
Explanation:
A business case provides justification for undertaking a project, explaining how it aligns with organizational goals and what the expected benefits are. When a project sponsor, like Cara, reviews a business case, they are typically looking for critical information to help them decide whether to approve or reject the project (a “go/no go” decision). If the business case is deemed “inadequate,” it likely lacks key elements necessary to make this decision, such as:
• Expected return on investment (ROI)
• Costs, risks, and benefits
• Alignment with strategic objectives
• Feasibility of the project
Without this information, the sponsor cannot properly assess whether the project should proceed.
Why the Other Options are Incorrect:
• A. Information to support prioritizing requirements: While this is important during project planning, it’s not typically part of the business case. Prioritization happens after the project is approved.
• B. Information stating how the requirements would be verified: This relates to quality assurance and would be outlined in later project planning stages, not the business case.
• D. List and roles of Stakeholders: While stakeholder identification is important, it’s not critical for the “go/no go” decision. The decision hinges more on whether the project is justified and feasible, which is covered under option C.
Question 6. Linda is performing document analysis, one of the following steps will not be performed
A. Study the material
B. Meet with the SMEs to review/ ask questions
C. Locate and evaluate relevant system and business requirements
D. Tracing requirements
In the context of document analysis, D. Tracing requirements is the step that is not typically performed.
Here’s an explanation of each option:
1. A. Study the material: When conducting document analysis, the first step often involves thoroughly studying the available documents, such as business requirements, technical specifications, or other relevant materials. This helps in understanding the content and context.
2. B. Meet with the SMEs to review/ask questions: Engaging with Subject Matter Experts (SMEs) is a key part of document analysis, as it provides an opportunity to clarify unclear points and verify information.
3. C. Locate and evaluate relevant system and business requirements: Identifying and reviewing relevant requirements is crucial during document analysis to ensure all necessary information is considered.
4. D. Tracing requirements: Tracing requirements refers to tracking each requirement to ensure it is addressed throughout the project lifecycle (e.g., in design, development, and testing). While important in requirements management, this step typically occurs after the document analysis phase, as it relates more to the implementation and validation of requirements rather than analyzing documents themselves.
Thus, D. Tracing requirements is the correct answer, as it is not part of the initial document analysis process.
Question 7. When performing Initial risk assessment the following except one is addressed.
A. Will the stakeholders on the project work efficiently
B. Can an organizational change be done effectively to realize the solution benefits
C. Will the new technology scale up to the performance required
D. Will there be a budget overrun.
The correct answer is A. Will the stakeholders on the project work efficiently.
Explanation:
Initial risk assessment in project management primarily focuses on identifying major risks that can affect the project’s success in terms of scope, schedule, budget, and performance. The other options (B, C, and D) align with typical concerns during an initial risk assessment, whereas option A does not directly fit.
• B. Can an organizational change be done effectively to realize the solution benefits: This addresses risks associated with organizational changes, a typical concern when implementing new systems or processes.
• C. Will the new technology scale up to the performance required: Assessing whether technology can meet performance requirements is a common technical risk that is considered during the initial stages.
• D. Will there be a budget overrun: Budget risks are one of the main aspects addressed during risk assessments.
On the other hand:
• A. Will the stakeholders on the project work efficiently: While stakeholder efficiency is important for project success, it’s more of a management and operational concern than a direct initial risk typically assessed in formal project risk evaluations. It would be indirectly related to risk, but it is not the primary focus at this stage.
Question 8. Required capabilities is an input into tasks in the following knowledge areas
A. Strategic Analysis and Business Analysis Planning and Monitoring
B. Business Analysis Planning & Monitoring and Requirements Analysis
C. Requirements Analysis and Strategy Analysis
D. Solution Assessment & Validation and Business Analysis Planning & Monitoring
The correct answer is D. Solution Assessment & Validation and Business Analysis Planning & Monitoring.
Explanation:
The concept of “required capabilities” refers to the abilities that a solution must possess to meet business needs. These required capabilities are used to guide decisions on assessing potential solutions and ensuring the chosen solution meets the identified needs. Let’s break down the answer choices:
• A. Strategic Analysis and Business Analysis Planning and Monitoring: Strategic analysis involves high-level business goals and vision, while Business Analysis Planning & Monitoring is about planning and managing the business analysis approach. “Required capabilities” are not typically inputs in these areas, as they focus more on planning than solution assessment.
• B. Business Analysis Planning & Monitoring and Requirements Analysis: While planning involves defining approaches and Requirements Analysis involves detailing requirements, neither directly involves assessing a solution based on required capabilities.
• C. Requirements Analysis and Strategy Analysis: Strategy analysis is concerned with defining the business need and high-level strategies, while Requirements Analysis is about specifying and modeling requirements. Both are more focused on understanding and documenting requirements rather than evaluating the required capabilities of a solution.
• D. Solution Assessment & Validation and Business Analysis Planning & Monitoring: This is the correct choice because:
• Solution Assessment & Validation involves assessing and validating the solution to ensure it meets the required capabilities identified earlier in the process.
• Business Analysis Planning & Monitoring might use required capabilities when monitoring and ensuring that the business analysis process is aligned with delivering the needed capabilities in the solution.
Hence, required capabilities are relevant as inputs during Solution Assessment & Validation and in the planning activities for business analysis.
Question 9. Where would the sponsor go to find the information necessary to make a go/no go decision for a proposed project?
A. Business case
B. Solution scope
C. Business need
D. Solution approach
The correct answer is A. Business case.
Explanation:
A business case provides a comprehensive overview of the project, including the benefits, costs, risks, and justifications for proceeding with or rejecting the project. It is typically the document that sponsors and decision-makers use to assess whether the proposed project should move forward (a “go”) or be stopped (a “no go”). The business case will contain the necessary financial and strategic data that supports the decision-making process.
Here’s why the other options are less suitable:
• B. Solution scope: This defines the boundaries and deliverables of the solution but does not usually include the comprehensive justification, financial analysis, or business impacts needed for a go/no go decision.
• C. Business need: This highlights the problem or opportunity that the project seeks to address but does not provide enough information for a complete go/no go decision, such as cost-benefit analysis or risks.
• D. Solution approach: This outlines how the solution will be implemented but, like the solution scope, it doesn’t include the detailed financial and risk information required for the overall decision-making process.
Therefore, the business case is the document that would provide all the necessary information to make the go/no go decision.
Question 10. All of the following except ———— is not an input to define business case
A. Business Need
B. Solution Approach
C. Solution Scope
D. Stakeholder Concerns
The correct answer is D. Stakeholder Concerns.
Explanation:
A business case outlines the rationale for starting a project and includes key information to justify the investment and expected benefits. The typical inputs to define a business case are:
1. A. Business Need: This is the fundamental reason for the project—what problem needs to be solved or opportunity needs to be seized. It is a crucial input.
2. B. Solution Approach: This describes potential ways or strategies to address the business need. It is essential to outline the direction the project will take.
3. C. Solution Scope: This defines the boundaries of the proposed solution. It specifies what will and won’t be included in the project, making it another important input.
However, Stakeholder Concerns (Option D) are typically considered during other phases of project planning and stakeholder management but are not typically seen as direct inputs when defining the business case. While understanding stakeholders is important, their specific concerns are more relevant to risk management and communications planning later in the project lifecycle.
Thus, D is the exception.