PMP Practice Questions

This scenario tests the project manager's emotional intelligence and application of servant leadership principles. The primary responsibility of a project manager is to support the team. Noticing a deviation in performance coupled with information about a personal issue requires a supportive, not punitive, response. The most appropriate first step is to approach the team member with empathy, seek to understand the situation in a private and respectful manner, and offer support. This builds trust, addresses the root cause of the performance issue, and fosters a psychologically safe environment, which is crucial for team cohesion and long-term performance.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition.

Section 3.4

Models

Methods

and Artifacts - Leadership: This section discusses various leadership styles

including servant leadership. It states

"Servant leaders focus on understanding and addressing the needs and development of team members in order to enable the highest possible team performance." Option D is a direct application of this principle.

2. Project Management Institute. (2017). Agile Practice Guide.

Section 5.2.2

Servant Leadership: This section emphasizes that servant leaders "put the needs of others first" and "create an environment of trust." Understanding a team member's issue and offering support is a core tenet of creating this environment.

3. Clarke

N. (2010). Emotional intelligence and its relationship to transformational leadership and key project manager competences. Project Management Journal

41(2)

5-20.

Page 10: This study empirically links emotional intelligence (EI) to project manager competence. The competency of "empathy" (a key component of EI) is critical. The article states

"EI is significantly related to project manager competencies for leadership..." Approaching the team member with understanding (Option D) is a direct application of empathy and effective leadership. (DOI: https://doi.org/10.1002/pmj.20162)

The identified root cause of the delay on the critical path is the developer's lack of understanding due to ineffective communication within the geographically distributed team. The project manager's primary role in such a situation is to act as a facilitator and servant leader. By facilitating direct communication between the developer and the off-site team, the project manager addresses the problem's source directly. This approach empowers the team member, resolves the immediate blocker, and improves the overall communication process, which is critical for the success of virtual teams. This action is a constructive, immediate, and collaborative solution.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition.

Section 2.2

Team Performance Domain: This domain emphasizes that "project teams are more effective when there is a culture of respect and trust where team members can communicate openly." The project manager's role includes fostering this environment and removing impediments

such as communication barriers. Facilitating clarification is a direct application of this principle.

Section 2.2.3

Leadership: Discusses servant leadership

where the focus is on "understanding and addressing the needs and development of team members in order to enable the highest possible team performance." Facilitating communication is a key servant leadership activity.

2. Project Management Institute. (2017). Agile Practice Guide.

Section 5.2.4

Communication for Distributed Teams (p. 53): This section highlights the challenges of distributed teams and states

"The project manager may need to take a more active role in facilitating communication and collaboration among the team members." This directly supports the action of facilitating communication to resolve the issue.

3. Hertel

G.

Geister

S.

& Konradt

U. (2005). Managing virtual teams: A review of current empirical research. Human Resource Management Review

15(1)

69-95.

This academic review emphasizes that a key success factor for virtual teams is proactive communication and coordination support from management. The research indicates that managers must actively "facilitate communication processes" to overcome the disadvantages of geographical distance and ensure shared understanding. (p. 81). https://doi.org/10.1016/j.hrmr.2005.01.002

According to the Tuckman ladder model of team development, the Forming stage is the initial phase where team members are introduced. In this stage, individuals are often uncertain about their roles, are not yet a cohesive unit, and are highly dependent on the leader for direction and guidance. For a team comprised of new hires, the project manager must invest the most significant effort in this stage to establish clear objectives, define roles and responsibilities, set expectations, and build a foundation of trust. This directive leadership style is crucial for integrating the team and is more intensive than in later stages.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Project Management Institute

Inc. See Section 2.4

"Project Team Development

" p. 44. The guide states

"The team leader needs to provide clear direction and purpose during this [Forming] phase

" highlighting the leader's critical and effort-intensive role at the outset.

2. Tuckman

B. W. (1965). Developmental sequence in small groups. Psychological Bulletin

63(6)

384–399. https://doi.org/10.1037/h0022100. The original paper describes the Forming stage as a period of "testing and dependence" where the group relies on the leader to provide structure and direction

implying a high level of required leadership effort.

3. Project Management Institute. (2021). The Standard for Project Management. Project Management Institute

Inc. See Section 3.4

"Principle: Foster a Collaborative Project Team Environment

" pp. 39-42. The activities described for creating a collaborative culture

such as establishing ground rules and building trust

are most intensive for the project manager during the initial Forming stage with a new team.

The Scrum Master is explicitly defined as a Servant Leader whose primary role is to coach the team, remove impediments, and facilitate processes, making "Servant Leadership" the direct training match. The Product Owner is responsible for backlog management, value maximization, and eliciting requirements, which are core Business Analysis activities. The Development Team must also attend Business Analysis in Practice because, in Agile, the team actively collaborates with the Product Owner during backlog refinement to analyze user stories, clarify requirements, and ensure the technical solution aligns with business value.

Scrum Guide (2020), Section: The Scrum Master. "The Scrum Master is a true leader who serves the Scrum Team and the larger organization." (Explicitly links Scrum Master to Servant Leadership).

PMI Agile Practice Guide (2017), Section 4.3.2 Team Facilitator. Describes the Scrum Master/Team Facilitator role as a servant leader who focuses on coaching and organizational health.

PMI Agile Practice Guide (2017), Section 5.2.3 Backlog Refinement. States that the team and product owner collaborate to refine the backlog, verifying the Development Team's involvement in business analysis work.

IIBA Agile Extension to the BABOK® Guide, Chapter 2 Agile Business Analysis. Defines agile business analysis as a collaborative process shared by the Product Owner and the Delivery Team (Development Team), distinct from the facilitation role of the Scrum Master.

A change from an agile to a predictive delivery approach represents a fundamental shift in how the project will be planned, executed, monitored, and controlled. The project management plan is the central document that defines this entire framework. Therefore, the project manager's most logical and comprehensive next step is to develop a new project management plan that aligns with the newly mandated predictive methodology. This plan will integrate all subsidiary plans (such as risk, communication, scope, and schedule) and provide a new baseline for project execution and control, addressing the core of the change.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition.

Project Performance Domain: Planning (Section 2.4

p. 69): "The project management plan is the comprehensive document that describes how the project will be executed

monitored and controlled

and closed." A change in the delivery approach (e.g.

from agile to predictive) fundamentally alters this "how

