Free PMP Practice Test Questions and Answers (2026)

The root cause of the rework and delays is a communication failure, specifically "different interpretations of the client's needs." The most direct and appropriate initial action for the project manager is to facilitate communication among all relevant parties to resolve this ambiguity. Setting up a meeting with key stakeholders, which includes the client and development team representatives, directly addresses the problem by creating a forum to clarify requirements, ask questions, and establish a shared understanding, thereby preventing future rework.

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

Section 2.2

Stakeholder Performance Domain: This domain emphasizes the importance of "working with stakeholders to maintain their alignment and to engage them in project decisions." A meeting to clarify needs is a primary activity for stakeholder engagement and alignment. (p. 41)

Section 4.3

Models

Methods

and Artifacts: "Meetings and Events" are listed as a common method used to "communicate

make decisions

and address issues." This situation requires a meeting to address the issue of misinterpretation. (p. 168)

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

Section 5.2.5

Communication and Knowledge Sharing: This section highlights that "Agile approaches favor high-bandwidth communication

" such as face-to-face conversation or video conferencing

to build trust and facilitate quick feedback cycles

which is essential for clarifying requirements with a distributed team. (p. 49)

3. Kerzner

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

Scheduling

and Controlling (12th ed.).

Chapter 11

Planning: This chapter discusses the criticality of defining requirements accurately. It states that "The leading cause of project failure has been poor or inaccurate requirements gathering." The text emphasizes that resolving requirement ambiguity through direct stakeholder communication is a fundamental responsibility of the project manager. (Section 11.5)

In agile projects, the product backlog is a dynamic artifact that reflects the current understanding of business needs and priorities. To address a changing business environment and ensure benefits realization, the project manager should facilitate the continuous reprioritization of the product backlog. This activity, often done between iterations (sprints), involves the product owner and other stakeholders evaluating user stories against current business objectives. This process is the primary mechanism for identifying and adapting to changes, ensuring that the team is always working on the most valuable features, thereby directly supporting the sponsor's concern for benefits realization.

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

Section 4.2.4

The Backlog: "The product backlog is a continuously updated list of all of the work that needs to be done for the product... The product owner is responsible for prioritizing the backlog items based on their business value." This highlights the dynamic and value-driven nature of the backlog.

Section 5.2.4

Backlog Refinement: "As the project proceeds

the team will learn more... The business environment may change... This new information may cause changes to the backlog

such as adding

removing

or reprioritizing items." This section explicitly links backlog refinement to adapting to environmental changes.

2. Serrador

P.

& Pinto

J. K. (2015). Does Agile work? — A quantitative analysis of agile project success. International Journal of Project Management

33(5)

1040–1051.

This study emphasizes that a key success factor in agile is the ability to manage changing requirements and stakeholder expectations. The paper notes

"Agile projects have a process for managing changes to requirements... The product backlog is used to manage all requirements." (p. 1043). Reprioritizing the backlog is the core of this process.

DOI: https://doi.org/10.1016/j.ijproman.2015.01.006

3. Hohl

P.

Klünder

J.

van der Vliet

H.

& Gorschek

T. (2018). A process model for value-based requirements engineering in agile software development. Requirements Engineering

23(4)

423–443.

This paper discusses how value is central to agile development. It states

"The product backlog is the main artifact for managing requirements in agile development... it is continuously prioritized to maximize the value delivered to the customer." (p. 425). This directly supports the idea that backlog reprioritization is the mechanism for ensuring value and benefits realization.

DOI: https://doi.org/10.1007/s00766-017-0279-z

The stakeholder is identified as having high power/influence, making their engagement critical to project success. Dismissing their opinions is a direct path to creating an adversary, increasing conflict, and jeopardizing project objectives. Effective stakeholder management, as outlined by PMI, involves actively listening to, understanding, and addressing the concerns of influential stakeholders to foster support and mitigate risks. Ignoring such a key figure is a significant project management failure and the one action that must be avoided.

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

Section 13.3

Manage Stakeholder Engagement: This process is defined as "communicating and working with stakeholders to meet their needs and expectations

