On day four of a 15-day sprint, the team should continue with the sprint work as planned and keep monitoring the burndown chart. The burndown chart is a visual representation of the work left versus the time remaining in the sprint. If the "Actual" line closely follows the "Planned" line, it indicates that the team is on track. Making adjustments or changing the sprint scope at this stage is premature unless there are significant deviations or impediments1. The team should maintain their current pace and monitor progress, making adjustments only if necessary as the sprint progresses2. References: "Burndown Chart: What it is, How to Use it, Example [2024]" by Asana; "Scrum Sprint Burndown Chart [Everything you Need to Know]" by KnowledgeHut12.

According to the PMBOK Guide, a root cause analysis is a technique used to identify the underlying reasons for the occurrence of a problem or a deviation from the expected performance. It is part of the monitor and control project work process, which involves tracking, reviewing, and reporting the project progress and performance, and implementing corrective or preventive actions as needed. A root cause analysis can help the project manager to understand the causes of the budget shift and to take appropriate actions to address them. It can also help to prevent similar problems from happening again in the future. Adjusting the original budget estimates, negotiating the project changes, or reviewing the activity duration are possible actions that the project manager can take after performing a root cause analysis, but they are not the first step to do when faced with a significant budget shift. References:
* PMBOK Guide, 6th edition, pages 121-122, 4.5 Monitor and Control Project Work
* PMBOK Guide, 6th edition, pages 686-687, Root Cause Analysis
* PMP Sample Test Questions, question 1, answer D

A project charter is a project planning document that sells the project to stakeholders and sponsors. It provides a preliminary delineation of roles and responsibilities, outlines the project's key goals, identifies the main stakeholders, and defines the authority of the project manager. A project charter is essential for any project, regardless of its size or complexity, as it serves the following purposes:
* It authorizes the project and grants the project manager the permission to use organizational resources
* It serves as a primary sales document that summarizes the project's value proposition and return on investment
* It acts as a roadmap that guides the project team and stakeholders throughout the project lifecycle
* It helps to manage the project scope and avoid scope creep by establishing the project boundaries and deliverables
* It facilitates communication and alignment among the project team, sponsors, and stakeholders by clarifying the project objectives, assumptions, risks, and constraints Therefore, the project manager should explain to the sponsor that a project charter is necessary to ensure agreement on scope and deliverables and to define the project manager's responsibilities. Without a project charter, the project may face the following risks:
* Lack of clarity and direction for the project team and stakeholders
* Misalignment of expectations and goals among the project team, sponsors, and stakeholders
* Scope creep and change requests that may impact the project schedule, budget, and quality
* Conflicts and disputes over roles, responsibilities, and authority
* Reduced stakeholder engagement and support References:
* What is a Project Charter? Complete Guide & Examples
* How to Write a Project Charter: Examples & Template Included
* Project charter - Wikipedia

The project manager should determine the value of the vendor's bid by calculating the expected monetary value (EMV) of the bid. The EMV is the product of the probability and the impact of a risk event or opportunity1. In this case, the vendor's bid has two possible outcomes: a cost overrun of US$100,000 with a
65% probability, or a cost saving of US$50,000 with a 35% probability. The EMV of the bid is calculated as follows:
EMV = (0.65 x 100,000) - (0.35 x 50,000) = 47,500
The value of the vendor's bid is the original bid amount plus the EMV, which is:
Value = 500,000 + 47,500 = 547,500
Therefore, the correct answer is C. US$547,500.
References: (Professional in Business Analysis Reference Materials source and documents) PMBOK Guide, 6th edition, Section 11.5.2.2, "Expected Monetary Value Analysis"

The project manager should evaluate the situation and identify ways to compress the schedule without impacting baselines, as this is a strategy for handling delays in project programming activities. According to the PMI website, project delays can occur due to various reasons, such as complexity, resource constraints, poor communication, or risk management issues. When a project is behind schedule or at risk of a critical delay, the project manager should analyze the root causes and the impact of the delay, and determine the best course of action to bring the project back on track. One of the possible actions is to compress the schedule, which is a technique to shorten the project duration without changing the project scope. There are two methods of schedule compression: crashing and fast-tracking. Crashing involves adding or adjusting resources, such as people, equipment, or materials, to critical path activities, to reduce their duration. Fast- tracking involves performing critical path activities in parallel or partially in parallel, to reduce their overall duration. Both methods have advantages and disadvantages, and the project manager should weigh them carefully before applying them. The project manager should also monitor and control the schedule performance, and communicate any changes or updates to the stakeholders1.
The other options, asking the team to work overtime, checking the scope, or submitting a change request, are not the best ways to handle delays in project programming activities. Asking the team to work overtime may not be feasible or effective, as it may increase costs, risks, or rework, and may also demotivate or burn out the team members. Checking the scope may help the project manager to verify if there is scope creep, which is the uncontrolled expansion of the project scope, but it may not address the actual causes or consequences of the delay. Submitting a change request may help the project manager to follow the change management process and seek approval from the project sponsor or the change control board, but it may not be necessary or desirable, as it may imply that the project manager is unable to manage the schedule within the agreed baselines.
: 1 A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Sixth Edition, Chapter
6.6 2 Business Analysis for Practitioners: A Practice Guide, Chapter 4.3.4 3 How to Manage Project Delays: 6 Effective Tips - ProProfs Project Blog 4 How Can Project Managers Handle Project Delays? - Online Tutorials Library 5 Dealing with delays - Project Management Institute