PMP Reviews Questions

According to the PMBOK® Guide, quality management is the process of ensuring that the project meets the needs and expectations of the stakeholders1. Quality management involves planning, managing, and controlling quality activities throughout the project life cycle1. A predictive approach to quality management is based on the assumption that the project requirements and scope are well-defined and stable, and that the quality standards and criteria are established upfront1. A predictive approach relies on sequential phases, such as initiation, planning, execution, monitoring and controlling, and closing, and evaluates the quality of the products at the end of each phase1. However, a predictive approach may not be suitable for projects that face high uncertainty, complexity, or change, as it may result in rework, delays, or customer dissatisfaction12.

A hybrid approach to quality management is a combination of predictive and adaptive methods, such as agile, that allows the project manager to tailor the quality practices to the specific needs and characteristics of the project23. A hybrid approach enables the project manager to balance the trade-offs between predictability and flexibility, and to deliver value to the customer in an iterative and incremental manner23. A hybrid approach requires the project manager to understand the context and interdependencies of the process from the team members and then define improvements23. By doing so, the project manager can leverage the expertise and feedback of the team members, who are closest to the work and the customer, and identify the best ways to enhance the quality of the products and the process23. The project manager can use various techniques to understand and improve the process, such as process mapping, value stream mapping, root cause analysis, and continuous improvement123. References:

• 1: PMBOK® Guide – 4th Edition, Chapter 8: Quality Management
• 2: A Guide to Hybrid Project Management: Blending Agile and Waterfall
• 3: How to Do Hybrid Right

Contingency control in the project and rebaseline is a process that involves adjusting the project baseline to account for the impact of unforeseen risks. This allows the project manager to update the project scope, schedule, and cost baselines to reflect the current situation and avoid further deviations. Integrated change control in the project is a process that ensures that any changes to the project are reviewed, approved, and communicated to all stakeholders. This helps the project manager to manage the expectations of the project sponsors, customers, and team members, and to maintain the alignment of the project objectives with the business needs. References: (Professional in Business Analysis Reference Materials source and documents)

• PMBOK Guide, Seventh Edition, Section 4.5.3, “Contingency Control”
• PMBOK Guide, Seventh Edition, Section 4.6.3, “Integrated Change Control”

The project manager should analyze the reason for the gap in understanding with both sides and negotiate a solution, as this is a strategy for managing stakeholder dissatisfaction in agile projects. According to the Agile Alliance, one of the principles of agile software development is to satisfy the customer through early and continuous delivery of valuable software. However, sometimes the customer or stakeholder may not be satisfied with the product, even if it meets the acceptance criteria and is approved by them. This may happen due to various reasons, such as unclear or changing requirements, miscommunication, unrealistic expectations, or lack of feedback. The project manager should identify the root cause of the dissatisfaction and try to resolve it through dialogue and collaboration. The project manager should also use agile techniques, such as backlog refinement, user stories, sprint reviews, and retrospectives, to ensure that the product delivers value to the stakeholder and aligns with their vision and goals1.

The other options, asking the project team to perform the modifications, asking the stakeholder to submit a change request, or explaining to the stakeholder that the project can be closed, are not the best ways to manage stakeholder dissatisfaction in agile projects. Asking the project team to perform the modifications may not address the underlying issue of the dissatisfaction and may also introduce new risks or defects to the product. Asking the stakeholder to submit a change request may not be feasible or appropriate in an agile environment, where changes are expected and welcomed, as long as they add value to the product and do not compromise the quality or scope2. Explaining to the stakeholder that the project can be closed may not satisfy the stakeholder or improve the relationship, as it may imply that the project manager is not willing to listen to their feedback or concerns.

References: 3 A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 13 2 Agile Practice Guide, Chapter 2 1 Effective Ways for Stakeholder Management in Agile - Premier Agile 4 How to Explain Agile to Your Stakeholders | Agile Alliance

A hybrid approach combines predictive and adaptive elements to deliver projects. In a hybrid approach, the project manager can break down the requirements into smaller and manageable chunks, and prioritize them based on their value and risk. This way, the project manager can deliver the most important and uncertain requirements first, and get feedback from the stakeholders and customers. This feedback can help clarify the unclear requirements and improve the quality of the project deliverables. The project manager can also adjust the delivery plan based on the changing requirements and environment. A hybrid approach is suitable for projects that have some degree of uncertainty and complexity, and that need to respond to changing customer needs and expectations. References:

• A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Seventh Edition, Chapter 2: Value Delivery System, Section 2.3: Delivery Approaches, pp. 31-35
• Project Management Professional (PMP) Handbook, Section 2.2: PMP Exam Content Outline, Domain II: Process, Task 1: Plan and manage project scope, pp. 14-15
• Hybrid Project Management: What It Is & How to Implement It, by Simplilearn, published on February 10, 2020