" thus requiring the plan to be redefined.

Tailoring (Section 4.3

p. 133): The guide states that tailoring involves the selection of the appropriate project management processes

inputs

tools

techniques

outputs

and life cycle phases. A mandated switch from agile to predictive is a significant tailoring decision that necessitates a new or heavily revised project management plan.

2. Project Management Institute. (2017). Agile Practice Guide.

Chapter 5

Implementing Agile: Creating an Agile Environment (Section 5.2

p. 50): This section discusses tailoring the approach for the project. A decision to move from an agile approach like Scrum to a predictive one is a foundational change that would require a complete replanning effort

encapsulated within a new project management plan.

The project manager's first responsibility upon learning of a significant change is to understand its full scope and impact. The vendor's move to the cloud introduces new security standards, which are currently unknown to the project team. Therefore, the most logical and immediate step is to engage the relevant subject matter experts—the internal security team—to comprehend these new requirements. This information is a prerequisite for any further action, such as assessing impacts on the project, creating a change request, or planning risk responses. This aligns with the principle of proactive stakeholder engagement to clarify requirements.

A. Initiating a change request is premature. A comprehensive change request requires a detailed understanding of the impact on scope, schedule, and budget, which is not yet known.

B. Researching alternative solutions is a potential risk response, but not the first step. The immediate priority is to understand and assess the impact of the current vendor's change.

C. Asking for training is presumptive. The need for and specific content of any training can only be determined after the new security standards are fully understood.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Newtown Square

PA: Project Management Institute

Inc.

Section 2.8

Stakeholder Performance Domain (p. 69): This domain emphasizes that "Effective stakeholder engagement includes implementing strategies and actions to promote productive involvement of stakeholders." The first step in this scenario is to engage the security team to understand their requirements.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Newtown Square

PA: Project Management Institute

Inc.

Section 4.6

Perform Integrated Change Control (p. 113): This process includes assessing the impact of changes. Before a formal change request can be properly created and evaluated

the project manager must facilitate an assessment

which starts with gathering information from relevant experts.

3. Kerzner

H. (2017). Project Management: A Systems Approach to Planning

Scheduling

and Controlling. Wiley.

Chapter 15

Change Control: This chapter details that a critical early step in any change management process is the analysis and evaluation of the proposed change's impact

which necessitates gathering information from all affected parties.

The significant disparity in estimates, with some activities at 100 story points, indicates these are likely epics or compound stories, not manageable user stories. In Agile frameworks, work items should be small enough to be completed within a single iteration. The presence of a 100-point item introduces high risk, uncertainty, and makes it impossible to deliver within a typical iteration. The correct project management practice is to guide the team in decomposing these large activities into smaller, independent, and valuable user stories that can be estimated more accurately and completed incrementally.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition.

Section 2.4

DELIVERY PERFORMANCE DOMAIN: This section emphasizes breaking down work. It states

"Large work items are decomposed into smaller pieces that can be completed in shorter time frames. This approach provides for a continuous flow of delivery of value

feedback

and learning." (p. 69). This directly supports the decomposition of the 100-point activity.

2. Project Management Institute. (2017). Agile Practice Guide.

Section 5.2.3

Backlog Refinement: This section explicitly addresses the need to break down large stories. It states

"Large stories need to be broken down into smaller stories until they are small enough to be worked on in an upcoming iteration... This activity of creating and refining stories is called backlog refinement." (p. 50). This aligns perfectly with the action of breaking down the larger activities.