address issues

and foster appropriate stakeholder involvement." Dismissing opinions is the antithesis of this process. The key benefit is to "increase support and minimize resistance

" which dismissing opinions would actively undermine.

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

Section 2.3

Stakeholder Performance Domain: This domain emphasizes that "Effective stakeholder engagement involves fostering positive relationships and creating an environment where stakeholders can contribute positively." Dismissing opinions would damage relationships and create a negative environment.

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

Section 5.2.3

Stakeholder Engagement: This section highlights the importance of active and frequent stakeholder engagement for feedback and collaboration. Dismissing opinions violates the core agile principle of collaboration with stakeholders.

The team members are demonstrating an accommodative style of conflict resolution. This approach, also known as smoothing, involves yielding to the other party's point of view, even at the expense of one's own concerns. The members are prioritizing group harmony and avoiding contention by agreeing with proposals they internally oppose. This is a lose-win strategy where they concede their position to satisfy others, which is the defining characteristic of the accommodative style.

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

Data Analysis

describes the "Smooth/Accommodate" technique as "Emphasizing areas of agreement rather than areas of difference; conceding one’s position to the needs of others to maintain harmony and relationships."

2. Thomas

K. W. (1992). Conflict and conflict management: Reflections and update. Journal of Organizational Behavior

13(3)

265–274. This foundational paper discusses the two-dimensional taxonomy of conflict-handling modes (assertiveness and cooperativeness)

