Three-point estimating is a technique that can be particularly useful when there is uncertainty about the individual task estimates. It involves the development team providing optimistic, pessimistic, and most likely estimates for each task, which can then be used to calculate an expected duration for the entire project. This method is beneficial when the team lacks experience with similar projects, as it allows for a range of possible outcomes to be considered, which can lead to a more realistic and reliable estimate123.
References:
* Expert-Guided Software Project Estimation Techniques1
* Software Development Estimation: A Quick Guide - ProjectManager2
* Five keys to estimating - Project Management Institute3

Agile and incremental delivery focuses on delivering value early and frequently. Since the prototype is being built incrementally, the project is likely following an adaptive or hybrid lifecycle. In such cases, delivering business value as soon as possible is the key objective. This enables faster feedback, early realization of benefits, and improved customer satisfaction.
According to the PMBOK Guide - Seventh Edition (Value Delivery System), one of the key goals of a project is to maximize value delivery. The Agile Practice Guide emphasizes iterative delivery and prioritizing features with the highest business value early in development.
Option A (PDCA) is a general continuous improvement method, not specific to value delivery prioritization.
Option C (Kanban) is a scheduling method that may help visualize flow but is not the primary priority here.
Option D (informing the sponsor of the schedule) is good practice but not the highest priority in this context.
References:
PMBOK Guide - Seventh Edition, Value Delivery System
Agile Practice Guide, Section 3.2: Delivering Frequently and Iteratively

Comprehensive and Detailed Explanation:
When team members are unclear about project completion, the project manager should first review the schedule and deliverables. This helps understand the remaining scope and clarify the path to closure.
Reaffirming the plan aligns the team and corrects confusion about transitioning to operations.
Option A gathers feedback but doesn't clarify the plan.
Option C skips necessary project analysis.
Option D changes methodology without reason.
References:
PMBOK Guide - Seventh Edition, Planning and Delivery Domains
PMI Guidelines on Project Closure and Lifecycle Completion
##############################################

According to the PMBOK Guide, 7th edition, section 2.2.1, organizational process assets (OPAs) are the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization. OPAs include any artifact, practice, or knowledge from any or all of the organizations involved in the project that can be used to execute or govern the project. OPAs also include historical information and lessons learned from previous projects. Therefore, the project manager's notes should be stored as OPAs, so that they can be accessed and utilized by other project managers in the future. OPAs are inputs to many project management processes and outputs of some project management processes. References:
* PMBOK Guide, 7th edition, section 2.2.1, page 37-38
* PMBOK Guide, 7th edition
* PMP Exam Content Outline