In a long-term, staged project, value is often delivered incrementally. The project manager is responsible for ensuring the project remains aligned with its business objectives. The project business plan, along with the benefits management plan, outlines the expected value and when it should be realized. By periodically evaluating the actual benefits generated at key milestones or stage gates against this plan, the project manager can track benefits realization. This practice confirms the project is delivering the intended monetized value and allows for corrective actions if there are deviations, ensuring the continued viability and success of the investment.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition.

Section 2.7

Measurement Performance Domain: This section emphasizes tracking project objectives and value. It states

"For some projects

the desired outcomes can only be measured after the project has finished. However

where possible

it is helpful to measure outcomes throughout the project. This provides an opportunity to check that the project is on track to deliver the intended outcomes and to take action if it is not." (p. 89). This supports the periodic evaluation described in option D.

2. Project Management Institute. (2021). The Standard for Project Management.

Section 3.5

Focus on Value: "The project team evaluates progress and adapts to maximize the expected value." (p. 31). This principle underpins the need for ongoing evaluation of benefits against the business plan at key points like milestones.

3. Serra

C. E. M.

& Kunc

M. (2015). Benefits Realisation Management and its influence on project success and on the execution of business strategies. International Journal of Project Management

33(1)

53-66.

Section 2.2

Benefits Realisation Management Process: The paper describes benefits realization as a process that includes "measuring and tracking benefits from the start of the investment until the realisation of the last benefit." It highlights that a "benefits review process is a formal process to monitor the realisation of the benefits against the plan

" which directly aligns with evaluating benefits at milestones against the business plan. (p. 56). https://doi.org/10.1016/j.ijproman.2014.03.011

The root cause of the issue was the failure to identify an influential individual who had a valid interest in the project's outcome. The Project Management Body of Knowledge (PMBOK® Guide) emphasizes that stakeholder identification should be performed early and continuously throughout the project lifecycle. By identifying the vice president as a stakeholder, the project manager could have engaged them, understood their concerns, and incorporated their requirements or addressed potential risks proactively. This would have prevented the last-minute surprise that resulted in a release delay. The VP, despite being from a different product line, was affected by or could affect the project, meeting the definition of a stakeholder.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.).

Section 2.7

Stakeholder Performance Domain: This section states

"Effective stakeholder engagement includes implementing strategies and actions to promote productive involvement of stakeholders." It begins with identification. The failure to identify the VP prevented any possibility of effective engagement.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.).

Section 13.1

Identify Stakeholders: This process is defined as "identifying project stakeholders regularly and analyzing and documenting relevant information regarding their interests

involvement

interdependencies

influence

and potential impact on project success." The scenario is a direct example of the negative consequences of failing to perform this process thoroughly at the project's outset.

3. Project Management Institute. (2017). Agile Practice Guide.

Section 5.2.2

Stakeholder Engagement: The guide notes the importance of engaging with a wide range of stakeholders

including "managers

portfolio managers

and organizational leaders

" to ensure their needs and viewpoints are understood and addressed throughout the project. This reinforces the need to look beyond the immediate project team.

The project manager's immediate priority is to understand why there is a deviation from the project plan, specifically why non-critical path items are being prioritized over critical ones. The most effective and collaborative first step is to engage the scrum master to investigate the root cause. This approach fosters communication and problem-solving within the team, which is essential in a hybrid environment. Taking any other action, such as issuing directives or escalating to the sponsor, would be premature without first gathering all the necessary information about the situation. Understanding the "why" will inform the appropriate corrective or preventive action.

A. The critical path, by definition, has zero or negative total float (slack). Attempting to find slack on the critical path to accommodate more work is a fundamentally flawed approach.

B. Instructing the scrum master to suspend a sprint is a highly disruptive, directive action that goes against agile principles of protecting the sprint and empowering the team. This should only be a last resort.

D. Contacting the project sponsor to adjust the baseline is a significant step of escalation. The project manager should first exhaust all options to resolve the issue within the project team.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition.

Section 2.8

Project Work Performance Domain: This domain covers the activities for establishing project processes

managing communications

and ensuring the project team has the knowledge and skills to produce the project’s deliverables. The first step in managing a deviation is effective communication and engagement (p. 99) to understand the situation

which aligns with asking the scrum master for clarification.

2. Project Management Institute. (2017). Agile Practice Guide.

Section 5.2.2

The Project Manager Role in an Agile Environment: In hybrid or agile environments

the project manager often acts as a servant leader

focusing on "understanding and addressing the needs of the team members and stakeholders" (p. 93). Asking for the reason behind the current plan is a key servant leadership behavior

contrasting with the command-and-control approach of option B.

3. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition.

Section 2.4

Planning Performance Domain: This domain involves "the initial

ongoing

and evolving organization and coordination necessary to deliver the project deliverables and outcomes" (p. 53). When a forecast (SPI trending to 0.90) indicates a deviation from the plan

the project manager's role is to investigate and facilitate replanning

not to immediately escalate or dictate solutions.