The situation described in the question is a common occurrence in project management known as scope creep, where additional features or functions are added to the project without changes to time, budget, or resources.
This can lead to projects overrunning their budget and schedule, and can reduce the value delivered to the client. The Project Management Professional (PMP) guidelines emphasize the importance of managing scope creep. In this case, the project manager should refocus the team on the agreed-upon features to ensure that the project delivers the expected value within the agreed time and budget. References: Project Management Professional (PMP) Certification Handbook from www.pmi.org and A Guide to the Project Management Body of Knowledge (PMBOK Guide) from www.pmi.org.

In an agile software development project, especially one with many unknowns, iterative scheduling is the most appropriate method. This approach allows the project to be broken down into smaller sections, often referred to as sprints, which can be planned, executed, and reviewed in a cyclical manner. It accommodates changes and unknowns by allowing for adjustments after each iteration, ensuring that the project remains flexible and responsive to the client's needs123. References:
* "An Agile Approach to Scheduling" article1
* Atlassian's guide on "Creating Project Schedules: Steps & Techniques"2
* "Agile Project Scheduling and Monitoring" from Open Colleges3

The best way to improve deliverable quality is to embed continuous feedback and inspection throughout the process, rather than relying solely on late-phase inspections. By breaking the project into iterations (an Agile principle), the team can apply automated testing early and often, while also using retrospectives (quality improvement sessions) to continuously improve.
According to the Agile Practice Guide (Chapters 3 and 5), Agile frameworks encourage frequent quality checks, test automation, and continuous integration to reduce defect rates. This approach aligns with "Build Quality In," a principle emphasized in both the PMBOK Guide (Seventh Edition) and lean/agile practices.
Option A addresses training but lacks ongoing quality integration.
Option B is reactive and too late in the process.
Option C is better than B, but quality auditing alone is not sufficient.
References:
PMBOK Guide - Seventh Edition, Quality Performance Domain
Agile Practice Guide, Chapter 5: "Agile Product Quality Management"
-

In the context of a product development project, planning for continuous validation is crucial to ensure that the product meets the required quality standards and to prevent major issues that could lead to rework and delays. Continuous validation involves regular checks and assessments throughout the product development lifecycle, which helps in identifying and addressing quality issues early on. This proactive approach aligns with the PMBOK guide's emphasis on quality management and the iterative nature of agile methodologies, which advocate for ongoing evaluation and adaptation.
PMBOK Guide - Sixth Edition
The PMI Guide to Business Analysis
Best practices in resolving quality issues in product development as outlined in various professional resources.

In the Scrum framework, the traditional project schedule is replaced by a combination of the sprint plan and the product roadmap. The sprint plan outlines the work to be performed during the sprint, which typically lasts 2-4 weeks, and includes the sprint goal, the set of product backlog items selected for the sprint, plus the plan for delivering the product increment and realizing the sprint goal. The product roadmap provides a longer-term view of where the product is headed and the milestones along the way. It is a strategic document that outlines the vision, direction, priorities, and progress of the product over time.
The information is aligned with the Scrum Guide and the principles outlined in the Project Management Institute's (PMI) Agile Practice Guide, which complements the PMBOK Guide and other PMI standards.