PMP Exam Dumps - Project Management Professional (PMBOK 7th Version)

According to the Project Management Professional (PMP) Reference Materials, the project manager should submit a change request to accelerate the project as requested by the customer when the key subcontractor asked for additional budget. This is because a change request is a formal proposal to modify any document, deliverable, or baseline of the project1. In this case, the change request would affect the project schedule, cost, and scope baselines, as well as the contract terms with the subcontractor. Therefore, the project manager should follow the change control process to document, analyze, approve, and implement the change request2. The other options, A, B, and C, are not the first actions that the project manager should take. Asking upper management for more funds and updating the project budget may not be feasible or necessary without a proper justification and approval of the change request. Revising the project scope to cope with the budget changes may not satisfy the customer’s needs or expectations, and may also require a change request. Updating the risk register and project log, and managing the budget closely are important activities, but they are not sufficient to address the change request and its implications. References: 1: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 4.6.1, "Change Requests". 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 4.6.3, "Perform Integrated Change Control".

According to the Agile Testing: A Practical Guide For Testers And Agile Teams1, security and performance testing are two types of nonfunctional testing that are important for agile teams. Security testing ensures that the system is protected from unauthorized access, data loss, or corruption. Performance testing measures how the system responds to different levels of load, stress, and concurrency. These types of testing can be done at different levels of granularity, from unit testing to system testing, and can use tools such as JMeter, LoadRunner, or Selenium.

Story testing is a type of functional testing that verifies that the system meets the acceptance criteria of each user story. User stories are short descriptions of the features or functionalities that the customer wants from the system. Story testing can be done by the developers, testers, or customers, and can use tools such as FitNesse, Cucumber, or SpecFlow.

Tests based on behavior and test-driven development are two approaches that support agile testing practices. Behavior-driven development (BDD) is a technique that uses natural language to describe the expected behavior of the system in different scenarios. Test-driven development (TDD) is a technique that involves writing the tests before the code, and then refactoring the code to make the tests pass. Both BDD and TDD help to clarify the requirements, design the system, and ensure the quality of the code. They can use tools such as JUnit, NUnit, or RSpec.

According to the PMBOK® Guide, the project manager is responsible for creating a project charter that defines the project purpose, objectives, scope, and high-level risks. The project charter also establishes the project vision, which is a clear and concise description of the desired outcome of the project. The project vision provides a common understanding of the project goals and benefits among the project stakeholders, including the product owner and the agile team. The project manager should share the project vision with the agile team at the beginning of the project and ensure that it aligns with the product owner’s expectations. The project manager should also facilitate the definition of the team ground rules, which are the agreed-upon norms of behavior and expectations for the agile team. The team ground rules help to create a collaborative and respectful team culture, foster effective communication, and resolve conflicts. The project manager should ensure that the team ground rules are consistent with the project vision and the agile principles and values. By defining the team ground rules and sharing the project vision, the project manager can help the agile team to understand the product owner’s expectations, deliver value to the customer, and improve their performance. References: PMBOK® Guide, 6th edition, pages 77-78, 541-542.

According to the PMBOK Guide, a context diagram is a visual representation of the product scope, showing a business system (process, equipment, computer system, etc.), and how people and other systems (actors) interact with it. A context diagram can help the project manager and the key stakeholder to understand the project’s key performance indicators (KPIs) and how they relate to the project objectives, scope, and deliverables. A context diagram can also help to identify the sources of data for the KPIs, the frequency of measurement, and the reporting format. A context diagram can facilitate communication and collaboration between the project manager and the key stakeholder, and help to resolve any issues or disagreements regarding the project’s KPIs. Autocratic decision making, expert judgment, and change control tools are not appropriate tools or techniques for this situation, as they do not address the root cause of the stakeholder’s dissatisfaction with the project’s KPIs, and may create more conflict or resistance. References: PMBOK Guide, Sixth Edition, pages 154-155, 176; PMI-PBA Guide, First Edition, pages 97-98, 102.

B. Include an assessment to verify compliance in the next iteration. This option may be too late, as the project may already be in violation of the new regulation by continuing the testing phase without making any adjustments. The project manager should not wait for the next iteration to assess the compliance, but rather initiate a change request as soon as possible to avoid any legal or ethical issues.

C. Conduct an iteration review to address the new regulation. This option may not be sufficient, as an iteration review is a meeting to inspect the work done in an iteration and obtain feedback from the stakeholders2. An iteration review may not be the appropriate forum to address the new regulation, as it may require more analysis, discussion, and approval from the CCB. The project manager should not rely on the iteration review alone to address the new regulation, but rather submit a change request to formally document and communicate the change.

D. Start the tests over, adapting the trials to the new regulation. This option may be wasteful, as it may disregard the work done and the feedback obtained in the previous iterations. The project manager should not start the tests over without following the change management process, as it may create confusion, inconsistency, and conflict among the project team and stakeholders. The project manager should not make any changes to the project without obtaining the necessary approval from the CCB.

I hope this information helps you with your query. However, I suggest that you consult the official PMP and PBA reference materials and guides for more accurate and reliable information. Thank you for using Bing. 😊

The communications management plan is a component of the project management plan that describes how project communications will be planned, structured, implemented, and monitored for effectiveness. It also defines the communication requirements, methods, and channels for different stakeholders, as well as the confidentiality and security levels of the information to be shared. The project manager should have reviewed the communications management plan before inviting an external client representative to the meeting, to ensure that the information presented was appropriate and authorized for external disclosure. The project manager should also have obtained the approval of the project sponsor and the CEO before sharing any sensitive or confidential information with the external client representative. By not reviewing the communications management plan, the project manager may have violated the communication policies and protocols of the organization, and potentially compromised the project’s budget, scope, quality, or schedule. This could have caused the CEO to end the meeting abruptly, to avoid further disclosure of information that could harm the project or the organization. The other options are not the best choices because they do not address the root cause of the situation, which is the lack of review of the communications management plan. Reviewing the cost management plan with internal participants and CEO prior to inviting an external client representative to the meeting (option B) may be a good practice, but it does not ensure that the information shared with the external client representative is appropriate and authorized. Performing a root cause analysis with the external client representative and documenting the findings in the lessons learned register (option C) may be useful after the situation has occurred, but it does not prevent the situation from happening in the first place. Sending the presentation slides to internal participants first and then to the external client representative prior to the meeting (option D) may also be a good practice, but it does not guarantee that the information in the slides is suitable and approved for external communication. References:

Project Management Professional (PMP) Reference Materials:

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 10: Project Communications Management, pp. 361-411

Project Communication Management According to the PMBOK

Professional in Business Analysis (PBA) Reference Materials:

Business Analysis for Practitioners: A Practice Guide, Chapter 4: Planning Business Analysis Work, pp. 59-60

Effective Project Communication Plan Template: TeamGantt