PMP Flashcards
In a short, 3-month project to implement a commercial-off-the-shelf (COTS) system, the business analyst determined that detailed software requirements specification document was not necessary and planned instead upon use cases for the analysis technique and documentation format. This is an example of which of the following?
A. Appropriate use of risk mitigation
B. Determining appropriate requirements analysis and documentation activities
C. An assumption that could become a risk
D. A common mistake leading to prescriptive requirements
*The business analyst determines the best technique to be used on the project regarding requirements process.
Determining appropriate requirements analysis and documentation activities
The analyst was able to determine the technique to be used in this project
The Business analyst determines the best technique to be used on the project regarding the requirements process. There is nothing to hint that an assumption or a risk is a consideration in the decision. There is nothing to hint that risk is a consideration in the decision. There are no prescriptive requirements. Business Analysis for Practitioners, section 4.11.8: Documenting with Use Cases, page 130
Your sponsor, Sami, has requested a group meeting to review submitted requirements documentation to ensure that the requirements as stated are valid. What type of meeting would be most appropriate?
A. A group focused requirements session
B. A requirements walkthrough session
C. A nominal group requirements session
D. A Delphi-based requirements session
Key fact: Sami has requested a group meeting to review requirements documentation to ensure that the requirements are valid. As project documentation is submitted, the business analyst reviews the material in detail to ensure they are complete, correct, consistent, feasable, measuarable, precise, testatble, traceable, and unambiguious before handed off to the next level.
B. A requirements walkthrough session
Sami requested a group meeting to review requirements documentation, thus a walkthrough.
Walkthroughs are used to review the requirements with the stakeholders and receive confirmation that the requirements as stated are valid. PMI Guide to Business Analysis, section 7.6.2.4: Walkthroughs, page 228
Your sponsor, Dima, is concerned about the needed complexity and significant level of detail associated with the requirements traceability matrix and requirements documentation. What might Dima suggest to confirm that the documentation is in compliance with the organizational requirements before a signoff meeting with the project stakeholders?
A. A review by the testing and change leads before the meeting
B. The project manager review the documentation
C. An informal review by Sami and Sara, two of your peers
D. A formal review by the project manager and change lead
Dima wants to confirm that the documentation is correct before meeting with the project stakeholders. Analysts will request these types of reviews to ensure there are no glaring mistakes or issues that could raise during stakeholders reviews and validation session.
An informal review by Sami and Sara, two of your peers
Peer reviews, which can be either formal or informal requirement reviews, can be conducted at any point during the requirements process. Peer reviews are opportunities for colleagues to provide insight, make recommendations to strengthen the process, and ensure that there are no obvious errors or omissions that could cause non-compliance with organizational documentation standards. PMI Guide to Business Analysis, section 7.5.5.2: Peer Reviews, page 224
You are the business analyst for a high tech manufacturing plant, supporting a component of an overall program whose ultimate goal is to develop full automated production line. It has been determined that a production line must replace one of its main computer systems. Before approving the work, the governing body for the program requested an illustration showing all the systems that may be affected by this upgrade. What technique would you recommend?
A. An ecosystem map showing all the systems within both the production line and the partner companies, identifying occasional interface and data requirements.
B. A visual representation highlighting all the features of the solution, arranged in hierarchical edifice, identifying occasional interface and data requirements with the partner organizations.
C. A context diagram detailing all the direct and human boundaries within a system.
D. A map showing all the boundaries within the manufacturing plant proposed system, so that partner organizations and the governing body can get a better understanding of the proposed initiative.
The governing body is requesting a map that extends beyond the typical boundaries of architectural diagrams.
An ecosystem map showing all the systems within both the production line and the partner companies, identifying occasional interface and data requirements.
Ecosystem maps extend beyond the typical boundaries of architectural diagrams. When used holistically, they identify all the organizations and associated systems that are affected, or that may be affected, by the proposed solution. PMI Guide to Business Analysis, section 7.2.2.5: Ecosystem map, page 190
You’re presenting a business case to your executive sponsor, along with your senior financial analyst, John, highlighting the financial valuation methods used to justify the investment. Your sponsor, Sami, asked that you expand the analysis to include the initial and ongoing costs, along with the projected annual yield of the investment. Upon returning with John, you should prepare which of the following?
A. A return on investment (ROI) analysis
B. An internal rate of return (IRR) analysis
C. A net present value (NPV) analysis
D. A present value versus future value (PV vs. FV) assessment
*The analysis must include intial and ongoing costs, along with the projected annual yeild of the investment. The results of this analysis will form the basis for the rough order-of-magnitude estimates of costs benefits.
An internal rate of return (IRR) analysis.
The IRR analysis projects the annual yield of a project investment incorporating both initial and ongoing costs.
This scenario is testing your understanding of each of the valuation techniques. The results of this analysis will form the basis for the rough order-of-magnitude estimates of costs and benefits. An internal rate of return (IRR) analysis is performed when organizations are considering CAPEX (capital expenditure) projects to determine the profitability of projects. When the NPV for the project is set to zero, IRR is the discount rate. Business Analysis for Practitioners, 2.5.6.3 Internal Rate of Return, page 34
Following the completion of the stakeholder register, Sami added further details for each stakeholder, noting their office location, how many years they’ve been with company, and their availability. What did Sami perform?
A. A stakeholder characteristics analysis
B. A stakeholder interest analysis
C. A stakeholder salience analysis
D. A stakeholder grouping analysis
This falls in line with things like, attitude, complexity, culture, experience, location, and availability to properly plan and manage requirements throughout the project lifecycle.
A stakeholder characteristics analysis
Business analysts define stakeholder characteristics such as attitude, complexity, culture, experience, location, and availability to properly plan and manage requirements throughout the project lifecycle. Roles and responsibilities are a component of the requirements management plan, which is the roadmap for delivering the planned solution. PMI Guide to Business Analysis, section 4.1: Conduct Stakeholder Analysis, page 328
While executing the business analysis activities on the project, a key stakeholder suggested change request that will improve the efficiency of the final product. As a professional business analyst, you assessed the impact of the proposed change and found that the change will increase the cost of the project, but will add new important feature to the product. You sent the change request along with your assessment results to the CCB, they reviewed the change and decided to defer it until providing the necessary budget. Which of following should be your next step?
A. Revise the change request and resubmit it to the CCB.
B. Assess the change impact again to cut the extra cost (if possible).
C. Document the change status with the approved date of resubmission.
D. Adjust the impacted business analysis activities.
Document the change status with the approved date of resubmission.
Change deferred: The decision to defer making the change is documented, along with a rationale for the decision. When the change is provided with a proposed date for a future product release, it is noted and reflected in the appropriate plans to ensure that the change is addressed at the requested future date. In adaptive life cycles, this is equivalent to the proposed change being assigned a lower ranking in the product backlog. PMI Guide to Business Analysis, section 8.4: Manage changes to requirements and other product information, page 271
Sami, your test lead, and John, your business SME, are satisfied with the test results and have requested a go/no-go meeting to explain their actual versus expected results to all internal stakeholders. They have a disagreement on how the results should be presented. As the business analyst, what can you recommend?
A. Advise both Sami and John that individuals who make go/no-go decisions would like an impact analysis to accompany the presentation; either format is acceptable.
B. Advise both Sami and John that the stakeholders should be provided with summarized details ahead of the meeting, and that during the meeting results should be presented using graphs and charts at a summary level.
C. Advise Sami to share the details of the solution testing during the meeting.
D. Advise John to present the results, using graphs and charts, at a summary level.
Sami and John are about to have a facilitated workshop where a selected group of stakeholders (all internal) will meet to collaborate and work toward a stated objective.
Advise both Sami and John that the stakeholders should be provided with summarized details ahead of the meeting, and that during the meeting results should be presented using graphs and charts at a summary level.
With focus on running efficient meetings and properly preparing attendees. As with all meetings, there should be a clear agenda with known objectives; ideally, meeting minutes follow within 24 hours. In this scenario, the objective is to solicit a vote on a go/no-go decision. To facilitate a smooth discussion, all the details should be provided in advance of the meeting, whereas summary data is presented during the meeting. Business Analysis for Practitioners, section 4.5.5.3: Facilitated Workshops, page 78.
Sami, a business analyst in his organization was conducting interviews with stakeholders to elicit requirements. The sessions were not going well and he asked a senior business analyst for help. Stakeholders were confused on the size of the project and why the project was needed. Which of the following would the senior business analyst recommend?
A. Advise Sami to bring the requirements traceability matrix and supporting materials.
B. Advise Sami to make sure the stakeholders are on the approved stakeholders lists and ignore the remaining stakeholders.
C. Advise Sami to review the business case/need and solution scope.
D. Advise Sami to work more closely with the project manager and project sponsor to get the stakeholder in line with the project.
Details of why the project has been selected and complexity and idea of size can be taken from one document. The stakeholders want an understanding of why the project was undertaken and what is the benefit. Traceability Matrix has not been fully created yet as the requirements is still being elicted
Advise Sami to review the business case/need and solution scope.
Business Case: A documented economic feasibility study used to establish the validity of the benefits of a selected component lacking sufficient definition and used as a basis for the authorization of further project management activities. Business Need: The impetus for a change in an organization, based on an existing problem or opportunity. The business need provides the rationale for initiating a project or program. Business Case is majorly comprised with cost benefit analysis and business need. This does not directly address the need for clarity of the scope and business need. Details of why the project has been selected and complexity and idea of size can be taken from business case; here the stakeholders need an understanding of why the project was undertaken and its benefit here, the traceability matrix has not been fully created yet as requirements is still being elicited. Also missing is what the requirements trace to-i.e., the business requirements. PMI Guide to Business Analysis, section 4.6: Assemble Business Case, page 96
While conducting business analysis planning, estimation techniques are used to provide a quantitative assessment of likely amounts or outcomes. In this context, which of the following is a method of estimating duration or cost by aggregating the estimates of the lower level tasks?
A. Relative estimation
B. Estimation poker
C. Bottom up estimating
D. Affinity estimating
This type of estimate takes more time to complete, but it is more accurate than the other estimates.
Bottom-up estimation
They key word for this question is the “lower level tasks.”
Bottom-up estimating. A method of estimating duration or cost by aggregating the estimates of the lower level tasks. A decomposition model often identifies these lower-level tasks. PMI Guide to Business Analysis, section 5.4.2.3: Estimation Techniques, page 132.
Sami is working as the senior business analyst in an IT services firm, and the project he is currently involved in is about building a high-tech delivery application. During tracking the requirements, he used to give access of the backlog to the product owner to manage it, but his executive manager disagrees with this approach, and he told Sami that this process can only be managed by the change control board. Which of the following should be your response?
A. Ignore the executive manager advise as you are the SME when it comes to business analysis
B. Explain to the executive manager that the product owner is responsible of the backlog in agile projects
C. Explain to the executive manager that the product backlog can managed by CCB or product owner
D. Agree with the executive manager, and revise your approach
In adaptive life cycles, backlog management is the technique used to manage the changes.
Explain to the executive manager that the product owner is responsible of the backlog in agile projects
Backlog management is a technique used in adaptive approaches to maintain the list of backlog items to be worked on during a project. The list is ranked in order of business value or importance to the customer and sized by the development team so that the highest-value items are selected and delivered in the next development cycle. Proposed changes or new stories are added to the bottom of the backlog, where they sit until the next time the backlog is reprioritized. In adaptive life cycles, backlog management is the technique used to manage changes. PMI Guide to Business Analysis, section 8.4.2.1: Backlog Management, page 273
Sami is the senior business analyst in a software development project, and he is involved in analyzing the product requirements. In this context, which of the following actions can be done in order to determine which requirements are accepted, deferred, or rejected?
A. Obtain sign-off on requirements baseline using decision-making techniques
B. Evaluate product options and capabilities by using decision-making and valuation techniques.
C. Write requirements specifications using process (such as use cases, user stories), data, and interface details.
D. Allocate accepted or deferred requirements by balancing scope schedule, budget, and resource constraints with the value proposition using prioritization, dependency analysis, and decision-making tools and techniques.
Sami needs to assess the product requirements to determine which ones will be accepted, deferred, or rejected.
Evaluate product options and capabilities by using decision-making and valuation techniques.
Exam content outline: Domain 3, Task 3. Evaluate product options and capabilities by using decision-making and valuation techniques in order to determine which requirements are accepted, deferred, or rejected.
While conducing business analysis activities in your software development project, and during a brainstorming session, the team came up with sixty five ideas for the new solution. As the senior business analyst of the team, what should you do next?
A. Narrow down the number of ideas in collaboration with the project manager
B. Present the sixty five ideas to key stakeholders to select the best one
C. Let the team agree on throwing out ideas that are not feasible
D. Apply voting techniques to select the best five ideas
Brainstorm is comprised of two parts: idea generation and analysis.
Let the team agree on throwing out ideas that are not feasible
Brainstorming is a data gathering technique that can be used to identify a list of ideas in a short period of time (e.g., list of risks, stakeholders, or solutions to issues). Brainstorming is conducted in a group environment and is led by a facilitator. A topic or issue is presented and the group is asked to generate as many ideas or solutions as possible about the topic. Ideas are provided freely and rapidly and all ideas are accepted. Because the discussion occurs in a group setting, participants feed off of each other’s inputs to generate additional ideas. The responses are documented in front of the group so progress is continually fed back to the participants. The facilitator takes on an important role to ensure all participants are involved in the discussion and to ensure no one individual monopolizes the session or critiques or criticizes the ideas that are offered by others. Brainstorming is comprised of two parts: idea generation and analysis. The analysis is conducted to turn the initial list of ideas into a usable form of information. In business analysis planning, brainstorming can be leveraged to build the initial list of stakeholders, to discover new stakeholders, or to identify a list of tasks to be included in the business analysis work plan. Business Analysis for Practitioners, Section 3.3.1.1, Brainstorming, page 39.
The business owner of your wind turbine project asked you to present an analysis comparing potential solution options for the next generation of solar panels made of carbon fiber that would be commercially available in five years. Your analysis should be based on which of the following?
A. Would the analysis be based solely on business requirements, stakeholder requirements, and solution requirements?
B. Would the project be based on the project management iron triangle considerations of quality as constrained by time, cost, and scope?
C. Can the organization acquire the technology; is it financially feasible; and can the solution be delivered in the timeframe outlined?
D. Are the options presented aligned with the organization’s requirements for sustainability and reliability; can the organization acquire the required technology; is it financially feasible; and can the solution be delivered in the timeframe outlined?
When considering options, the business analyst may often need to assess their feasibility so the organization can determine the preferred options
Are the options presented aligned with the organization’s requirements for sustainability and reliability; can the organization acquire the required technology; is it financially feasible; and can the solution be delivered in the timeframe outlined?
When considering solution options, business analysts may often need to assess their feasibility so the organization can determine the preferred option. Feasibility studies often consider (a) operational, (b) technology/system, (c) cost-effectiveness, and(d) time constraints associated with each option. In this scenario, the business analyst is tasked with conducting a complete feasibility analysis. Organizations will often have “blue sky” ideas; given the current environment, we need to determine the “art of the possible.” Business Analysis for Practitioners, 2.5.4 Assess feasibility and organizational impacts for each option, page 30
You received a change request about one of the product key features. You assessed the change, and submitted a change request to the change control board (CCB) for approval. Few days later, you received a notification that the change was differed, which of the following should be your next step?
A. Adjust the impacted business analysis activities.
B. Document the decision to defer, along with the rationale for the decision.
C. Revise the change request and resubmit it to the CCB.
D. Arrange a meeting with the CCB to discuss the change.
Document the decision to defer, along with the rationale for the decision.
Change deferred: The decision to defer making the change is documented, along with a rationale for the decision. When the change is provided with a proposed date for a future product release, it is noted and reflected in the appropriate plans to ensure that the change is addressed at the requested future date. In adaptive life cycles, this is equivalent to the proposed change being assigned a lower ranking in the product backlog. PMI Guide to Business Analysis, section 8.4: Manage changes to requirements and other product information, page 271
For estimation purposes, the team is using poker estimation technique in order to size user stories. Six members are participating in the session, and when they turned the cards, four team members selected 5, one selected 7, and one selected 17. As you are facilitating this session, what should you do next?
A. Conduct a voting session to agree on the estimate.
B. Directly conduct another round to reach agreement.
C. Calculate the average estimate.
D. Ask the member who selected 17 to explain his point of view.
Ask the member who selected 17 to explain his point of view.
Each person participating in estimation poker is given a series of cards with the agreed-upon scale. Team members typically will converge upon a reference estimate for one of their project’s product backlog items, often using a Delphi or wide-band Delphi approach. The reference estimate is then used as a basis for subsequent relative estimates for each additional product backlog item that is to be estimated. Team members hold up cards that represent their estimates of the level of effort required in the context of their agreed-upon reference estimate, expressed within the chosen scale. Those who created the highest and lowest estimates explain their rationale, following which everyone estimates again. The process repeats until convergence is achieved. PMI Guide to Business Analysis, Section 5.4.2.3, Estimation Techniques, page 133.
During business analysis planning, the team should establish how decisions will be made across the business analysis effort to avoid misunderstandings or conflict later on when performing the work. In this context, which of the following techniques reaches a decision by everyone agreeing on a single course of action?
A. Plurality
B. Majority
C. Unanimity
D. Autocratic
Unanimity
A few decision-making techniques include the following: Autocratic: One individual makes the decision for the group. Delphi: Reduces bias and prevents any one person from imposing undue influence on the team. Delphi reaches a decision through consensus. Force field analysis: Reaches a decision by exploring the forces that are for or against a change and assessing which is greatest. Majority: Reaches a decision when support is obtained from more than 50% of the members of the group. Plurality: Obtains a decision by taking the most common answer received from among the decision makers. Unanimity: Reaches a decision by everyone agreeing on a single course of action. PMI Guide to Business Analysis, section 8.3.2.7: Group Decision Making Techniques, page 267.
While working as the business analyst for a web development project that is managed using an agile methodology, you were just done with your team with identifying the subset of product backlog items that the development team will work on for the upcoming iteration. Which of the following techniques is the one you just used?
A. Iteration review
B. Retrospective
C. Iteration planning
D. Backlog refinement
iteration planning
It is a technique used in agile methodologies to plan the work completed during the upcoming iteration or sprint. The teams will review the product backlog and identify the subset of backlog items that they will work on during the iteration.
In adaptive approaches, iteration planning or sprint planning is the activity used to identify the subset of product backlog items that the product development team will work on for the current iteration or sprint. The entire team collaborates just before or at the beginning of the iteration to select the backlog items that should be part of an iteration backlog. Business analysis activities ensure that product backlog items are ready to be developed. The business analysis responsibilities entail choosing items for the iteration backlog that are sufficiently elaborated upon and most important in terms of delivering business value. PMI Guide to Business Analysis, Section 7.7.2.3, Iteration Planning, page 233.
After several weeks of effort, you have just completed the business analysis work plan for a highly complex project. Following a review session with the project team and key stakeholders, your project manager, Sami, has expressed concern about full integration with the project management plan. To simplify matters, which of the following should you suggest?
A. The fine details can be tracked in a separate plan; summary information should be integrated with the overall project management plan.
B. Considering the highly complex nature of the project, we can maintain two separate project plans.
C. To properly manage the project, both plans need to be fully integrated.
D. Because a majority of the project is focused on requirements, all the details can be integrated, and as the business analyst, you will maintain the overall plan.
The fine details can be tracked in a separate plan; summary information should be integrated with the overall project management plan.
Work plans developed by the business analyst detail the product activities to be accomplished by the performing organization. It’s leading practice to have an integrated business analysts work plan at the summary level, with the other project activities. This can assist with sequencing of activities, leveling of resources, and helping to uncover any gaps or inconsistencies. In doing so, the business analyst will have accountability for managing and directing the work detailed on their plan, and reporting status to the project manager. Business Analysis for Practitioners, 3.5.5 Review Business Analysis Plan with Key Stakeholders, page 67
In order to manage changes of the requirements baseline, traceability matrix is one of the best tools. As a professional business analyst, you linked all the product requirements back to business goals and objectives. Your executive manager was satisfied to see how requirements contribute to achieving organizational goals, but the technical team was not satisfied. Which of the following is the most probable reason of their dissatisfaction?
A. Because requirements should be traced forward, not backward only.
B. Because requirements traceability should be shared with the technical team only.
C. Because requirements should be traced backward, not forward only.
D. Because requirements should not be traced to organizational goals and objectives.
Because requirements should be traced forward, not backward only.
Traceability is the ability to track information across the product life cycle by establishing linkages between objects. These linkages are also known as relationships or dependencies. Traceability is sometimes qualified as bidirectional, or forward and backward, because requirements are traced in more than one direction. For instance, backward traceability is performed from the requirements to the scope features and business goals and objectives that triggered them; forward traceability is performed from the requirements to design and test components and, ultimately, the final product. Tracing can also be performed laterally-for instance, tracing textual product information to models. PMI Guide to Business Analysis, Key Concepts for Traceability and Monitoring, page 253
A business analyst is trying to understand the magnitude of the problem or opportunity to help determine an appropriately sized solution as soon as a broad understanding of the situation is obtained. The business analyst is lacking internal data to discover further insight or “sizing up” the situation. The business analyst observed that it is not feasible to collect data using quantitative techniques, what can be done in this situation?
A. Sampling
B. Questionnaire
C. Document analysis
D. Benchmarking
Benchmarking
When no internal data exist or when it cannot be feasibly collected, in that case benchmarking may be performed. Benchmarking is a comparison of the metrics or processes from one organization against a similar organization in the industry that is reporting or finding similar industry averages. Benchmarking may also involve comparing internal organizational unit or processes against each other. Document Analysis, Questionnaire and sampling are the tools which can be used in data collection and business analyst identified that collecting data is not feasible. PMI Guide to Business Analysis, section 4.1.2.1: Benchmarking, page 60
You are in the process of determining the viable options in order to recommend one option to your executive management, and you want to perform a comparison of your organization’s practices, processes, and measurements of results against established standards or against what is achieved by a “best in class” organization within its industry. In this situation, which of the following techniques can help you?
A. Market analysis
B. Competitive analysis
C. Brainwriting
D. Benchmarking
Benchmarking
This is a technique that involves comparing an organization;s practices and processes and measurements of results against industry standards or against the practice of leading organizations in the industry.
The subject matter experts from manufacturing-Dima, Suzan, and Sara -seem to be at an impasse and cannot agree on the solution to address the robotic control arm. All are highly skilled in robotics and considered experts in their field. What can you suggest to mediate the conversation?
A. Facilitate a conversion with the team and have them list the strengths and weaknesses of each proposed solution.
B. Create a grid listing options, so they can be ranked and voted upon.
C. Create a chart and list the forces for and against each option.
D. Build an options analysis chart and facilitate a conversion to derive a resolution.
Create a grid listing options, so they can be ranked and voted upon.
It allows the SME to evaluate and compare the strengths and weaknesses of each proposed solution and to weigh the pros and cons of each option.
The weighted rankings and scorings technique, also used during the needs assessment to rank solution options, is used during analysis to resolve requirements-related conflicts. The process is identical to what was used during the needs assessment, whereby solution options are listed, ranked, and voted upon by team members. The tool is used objectively to compare solution options; the option with the highest score is selected. PMI Guide to Business Analysis, section 4.4.2.8: Weighted Ranking, page 90
At the final stages of the project you are working in as the business analyst, you faced a requirement related conflict that you were not able to resolve by applying different techniques. You decided to escalate this conflict. In which of the following documents should you find the escalation path to follow?
A. Elicitation approach
B. Requirements management plan
C. Solution evaluation approach
D. Business analysis plan
Business analysis plan
Conflicts may arise at any point in the business analysis process. Whether the conflict is between business units voicing opposing views of what the solution should be or a solution team and a product stakeholder disagreeing on the way to solve the business problem, the first order of business is to determine what the problem is that the parties are attempting to solve. The business analyst mediates the situation by discussing the differences and by understanding the points of view of each stakeholder. Several discussions may need to occur before a resolution is reached. When unable to reach a decision, the issue needs to be escalated. The process for making decisions, resolving requirements- related conflicts, and the escalation path to follow when negotiating efforts fail should have been defined during business analysis planning. Business Analysis for Practitioners, Section 4.15, Resolve requirements-related conflicts, page 134.