Last Updated on March 19, 2022 by Admin 2
PMI-PBA : PMI Professional in Business Analysis : Part 04
Which of the following actions will contribute most to the success of the initial stage of the project?
- Interview stakeholders to clearly define the problem.
- Establish the change control process of the project.
- Define the acceptance criteria required during the acceptance phase.
- Document the requirements and obtain sign-off.
A business analyst for Company A has been assigned to a three-year project to assist health insurance Company B with implementing and testing a new set of medical codes. The business analyst has identified many stakeholders who will participate in the project. For example, Company A will designate technical staff to write and code the requirements and provide a testing team to test the new functionality. The senior director of Company B will require weekly progress updates. The project manager from Company A will create project plans, schedule meetings, and provide meeting minutes.
In the scenario above, what is the role of the technical staff and testing team from Company A?
Testing on a project has been completed. In order to proceed with deployment, a decision is needed.
Who should the business analyst contact to review the testing results and get approval to proceed with deployment?
- The tester identified in the testing strategy
- The project manager identified in the project charter.
- The project sponsor identified in the scope document.
- The person identified in the RACI matrix.
The business managers had clearly stated that the delivered website must simultaneously accommodate millions of users around the globe. However, within the first week of the production launch, the website crashes frequently.
This situation could have been averted if:
- critical business requirements were accommodated and tested.
- essential product requirements were captured and tested.
- quality attributes were captured and tested.
- nonfunctional requirements were identified and tested.
The best way to ensure the integrity of requirements is to:
- implement version control, maintain a history of requirements changes, and track the status of each requirement
- establish a requirements baseline, establish a change control board, and label each requirement uniquely
- use a requirements management tool, measure requirements volatility, and maintain a history of requirements changes
- establish a change control board, track the status of each requirement, and use a requirements management tool.
An insurance company embarks on a project to replace its current enrollment and billing software application, which will no longer be supported by the end of the calendar year. The new enrollment and billing application must be implemented before the current vendor contract ends. The business analyst gathers the initial requirements for the new enrollment and billing application. Based on the large volume of requirements, the business analyst realizes that the requirements will need to be prioritized.
Which requirements prioritization method should the business analyst use for this project?
- Risk analysis
- Weighted ranking
Projects have been managed well and completed on schedule and on budget. However, successful completion of the projects has not improved the company’s performance and profitability.
Which of the following should have been implemented to ensure that the projects would improve the company’s performance and profitability?
- A risk plan
- A strategies and goals analysis
- A project management plan
- A review with appropriate stakeholders
During the initial phase of a project, which technique could assist in identifying and categorizing the stakeholders?
- Organization modeling
- Power/interest grid
- Business activity model
- RACI matrix
A business analyst anticipates receiving requirements changes. What should the business analyst do to avoid scope creep?
- Meet with the stakeholder and discuss timeline impact.
- Define a requirements baseline and implement a change control process.
- Implement only the original requirements.
- Refer changes to the project manager.
Which statement accurately depicts what changes can be made to requirements after they are baselined?
- Requirements can be changed through a defined process.
- Requirements cannot be changed once development begins.
- Requirements cannot be changed once user acceptance testing begins.
- Requirements can be changed only with sponsor approval.
The main output is the scope baseline, which consists of three documents; the scope statement (including both project and product requirements), the WBS(s), and the WBS dictionary. These are reviewed and upon approval, the scope baseline is created. Once that baseline has been approved, changes can only be made through a change control procedure. The scope baseline will be used to continually compare the actual results and work being done on the project to the original, approved scope.
When faced with a tight timeline, the project sponsor suggests that the project team start development without creating traceability artifacts. What should the business analyst do?
- Negotiate for a quick approval of a reduced set of traceability artifacts.
- Explain the value of requirements traceability.
- Eliminate traceability activities for the project.
- Start development activities without traceability items.
A business analyst assigned to review test output for a project realizes that an approved requirement has been missed. Which technique could the business analyst have used to ensure that requirements were delivered as stated?
- Use cases
- Requirements management plan
- Traceability matrix
- Work breakdown structure
After implementation of the product, the customer reports defects. What is the best course of action to take?
- Escalate the issue to the project manager since the acceptance was given by the customer.
- Do nothing since the solution is now the responsibility of the operations manager.
- Compare reported defects with user acceptance test results.
- Involve the end users and plan a new round of acceptance tests to check the gaps.
A company has just finished the development work for a new software sales tracking application and is in the process of validating that the new application meets all of the acceptance criteria defined for the business requirements. During the validation process, a stakeholder discovers that the application does not provide the selection criteria needed to produce the sales volume reporting required by the company’s financial department. The business analyst for the project determines that the selection criteria needed was not specified in the system requirements or design specifications.
Which of the following tools and/or techniques might be used by the business analyst to determine how the selection criteria requirement was missed?
- Root cause analysis, fishbone diagram, and/or the Five Whys
- Scope modeling, Ishikawa diagram, and/or the Five Whys
- Root cause analysis, problem tracking, and/or benchmarking
- Cause and effect diagram, brainstorming, and/or the Five Whys
A major stakeholder of a project is surprised to learn that a particular requirement was not implemented during the latest launch. The business analyst tells the stakeholder that the requirement status was changed to “deferred”.
What could have prevented the stakeholder from being surprised about the status change?
- The status should have been reviewed prior to project launch.
- The status should have been communicated to all project stakeholders.
- The status should have been updated in the traceability matrix.
- The status should have been communicated to the requirement’s source.
Last year, a company registered a high number of complaints about its customer service. Which of the following tools or techniques can help to identify the high-priority changes needed to improve that service?
- A work breakdown structure analysis of the service
- A cause-and-effect diagram
- A Pareto analysis
- A flowchart of the service
The project sponsor needs to know which requirements will be implemented. Which of the following would be the most valuable for a business analyst to provide?
- Requirements baseline document
- Requirements management plan
- Requirements impact analysis
- Requirements traceability matrix
A business analyst has received a test result report that shows evidence of defective functionality. The business analyst checks the test result again and verifies that the functionality behaves according to the requirements.
At this point, the business analyst should first:
- let the users decide if the test result is acceptable.
- change the requirement according to the test result.
- verify that the test case is incorrect.
- ask the tester to perform the test again.
A project that was going well for the last few months has encountered a situation-regulatory authorities have deemed that the project does not meet their requirements. Although regulatory requirements were identified during an earlier phase of the project, there is no substantial evidence to prove that the requirements were formally rejected.
This could have been avoided if:
- the customer met with regulatory authorities to verify that their requirements were also considered.
- a change control process for requirements and their statuses was followed.
- the project manager circulated the meeting minutes after the discussions with all the attendees.
- the project team documented customer requests and obtained sign-off.
Company A has initiated a project to update their online ordering system. The business analyst has noticed that the purchasing department, a primary stakeholder, is excluded from the list of stakeholders.
In which reference material can the business analyst find information about the missing project stakeholders?
- Business analyst communication plan
- Business case
- Organizational chart
- Business analysis plan