defining accommodating as low in assertiveness and high in cooperativeness. (https://doi.org/10.1002/job.4030130307)

The project manager has been assigned a specific task: to enforce a unified direction and control framework. The most immediate and logical first action is to understand the specific needs, expectations, and constraints for this framework. This is achieved by collecting requirements from the key stakeholders who initiated or are most impacted by this directive. This step is foundational as it defines the scope and objectives of the initiative, which will then guide the development of plans, documentation, and broader engagement strategies.

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

Section 5.2

Collect Requirements: This process is defined as "determining

documenting

and managing stakeholder needs and requirements to meet project objectives." (p. 138). Before the PM can enforce a framework

they must first determine the requirements for it. This precedes detailed planning or documentation.

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

Section 2.7

Stakeholders: This section emphasizes that project success is dependent on effective stakeholder engagement

which begins with understanding their needs and expectations. The first step in addressing a stakeholder-driven initiative is to clarify those needs (requirements).

3. Kerzner

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

Scheduling

and Controlling (12th ed.). Wiley.

Chapter 11

Planning: Kerzner emphasizes that effective project planning begins with a clear definition of the objectives and requirements. "The first step in planning is to understand the requirements of the project... Without a clear definition of the requirements

the project is destined for failure." (p. 365). This principle applies directly to the sub-initiative of creating a control framework.

The most appropriate next step is to proactively engage the new, influential stakeholder. A one-on-one interview allows the project manager to understand the senior manager's perspective, expectations, and experience. It also provides an opportunity to brief them on the project's current objectives, scope, and plan. This alignment is crucial before the kick-off meeting to prevent disruptions, build a positive working relationship, and ensure the new member can contribute constructively from the start. This action exemplifies effective stakeholder engagement, a key responsibility of the project manager.

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

Section 2.3

Stakeholder Performance Domain (p. 65-75): This domain emphasizes the importance of "proactively engaging stakeholders to foster positive relationships and satisfaction." A one-on-one meeting is a primary method for understanding stakeholder interests and expectations (p. 66) and fostering effective engagement (p. 69).

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

Section 13.3

Manage Stakeholder Engagement (p. 523): This process focuses on "communicating and working with stakeholders to meet their needs and expectations." The tools and techniques include "Communication skills" and "Interpersonal and team skills

" for which a direct interview is a prime example.

3. Pinto

J. K. (2019). Project Management: Achieving Competitive Advantage (5th ed.). Pearson.

Chapter 3

Project Selection and Portfolio Management: This chapter often discusses the "political dimension" of projects. Engaging a new senior leader on the steering committee is a critical political and relationship-building activity that should be handled proactively and personally to secure their support and align their vision with the project's goals.

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.

The most immediate and critical action is to engage the new key stakeholder. The project executive is a powerful stakeholder whose support is essential, especially for an upcoming milestone approval. The project manager's first responsibility is to establish communication and bring the new executive up to speed on the project's status, objectives, progress, and the importance of the upcoming decision. This proactive communication is fundamental to the Stakeholder Engagement process and ensures the new leader can make an informed decision, thereby mitigating potential risks to the project's progress.

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

Inc.

Reference: Section 2.5

Stakeholder Performance Domain

p. 67. This section emphasizes that effective project management involves implementing strategies and actions to promote the productive involvement of stakeholders. Briefing a new executive is a primary action for engagement.

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

Inc.

Reference: Section 13.3

Manage Stakeholder Engagement

p. 523. This process focuses on communicating and working with stakeholders to meet their needs and foster appropriate involvement. The arrival of a new executive immediately triggers the need for this process.

3. Aaltonen

K. (2011). The role of the project manager in stakeholder management. Project Management Journal

42(1)

1-24.

Reference: This publication highlights the project manager's proactive role in managing stakeholder relationships. When a key stakeholder changes

the immediate priority is to establish communication to ensure alignment and continued support for project objectives. (DOI: https://doi.org/10.1177/875697281104200105)

Iteration Planning: The primary output of this event is the Iteration Goal and the Iteration Backlog. The team determines what can be delivered and defines the goal for this iteration.

Daily Meeting (Daily Stand-up): This event is for synchronization and planning the next 24 hours. It focuses on impediments and progress, ensuring the smooth development flow toward the goal.

Iteration Review: The purpose is to inspect the increment. The Product Owner or team discusses which backlog items [were] completed or not to stakeholders to adapt the future backlog.

Iteration Retrospective: The team inspects its own processes to improve effectiveness. A common technique used here is identifying continue, stop, or start actions to implement in the next iteration.

Schwaber, K., & Sutherland, J. (2020). The Scrum Guide: The Definitive Guide to Scrum: The Rules of the Game.

Section: Sprint Planning ("The Scrum Team ... defines a Sprint Goal that communicates why the Sprint is valuable to stakeholders.")

Section: Sprint Review ("The Product Owner explains what Product Backlog items have been 'Done' and what has not been 'Done'.")

Scaled Agile, Inc. Scaled Agile Framework (SAFe) 6.0.

Topic: Iteration Retrospective ("...Quantitative and qualitative insights... What went well? What didn't? What can we do better next time? [Start, Stop, Continue]")

Topic: Daily Stand-up ("The DSU is key to team synchronization... [it] makes visible any problems or impediments to the flow of work.")

Project Management Institute (PMI). Agile Practice Guide.

Chapter 5: Implementing Agile: Delivering in an Agile Environment (Discusses the "Start, Stop, Continue" format for Retrospectives and the flow-based nature of daily stand-ups).

The transition of a project to an operational state occurs during the Closing Process Group. A critical activity in this phase is to verify that all planned work is complete and all deliverables have been formally accepted. The Work Breakdown Structure (WBS) is a key component of the scope baseline, which defines the total scope of the project. Systematically reviewing the WBS with the project team is the most effective method to ensure that every deliverable has been completed as planned, thereby confirming the project's readiness for handover to operations and subsequent closure.

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

Section 4.7

Close Project or Phase: This process involves finalizing all activities and formally completing the project or phase. A key activity is to "confirm that the defined project scope is complete." The scope baseline

which includes the WBS

is a primary input to this process

used to verify completion. (p. 123).

Section 5.5

Validate Scope: This process is about formalizing the acceptance of completed project deliverables. The WBS

as part of the scope baseline

is used to confirm that the work is finished and meets stakeholder requirements before final acceptance. (p. 163).

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

Section 2.4

Delivery Performance Domain: This domain addresses the activities and functions associated with delivering the scope and quality that the project was undertaken to achieve. Verifying that "the project deliverables have been completed and that the project has achieved its intended business value" is a key check before closure. (p. 69).

Section 4.3

Artifacts: The Work Breakdown Structure is described as a "hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables." It serves as the definitive record of what must be delivered. (p. 188).

3. Kerzner

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

Scheduling

and Controlling (12th ed.). John Wiley & Sons.

Chapter 19

Project Termination: This chapter details the closure process

emphasizing the need for a final report that confirms "all deliverables have been made to the satisfaction of the client." The verification process relies on checking against the initial project plan and scope

for which the WBS is the foundational document. (pp. 618-620).

The resource management plan is the primary document that outlines how project resources, including team members, are defined, acquired, managed, and controlled. A key component of this plan is the "Roles and Responsibilities" section, which explicitly details the authority, duties, and decision-making power assigned to each role on the project team. This is often documented using tools like a Responsibility Assignment Matrix (RAM), such as a RACI (Responsible, Accountable, Consulted, Informed) chart, which provides clear guidance on levels of authority.

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

Resource Management Plan. Newtown Square

PA: Project Management Institute. This section explicitly states that the resource management plan includes "Roles and responsibilities

" which covers "Authority: The level of authority that a project team member has

such as the authority to make decisions

approve changes

or sign off on acceptances." (p. 318).

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

Team Performance Domain. Newtown Square

PA: Project Management Institute. This domain emphasizes the importance of establishing "a clear understanding of roles and responsibilities" for team effectiveness. The resource management plan is the formal artifact where this is documented.

3. Kerzner

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

Scheduling

and Controlling (12th ed.). John Wiley & Sons. Chapter 5

"Organizing and Staffing the Project Office and Team

" discusses the Responsibility Assignment Matrix (RAM) as a crucial tool within resource planning to define roles

responsibilities

and authority.

The question states the project manager is in the process of building the first baseline. This means the project management plan and its components (scope, schedule, cost baselines) are not yet formally approved. In this pre-baseline phase, the plan is considered a draft and is subject to refinement through progressive elaboration. Therefore, the formal change control process is not yet in effect. The project manager's immediate and most appropriate action is to analyze the request to understand its potential impact on the project's objectives, constraints, and overall plan. This analysis is a crucial part of the planning process itself, helping to finalize a realistic and comprehensive baseline.

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

PA: Project Management Institute

Inc.

Page 89

Section 4.2.3.1: "Before the project management plan is baselined

changes can be made as needed without following a formal process. Once it is baselined

changes have to be processed through the Perform Integrated Change Control process." This directly supports that a formal process (like CCB approval) is not yet required.

Page 113

Section 4.6: The introduction to "Perform Integrated Change Control" describes it as the process for reviewing change requests after the project management plan has been baselined.

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

PA: Project Management Institute

Inc.

Page 53

Section 2.5

Planning Performance Domain: This domain is described as an "evolving" activity. A request received during this phase is part of the iterative work to "produce a holistic approach to delivering the project outcomes." Analyzing the request is a fundamental part of this evolving planning effort.

3. Kerzner

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

Scheduling

and Controlling (12th ed.). John Wiley & Sons.

Chapter 11

Planning: This chapter details that the planning phase is iterative. Before baselines are set

project plans are dynamic. The project manager's role is to incorporate stakeholder input and analyze impacts to develop the most viable plan for approval. This aligns with analyzing the request as part of the planning cycle.

Policy Compliance refers to adhering to internal organizational mandates, such as "company standards." Standards Compliance ensures deliverables meet established external technical benchmarks, directly addressing the "quality of the industry standard." Governmental Compliance specifically addresses adherence to statutory "laws" (federal or state), such as health and safety acts. Regulatory Compliance involves following specific codes and rules enforced by regulatory bodies; "industry codes" (like building or electrical codes) are the primary example of this category.

Project Management Institute (PMI). (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Newtown Square, PA: Author. (See Section 2.3.2 regarding the external environment, distinct regulations, and standards).

Project Management Institute (PMI). (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Newtown Square, PA: Author. (See Section 2.1.1.2: Enterprise Environmental Factors - differentiating between governmental standards, industry standards, and internal policies).

Heldman, K. (2018). PMP: Project Management Professional Exam Study Guide. 9th Edition. Sybex. (Chapter 1 details the differences between Regulations [Mandatory] and Standards [Voluntary/Quality guidelines]).

When a significant change, such as a scope expansion, is requested, the project manager's primary responsibility is to perform an impact analysis. This analysis must cover all project constraints, including resources. The scenario identifies a critical resource risk: a lack of leadership experience to manage the expanded work. The correct professional action is to communicate this risk and its potential consequences to the sponsor and other key stakeholders. Proposing a solution, such as hiring experienced members, is a proactive approach that allows for an informed decision on how to proceed with the change request, aligning with the Perform Integrated Change Control process.

B. Declining the request outright is inappropriate. The project manager should analyze and present options, not unilaterally reject a potentially beneficial change requested by the sponsor.

C. Implementing the scope expansion without securing the necessary resources introduces unmitigated risk, which is an irresponsible action that jeopardizes the project's success.

D. While recognizing the team and planning for their development are positive actions, they do not address the immediate skill gap and risk associated with the scope expansion.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Section 4.6

Perform Integrated Change Control

p. 113. The text emphasizes that the process includes "assessing the impact of the change" on project objectives and constraints.

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

Project Work Performance Domain

subsection 2.8.3

Managing Project Changes. This section details that managing change involves evaluating impacts and presenting the "options and recommendations" to the relevant stakeholders for a decision.

3. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Section 9.3

Acquire Resources

p. 328. This process focuses on obtaining the necessary team members. A scope change that reveals a competency gap would necessitate activities from this process.

In managing virtual Agile teams, communication tools must be matched to the task's complexity and requirements (Media Richness Theory). Negotiation involves resolving conflicts and reaching agreements, requiring high-bandwidth communication to capture non-verbal cues; video conferencing provides the necessary face-to-face interaction. Routine information (status updates, announcements) is effectively handled via online bulletin boards (information radiators), allowing members to pull information as needed without synchronous interruption. Project deliverables (code, documentation) require strict configuration management and history tracking, which is the primary function of a version control system. Finally, general team discussion and informal collaboration are best facilitated by chat rooms, which offer a balance of immediacy and persistence for ongoing dialogue.

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

Section 10.1.2.3 (Communication Technology): Discusses how the urgency of the need for information and the sensitivity of the information determine the tool choice (e.g., video for sensitive/complex interactions).

Section 10.1.2.5 (Communication Methods): Defines "Pull communication" (e.g., web portals, bulletin boards) for large volumes of information or very large audiences, suitable for routine info.

Project Management Institute (PMI) & Agile Alliance. (2017). Agile Practice Guide. Newtown Square, PA: Project Management Institute.

Section 4.3.2 (Team Practices - Distributed Teams): Page 46. Discusses the use of "fishbowl windows" (video conferencing) to bridge the gap in distributed teams, essential for complex interactions like negotiation.

Daft, R. L., & Lengel, R. H. (1986). Organizational Information Requirements, Media Richness and Structural Design. Management Science, 32(5), 554–571. doi.org/10.1287/mnsc.32.5.554

Foundational academic source for Media Richness Theory, which dictates that ambiguous tasks (Negotiation) require rich media (Video), while standard tasks (Routine info) use lean media (Boards/Documents).

The core issue is a breakdown in communication and transparency, which a formal daily report is failing to address. A physical task board (like a Kanban or Scrum board) serves as an "information radiator." It makes the workflow, progress, dependencies, and blockers highly visible to the entire team and the product owner in real-time. This visual management tool fosters collaboration, provides a focal point for daily discussions, and creates a shared understanding of the team's work and challenges. It directly addresses the dissatisfaction by replacing an ineffective formal report with a transparent, collaborative, and continuously updated tool.

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

Section 4.2.5

Artifacts: Discusses visual controls

stating

"Visual controls are artifacts that post information in a highly visible physical location to convey a message

share information

or prompt a decision or action... Examples include story maps

Kanban boards

and burndown/burnup charts." This supports using a task board as a key artifact for communication.

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

Section 5.2.3

Information Radiators: This section explicitly describes the value of tools like task boards. It states

"To share information with the team and stakeholders

agile teams use information radiators... The goal is to have simple

high-visibility displays of key information... Examples include task boards..." (p. 52). This directly aligns with using a task board to solve the communication problem.

3. Sutherland

J.

& Schwaber

K. (2020). The Scrum Guide. Scrum.org.

Section on Scrum Artifacts

The Sprint Backlog: The guide describes the Sprint Backlog as a "highly visible

real-time picture of the work that the Developers plan to accomplish." This emphasizes the principle of making work visible to enhance transparency

which is the goal of a task board.

The project manager's immediate responsibility is to manage team dynamics and resolve conflict. The team member's disruptive behavior is a symptom of an underlying problem. The most effective and professional first step is to engage with the individual to understand the source of their negativity and disruption. This approach, rooted in root cause analysis, allows the project manager to determine if the issue stems from a misunderstanding, a valid unaddressed risk, or a personal issue. Only after identifying the cause can an appropriate resolution be implemented. This aligns with the conflict management principle of confronting the problem, not the person.

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.3

Team Performance Domain

p. 52

which states

"Effective project managers proactively address conflict rather than avoid it." This proactive approach begins with understanding the source of the conflict.

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

Inc. See Section 4.3

Models

Methods

and Artifacts

under the "Conflict Management" method

which implicitly requires identifying the cause of the conflict as the first step to selecting an appropriate resolution strategy (e.g.

collaborating/problem-solving).

3. Kerzner

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

Scheduling

and Controlling (12th ed.). Wiley. In Chapter 6

"Management Functions

" the discussion on conflict resolution emphasizes the "confrontation" or "problem-solving" mode as the most effective. This mode involves directly addressing the disagreement to identify the root cause and find a mutually agreeable solution.

These terms describe behavioral constraints addressed in Critical Chain Project Management (CCPM). Parkinson’s Law dictates that work expands to fill the time allotted, eliminating potential early finishes. Self-Protection occurs when resources hide early finishes to prevent management from reducing future time estimates, thereby protecting their "safety" margins. Student Syndrome refers to the human tendency to delay the start of a task until the deadline is imminent, which consumes the project buffer before work even begins. Finally, the Dropped Baton effect describes a resource handoff failure: when a predecessor finishes early but the successor is unprepared, the time gained is lost, neutralizing the benefit of the early finish.

Goldratt, E. M. (1997). Critical Chain. Great Barrington, MA: The North River Press. (Chapters 11-13 detail Student Syndrome, Parkinson's Law, and the "relay runner" dropped baton analogy).

Leach, L. P. (1999). "Critical Chain Project Management." Project Management Journal, 30(2), 39–51. (Defines Student Syndrome and Parkinson’s Law in the context of project buffers).

Herroelen, W., & Leus, R. (2001). "On the merits and pitfalls of critical chain scheduling." Journal of Operations Management, 19(5), 559-577. https://doi.org/10.1016/S0272-6963(01)00054-7 (Academic review of Goldratt’s behavioral assumptions).

Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Newtown Square, PA: Project Management Institute. (Section 9.1 and 6.4 discuss resource management and estimation behaviors).

The root cause of the issue is a conflict of authority and a lack of clarity regarding decision-making power over requirements. A manager, due to their influence, overruled a requirement from a subject matter expert (SME). This situation indicates a failure in the initial stakeholder analysis and engagement planning. The project manager's primary responsibility is to understand the stakeholder landscape, including their roles, interests, and authority levels. By consulting with the project sponsor, who typically authorizes the project and has organizational authority, the project manager could have formally clarified the roles and decision-making responsibilities of key stakeholders like the manager and the SME. This foundational step would have ensured the correct individuals were engaged for requirements approval, preventing this late-stage conflict.

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

Inc.

Section 2.3

Stakeholder Performance Domain (p. 42): This section emphasizes that effective stakeholder engagement involves understanding stakeholders' "authority to make decisions." The scenario highlights a failure in this understanding. Clarifying roles and responsibilities with a sponsor is a key activity in analyzing and planning for stakeholder engagement.

Section 4.5.2

Tailoring Stakeholder Engagement (p. 113): "The project manager and the project team can consult with the sponsor...to identify the key stakeholders." This consultation extends beyond a simple list to understanding their roles and influence.

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

Inc.

Section 13.1.2.1

Stakeholder Analysis (p. 511): This section details the process of analyzing stakeholders' roles

interests

influence

and impact. The conflict between the manager and SME points to an inadequate analysis of power and influence. Consulting the sponsor is a primary method for gathering this information.

Section 13.2

Plan Stakeholder Engagement (p. 516): The goal of this process is to develop "strategies to effectively engage stakeholders throughout the project life cycle

based on the analysis of their needs

interests

and potential impact." This plan would formalize the roles and responsibilities discussed with the sponsor.

3. Pinto

J. K. (2000). Understanding the role of politics in successful project management. International Journal of Project Management

18(2)

85-91. https://doi.org/10.1016/S0263-7863(98)00073-0

This article underscores the importance of understanding the political landscape and power structures within an organization for project success. The scenario is a classic example of project politics where a manager's influence (informal or formal power) impacts the project outcome. A project manager must proactively identify and manage these political stakeholders

often by clarifying their roles and authority with senior leadership like the project sponsor.

This exercise contrasts the core philosophies of predictive (plan-driven) and agile (change-driven) project management.

• Predictive: This approach, often called "waterfall," is built on detailed upfront planning. Requirements are fully defined at the start. Because the plan is paramount, Changes are undesirable and thus constrained. Risk and Cost are managed via a detailed initial plan. Key Stakeholders are typically involved at major sign-off points or milestones.
• Agile: This iterative approach is designed to embrace change. Requirements are expected to evolve and are elaborated frequently in small batches. Changes are welcomed and incorporated in real-time during development sprints or iterations. Key Stakeholders (like a product owner) are continuously involved to provide constant feedback. Risk and Cost are managed iteratively as new information and requirements emerge.

MIT OpenCourseWare. (2016). 16.852J / ESD.36J System and Project Management. Fall 2016. Lecture 3: Project Life Cycles & Processes.

Reference: This lecture material explicitly contrasts predictive (e.g., Waterfall) and adaptive (Agile) lifecycles. It notes that predictive models fix requirements early, while adaptive models allow requirements to be elaborated throughout the project. It also describes stakeholder involvement as periodic in predictive models versus continuous in adaptive models.

Tripp, J., & Armstrong, D. J. (2018). "Agile Methodology: A Review of the Literature and Project Management Framework." Journal of Information Systems Education, 29(3), 147-156.

Reference: Page 148 discusses how Agile methodologies, unlike traditional predictive models, "welcome changing requirements, even late in development." This supports matching "incorporated in real-time" with Agile changes and "constrained" with Predictive changes.

Serrador, P., & Pinto, J. K. (2015). "Does Agile work?—A quantitative analysis of agile project success." International Journal of Project Management, 33(5), 1040-1051. https://doi.org/10.1016/j.ijproman.2015.01.006

Reference: Page 1041, in its comparison of "Traditional" (Predictive) and "Agile" methods, highlights that stakeholder engagement in traditional models is "Limited, at start and end," whereas in Agile it is "Constant." This supports the placement of "involved at specific milestones" (Predictive) and "continuously involved" (Agile).

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

Reference: Section 3.1 (Page 18-19), "Characteristics of Project Life Cycles," contrasts predictive and agile approaches. It states predictive life cycles involve "up-front planning" for scope, time, and cost, supporting the "controlled by detailed planning" match. In contrast, it describes agile life cycles as having requirements "elaborated in iterations," supporting the "elaborated frequently" match.