PMP Exam Questions & Answers

Estimating using historical data from past similar projects (analogous estimating) is a best practice to prevent errors and improve accuracy in cost planning. It helps identify items or tasks that may be overlooked if only current project documentation is used.

According to the PMBOK Guide -- Seventh Edition, past project records and lessons learned are valuable tools for improving cost and scope planning.

Option A is a governance step but doesn't improve estimation accuracy.

Option B addresses when to update but not how to improve the original estimate.

Option C (padding) is not best practice and may not be acceptable in cost-constrained projects.

PMBOK Guide -- Seventh Edition, Cost Performance Domain

PMI Practice Standard for Project Estimating

The project manager should take these two actions to align customer expectations with the current situation of the project. The sprint velocity is a measure of how much work the agile team can complete in a sprint. By reviewing the updated sprint velocity with the customer, the project manager can show the impact of losing two team members on the project schedule and scope. The customer can then adjust their expectations accordingly and provide feedback on the project progress. The prioritized backlog is a list of features and requirements that the customer wants to have in the product. By asking the product owner to review the prioritized backlog with the customer, the project manager can ensure that the most valuable and important features are delivered first. The customer can also reprioritize the backlog items based on their changing needs and preferences. This way, the project manager can deliver early results that meet the customer's satisfaction.

The other options are not the best actions to align customer expectations. Asking the agile team to review and update the quality management plan with the customer is not relevant to the budget reduction or the early results. The quality management plan defines the quality standards, criteria, and methods for the project. It is not a tool for communicating the project status or scope with the customer. Reviewing the impediments log with the customer is not a good practice, as it may expose the internal issues and challenges of the agile team. The impediments log is a record of the obstacles and problems that the agile team faces during the project. It is used by the agile team and the scrum master to identify and resolve the impediments. The customer does not need to know the details of the impediments log, as it may affect their trust and confidence in the project team. Sending a detailed project management plan to the customer is not appropriate for an agile project, as it may imply a fixed and rigid approach to the project. The project management plan is a formal document that describes how the project will be executed, monitored, and controlled. It is not suitable for an agile project, as it does not accommodate the changes and uncertainties that occur during the project. An agile project relies on frequent and informal communication, collaboration, and feedback with the customer, rather than a detailed project management plan.Reference:

PMBOK Guide, 6th Edition, Chapter 6, Section 6.7, ''Control Schedule''

PMBOK Guide, 6th Edition, Chapter 13, Section 13.2, ''Plan Stakeholder Engagement''

PMBOK Guide, 6th Edition, Appendix X3, Section X3.2.2.3, ''Sprint Velocity''

PMBOK Guide, 6th Edition, Appendix X3, Section X3.2.2.4, ''Prioritized Product Backlog''

PMBOK Guide, 6th Edition, Appendix X3, Section X3.2.2.5, ''Impediments Log''

PMP Project Management Professional Exam Study Guide: 2021 Exam Update, 10th Edition, Chapter 12, Section 12.2, ''Agile Project Management''1

The project manager should prioritize removing barriers that impede team performance and autonomy.This action aligns with the principles of agile project management, which emphasize empowering team members to make decisions and take ownership of their work12.By addressing the internal procedures that are hindering progress, the project manager can facilitate a more efficient and autonomous environment, allowing the team to focus on delivering value more effectively3.

PMI's resources on team building and the importance of removing barriers to enhance team performance1.

Literature on expected behaviors for project team performance, which includes empowering team members and promoting autonomy2.

Agile methodologies that advocate for team empowerment and the removal of impediments to improve project outcomes3.

In Agile project management, particularly Scrum, the product owner is responsible for the product backlog, which includes prioritizing features and user stories based on value and necessity. When a new feature is identified that could significantly enhance performance, it should be discussed with the product owner.If the feature is agreed upon, it is then added to the product backlog1. The product backlog is a dynamic list that evolves as new insights and requirements emerge.It is the product owner's role to ensure that the backlog items are well-defined and prioritized for future sprints2.This process ensures that the development team can focus on completing the items in the sprint backlog without overloading the current sprint with new,

To ensure an ERP project delivers its intended outcomes---process improvement, error reduction, and better user services---the project manager must continuously validate that what is being produced still supports the business case. Evaluating deliverables against the business case continuously (B) enables early detection of ''solution drift,'' where features may be delivered but do not drive the targeted benefits. Ongoing evaluation supports benefits realization management: confirm KPIs, test process improvements, validate user journeys, and adjust priorities so the evolving solution stays aligned to value. Reviewing the business case only at the end (C) is too late; by then, changing direction is expensive and value gaps are locked in. Reviewing the business case only when change requests occur (A) is reactive and may miss gradual misalignment that doesn't trigger formal changes. Combining customer feedback with business case review (D) is useful, but the best answer focuses on continuous alignment of deliverables to the business case, using feedback as an input within that ongoing validation loop. Continuous evaluation protects strategic alignment and maximizes ROI.