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"
-

According to the PMBOK Guide, 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 includes information such as the communication requirements, methods, formats, frequency, roles, and responsibilities of the project stakeholders. When a company's new communication system introduces online dashboard reporting, this is a change that affects the communication methods and formats of the project. Therefore, the project manager should update the communications management plan to reflect this change and ensure that the project communications are aligned with the new system and the stakeholder expectations. Updating the communications management plan will also help the project manager to identify and address any potential risks, issues, or challenges that may arise from the change, such as compatibility, security, or training needs. References: PMBOK Guide, Tools for managing projects : digital dashboards to report performance

Agile project delivery is adopted primarily because it allows for early and incremental delivery of value, which is prioritized based on customer and project needs. This approach enables teams to deliver parts of the project as they are completed, allowing for early benefits and the ability to adapt to changes quickly. Agile emphasizes customer collaboration and responsive planning which is more conducive to delivering a product that better meets user needs and has a higher value early in the process123.
References:
* Agile project management and the PMBOKguide1.
* Agile and PMBOKguide project management techniques2.
* Tips for Adopting Agile Approaches3.

In project communications, messages must be tailored to the stakeholder's role, interest, and level of influence. The Communications Management Plan defines how information is formatted, delivered, and customized. It is standard practice to segment communication content by stakeholder groups to ensure relevance and engagement.
The PMBOK Guide - Seventh Edition emphasizes tailoring communications "based on stakeholder needs and preferences" and aligning the format and detail with their interests. This ensures effective communication and reduces the risk of disengagement or misinterpretation.
Option A is close but implies arbitrary compliance, not intentional tailoring.
Option B describes an inefficient and impractical practice.
Option C describes organizational norms, not best practices per PMI standards.
References:
PMBOK Guide - Seventh Edition, Communication Performance Domain
PMBOK Guide - Sixth Edition, Section 10.2 "Manage Communications"

In Agile, backlog refinement and prioritization are continuous and collaborative activities. If user stories (especially those fixing demo issues) are left unprioritized, the team and product owner must work together to reassess and reorder the backlog for upcoming sprints.
Option B is the most proactive, aligned with Agile practices, and focused on collaboration.
Option A may help scope understanding but doesn't address prioritization.
Option C misuses "spikes" (intended for research, not unplanned work).
Option D is reactive and extends scope rather than adjusting priorities.
References:
Agile Practice Guide, Chapter 5 - Backlog Refinement and Iteration Planning PMBOK Guide - Seventh Edition, Delivery Performance Domain
##############################################