PMI-PBA Mock Exam Lite - 2 Flashcards
You have been asked to analyze the current sales and marketing capabilities of your organization and design and implement a sales pipeline management process. In order to proceed, you need an initial list of key stakeholders to start your conversations. Which of the following techniques could be used to quickly generate an initial list of stakeholders?
Reviewing organizational charts
Since you are designing a new process, you can observe the process or review the process documentation. Developing RACI matrix is irrelevant here. However, reviewing the organizational charts will help you identify the initial list of stakeholders. [Business Analysis for Practitioners: A Practice Guide, page 40; The PMI Guide to Business Analysis, page 111]
You have recently kick-started a datacenter upgrade project and are now meeting different stakeholders to understand their needs and expectations from the project. The datacenter currently serves a number of business critical applications and attention to risk management is critical. Which of these is not a data gathering technique used in the Identify Risks process?
Delta technique
Delta technique is not a valid type of data gathering technique. [PMBOK® Guide 6th edition, Page 409]
You are leading the development of a robotic process automation product. You need to present the product’s features at a conference but due to the sheer number of the backlog items you need to classify these in groups. All of the following techniques can be used to classify the product features EXCEPT:
Salience Model
A salience model is used to classify stakeholders and not product features. The rest of the choices can all be used to classify product features. [The PMI Guide to Business Analysis, pages 79, 81, 234]
You need to identify all impacted stakeholders for your project. You have identified some SMEs who can help you with the stakeholder identification. In order to engage with these SMEs, you are currently considering either using questionnaires or using brainstorming in a facilitated environment. In comparison to questionnaires and surveys, which of the following is a benefit of using the brainstorming technique for stakeholder identification?
Participants feed off each other’s inputs to generate additional ideas.
During brainstorming sessions, participants feed off each other’s input to generate additional ideas. This is not possible through questionnaires and surveys. [Business Analysis for Practitioners: A Practice Guide, page 39; The PMI Guide to Business Analysis, page 111]
James is currently managing a software upgrade project. He has recently identified and analyzed his key project stakeholders. He is now searching his organizational process assets for a template with which he can update the results of this analysis along with the planned strategies required to engage the stakeholders effectively. Which of the following should he search for?
Stakeholder engagement plan
A change request form is used to initiate a change in the project baselines. The risk management plan does not document the stakeholder engagement strategy. Although the stakeholder register contains stakeholder identification, classification and assessment information, it does not record the stakeholder engagement strategy. James should search for a stakeholder engagement plan template where all this information can be updated. [PMBOK® Guide 6th edition, Page 522]
Your product team has recently released a new accounting system into the market which has not been well-received by your customers. You have invited a few SMEs for a workshop to identify the product features that customers find problematic. Which of the following elicitation techniques should you use for the workshop?
Speedboat
Speedboat is an elicitation technique that uses game play to elicit information about product features that customers/stakeholders find problematic. [The PMI Guide to Business Analysis, page 166]
An Agile team is currently working with the product owner in defining project requirements. Some of the features would not be developed in the near future. It was recommended to write one much larger user story for such features rather than multiple fine-grained user stories. Such stories are called:
Epics
Larger user stories are known as epics. [The PMI Guide to Business Analysis, page 95]
You are leading the development of a software application for the finance department in your organization. You have supplied the ERD to the database designer who has designed the database for the application. The developers have already used the wireframes to develop the UI screens. Which of the following should you pass over to the developers so that they can limit the user access with regards to data access and update rights at the UI-layer?
CRUD matrix
CRUD, defined as create (C), read (R), update (U), and delete (D), represents the operations that can be applied to data or objects. CRUD matrices describe who or what has permission to perform each of the CRUD operations on elements, such as data or user interface screens. [The PMI Guide to Business Analysis, page 197]
You have been assigned as the lead business analyst for an enterprise system upgrade project. It has been decided that the project will be managed using a predictive approach. You are currently determining the requirements management approach for the project. Which of the following requirement lifecycle states should you select for the project?
Defined, elaborated, verified, validated, and prioritized
The requirements life cycle on predictive projects represents the various phases or states through which a requirement moves as it is defined, elaborated, verified, validated and prioritized. When using an adaptive delivery approach, the requirement states may be more implicit. User stories may be states as not ready, ready, or done. [The PMI Guide to Business Analysis, page 179]
You are managing an Agile project with constantly changing requirements impacting the product design and features. You are worried that soon the product development will lose its alignment with the business case that authorized this project. You do not have any authority to update the busines case. This would be a major headache if someone audits the project in the future. You are considering minimizing this risk by acquiring a capability to manage your product requirements, maintaining a change log, and maintaining the history of each requirement lifecycle details. Which of the following tools should you acquire?
Requirements management tool
A requirements management tool allows requirements and other product information to be captured and stored in a repository. This tool will help you not only to manage your requirements by their individual requirement lifecycle stages, it will help you maintain a change log and an audit trail. [The PMI Guide to Business Analysis, page 213]
A product team has recently developed a new information system that would replace the existing legacy system in the organization. You are responsible for the successful rollout of this new system. You have identified that there is a significant difference between the new and the old system, and this needs to be carefully analyzed to train the users on the new system. You conduct a detailed gap analysis for each user role and identify training requirements. You have also completed the readiness assessment. What should you do next?
Develop a transition plan.
Once the training and other transition requirements have been identified, the next logical step is to define the transition plan. [The PMI Guide to Business Analysis, page 297]
In projects following adaptive lifecycles, what are the two critical components of iterative scheduling with a product backlog?
User stories and time-boxed periods of work
In adaptive life cycles, the requirements are documented in user stories that are then prioritized and refined. The product features are developed using time-boxed periods of work. [PMBOK® Guide 6th edition, Page 177]
A product team is developing a software solution using an adaptive project life cycle. When should the product team request the stakeholders for formal release signoffs on such projects?
Prior to each product release
Depending on organizational norms, obtaining a release decision may include obtaining signoff. For an iterative or adaptive project life cycle, informal signoff generally occurs at the end of each sprint or iteration, with formal signoff, when required, occurring prior to each release of the solution to the production environment. [The PMI Guide to Business Analysis, page 296]
How does time-boxing help minimize scope creep in agile projects?
It forces the team to process essential features first, then other features.
Time-boxed periods are durations during which the team works steadily toward completion of a goal. Time-boxing helps to minimize scope creep as it forces the teams to process essential features first, then other features when time permits. [PMBOK® Guide 6th edition, Page 182]
A product team has recently developed a new product. Several performance issues were reported by the stakeholders during the UAT sessions. You have collected the necessary data regarding the reported issues and want to analyze the results. Which of the following techniques would you use to analyze the performance divergence from the acceptance criteria?
Variance analysis
Variance is a quantifiable deviation, departure, or divergence from a known baseline or expected value. Variance analysis is a technique for determining the cause and degree of difference between the baseline and actual performance. [The PMI Guide to Business Analysis, page 293]
You are interested in developing a new business intelligence product. A small team of SMEs have brainstormed and gathered a list of potential product features. You are now analyzing these product features using a purpose alignment model to ensure strategic alignment. What should be your strategy for the features that are neither differentiating nor mission critical to the organization?
Do not build these features.
Features that are neither differentiating nor mission critical to the organization and generally not built. [The PMI Guide to Business Analysis, page 82]
How is the scope of Prepare for Elicitation process different to the scope of the Determine Elicitation Approach process?
Elicitation preparation is the planning performed prior to the start of each elicitation activity, while determining elicitation approach is the planning performed prior to commencing the elicitation stage.
Elicitation preparation is the planning performed prior to the start of each elicitation activity, while determining elicitation approach is the planning performed prior to commencing the elicitation stage. [The PMI Guide to Business Analysis, page 160]
An ecosystem map is a scope model that shows all the relevant systems, the relationship between systems, and optionally, any data objects passed between them. Ecosystem maps are most useful when they are created:
At the beginning of a project
Ecosystem maps are most useful when they are created at the beginning of projects to understand all the systems that may be affected by or that will impact the in-scope systems. [The PMI Guide to Business Analysis, page 190]
You have recently taken over leadership of an Agile team that is halfway through a complicated project. You have recently examined project requirements and now want to get an idea of the team velocity. Which document should provide some insight on the team’s velocity?
Burndown chart
You need to have a look at the burndown chart. The burndown chart will tell the number of story points remaining and the current team’s velocity. Teams might update velocity on a Kanban board, but this is not a common practice. [The PMI Guide to Business Analysis, page 131, 148]
You have recently taken over the leadership of a software development project. Due to the complexity of the project and the highly regulated project environment, you are considering using a requirements management tool on this project. All the following are typical features of a requirements management tool except:
Cost performance management
Requirements management tools allow requirements and other product information to be captured and stored in a repository. These tools help maintain audit trails and perform version control to assist with change management. These tools also facilitate review and approval processes thorough workflow functionality. Requirements management tools catered to adaptive projects may include additional functionality to create and manage product and iteration backlogs, and produce burndown charts. Cost performance management is not a typical component of a requirements management tool. [The PMI Guide to Business Analysis, page 260]