- Two senior developers on your agile project openly argue during a daily standup about which database technology to use, and their disagreement is now delaying a key feature. As the project manager applying servant leadership, what should you do first?
- Reassign one of the developers to a different feature so they stop interacting
- Bring the two developers together to understand the underlying interests behind each position before facilitating a resolution
- Escalate the disagreement to the project sponsor for a final ruling
- Make the technology decision yourself to end the delay and restore momentum
Correct answer: Bring the two developers together to understand the underlying interests behind each position before facilitating a resolution
The first step in managing conflict is to understand its source and the underlying interests, not the surface positions. A collaborating (problem-solving) approach starts by listening to both parties. Imposing a decision, escalating, or separating them avoids the conflict rather than resolving it constructively.
- A project manager notices early signs of disagreement when two team members begin disputing facts and ownership of a deliverable, but the issue has not yet become personal or hostile. According to the stages of conflict, this situation is best described as which stage?
- A crusade, where parties view their position as the only acceptable one
- A world war, where the goal has shifted to defeating the other party
- A daily annoyance with no real impact on the work
- A problem to solve, where parties exchange information and openly debate
Correct answer: A problem to solve, where parties exchange information and openly debate
In escalating conflict stages, the earliest manageable stage is 'problem to solve,' characterized by open exchange of facts and constructive debate. Crusade and world war are later, more destructive stages. Recognizing the stage early lets the PM intervene while resolution is still collaborative.
- During sprint planning, a stakeholder and a team lead reach an impasse over scope. To preserve the relationship and find a solution acceptable to both, the project manager facilitates a discussion where both parties' concerns are fully addressed. Which conflict resolution approach is being used?
- Withdrawing / avoiding
- Collaborating / problem solving
- Forcing / directing
- Smoothing / accommodating
Correct answer: Collaborating / problem solving
Collaborating (problem solving) seeks a win-win outcome by addressing all parties' concerns, which builds commitment and preserves relationships. Smoothing minimizes differences, forcing imposes one view, and withdrawing postpones the issue—none of which fully satisfy both parties.
- A project manager faces a conflict between two team members over a minor formatting standard while a critical production outage demands immediate attention. The PM tells the team to use one standard for now and revisit the debate later. Which conflict-handling technique is most appropriate here and why?
- Withdrawing, because the formatting issue should never be addressed
- Forcing, because a quick decision on a low-stakes issue lets the team refocus on the urgent priority
- Compromising, because both parties must lose something equally
- Collaborating, because every conflict requires a full win-win discussion
Correct answer: Forcing, because a quick decision on a low-stakes issue lets the team refocus on the urgent priority
Forcing (directing) is appropriate when a quick, decisive resolution is needed on a low-importance issue, especially under time pressure. The relationship cost is minimal because the stakes are low, and it frees the team to handle the urgent outage. Collaborating would waste time disproportionate to the issue's importance.
- After resolving a heated dispute between two team members, the project manager wants to prevent similar conflicts from recurring. Which action best supports this goal?
- Work with the team to establish and document ground rules that define acceptable behavior and a process for raising disagreements
- Require all future disagreements to be escalated directly to the sponsor
- Document the individuals involved in a performance file for later review
- Reduce team interaction by assigning members to work in isolation
Correct answer: Work with the team to establish and document ground rules that define acceptable behavior and a process for raising disagreements
Defining team ground rules establishes shared expectations for communication and conflict, reducing recurrence. Escalating everything overloads the sponsor and undermines team self-management, isolating members harms collaboration, and punitive documentation damages psychological safety and trust.
- A project manager observes that a recurring conflict between the QA team and the development team stems from QA feeling their defect reports are ignored. Before recommending a resolution, what should the project manager do to properly analyze the context?
- Wait to see whether the conflict resolves itself over the next few sprints
- Assume the conflict is purely personal and address it through discipline
- Immediately apply a compromise so each side gives up something equally
- Investigate the broader circumstances, history, and stakeholder dynamics surrounding the conflict
Correct answer: Investigate the broader circumstances, history, and stakeholder dynamics surrounding the conflict
Managing conflict requires analyzing the context—history, environment, and relationships—before choosing a resolution. Jumping to compromise without understanding root causes, assuming it is personal, or ignoring it all skip the analysis step essential to selecting the right approach.
- A team member privately tells the project manager that they feel another member consistently takes credit for shared work, but they are afraid to raise it. What is the most effective first action for the project manager?
- Reassign the complaining member to remove them from the situation
- Publicly call out the credit-taking behavior in the next team meeting
- Create a safe environment and facilitate a direct conversation between the parties to surface and address the concern
- Ignore it since the complaint was made privately and informally
Correct answer: Create a safe environment and facilitate a direct conversation between the parties to surface and address the concern
Effective conflict management surfaces issues in a psychologically safe way and helps the parties address them directly. Public confrontation humiliates and escalates, ignoring it lets resentment grow, and reassignment avoids rather than resolves the underlying conflict.
- When a compromise (reconcile) approach is used to resolve a conflict between two stakeholders, what is the most accurate description of the typical outcome?
- Both parties give up something, producing a temporary or partial resolution that may leave neither fully satisfied
- One party fully wins while the other fully loses
- The conflict is permanently eliminated with no follow-up needed
- Both parties achieve everything they wanted with no trade-offs
Correct answer: Both parties give up something, producing a temporary or partial resolution that may leave neither fully satisfied
Compromising (reconciling) involves mutual concessions, producing a 'lose-lose' or partial solution that is often temporary because neither party is fully satisfied. It differs from collaborating (win-win) and forcing (win-lose) and frequently requires later follow-up.
- A project manager is setting direction for a newly formed cross-functional team. Which action best reflects providing a clear vision and mission for the team?
- Articulate the project's purpose and desired outcomes so members understand how their work contributes to the larger goal
- Assign each member detailed daily tasks without explaining the overall objective
- Tell the team the deadline and let them infer the purpose on their own
- Focus only on individual performance metrics rather than shared goals
Correct answer: Articulate the project's purpose and desired outcomes so members understand how their work contributes to the larger goal
Leading a team starts with communicating a clear vision and mission that connects members' work to project outcomes, fostering alignment and motivation. Issuing tasks without context, providing only a deadline, or focusing solely on individual metrics fail to create shared purpose.
- A project manager removes obstacles for the team, asks how they can help members succeed, and prioritizes the team's growth and needs over personal authority. Which leadership style is the project manager demonstrating?
- Laissez-faire leadership
- Autocratic leadership
- Transactional leadership
- Servant leadership
Correct answer: Servant leadership
Servant leadership focuses on serving the team—removing impediments, supporting growth, and enabling success. Transactional leadership relies on rewards/penalties, autocratic centralizes control, and laissez-faire is hands-off. Servant leadership is heavily emphasized in PMI's people-centric, agile-aware approach.
- A project manager leads a highly experienced, self-organizing team that consistently delivers without close oversight. Which leadership style is generally most appropriate for this team?
- A delegating, hands-off style that grants the team autonomy to make decisions
- A highly directive style that specifies exactly how each task is performed
- A controlling style that requires approval for every minor decision
- An avoidant style that withholds all guidance and feedback
Correct answer: A delegating, hands-off style that grants the team autonomy to make decisions
Situational leadership matches style to team maturity. A mature, capable, self-organizing team performs best with a delegating, autonomy-granting style. Heavy direction or control would demotivate skilled members, and an avoidant style abandons the leader's facilitative role.
- A globally distributed project team includes members from several cultures and backgrounds. Which leadership behavior best demonstrates support for diversity and inclusion?
- Actively seek input from all members and adapt communication so every voice is heard and valued
- Rely primarily on the most vocal members to represent the team's views
- Standardize all meetings to one time zone regardless of member location
- Limit decision-making input to members who share the project manager's background
Correct answer: Actively seek input from all members and adapt communication so every voice is heard and valued
Supporting diversity and inclusion means ensuring all members can contribute and feel valued, which often requires adapting communication and accommodating differences. Favoring vocal members, ignoring time zones, or limiting input to similar backgrounds undermines inclusion and team performance.
- A team member is highly skilled but recently disengaged and unmotivated. Applying motivation theory, what is the project manager's best first step to re-engage them?
- Assign more tasks to keep the member busy
- Have a conversation to understand the member's needs and what intrinsically motivates them, then adjust support accordingly
- Immediately offer a cash bonus tied to the next deliverable
- Issue a formal warning about declining engagement
Correct answer: Have a conversation to understand the member's needs and what intrinsically motivates them, then adjust support accordingly
Inspiring and motivating requires understanding individual drivers, since intrinsic factors (purpose, autonomy, recognition) often matter more than money for skilled professionals. Offering cash assumes the cause, a warning damages trust, and adding work ignores the root issue.
- To lead effectively, a project manager wants to understand how different stakeholders can affect project outcomes. Which activity directly supports analyzing stakeholder influence?
- Assume all stakeholders have equal influence and engage them identically
- Wait until a stakeholder raises a concern before considering their influence
- Communicate only with the sponsor and ignore other stakeholders
- Assess each stakeholder's level of power, interest, and ability to impact the project
Correct answer: Assess each stakeholder's level of power, interest, and ability to impact the project
Leading a team includes analyzing stakeholders' influence by evaluating power, interest, and impact so engagement can be tailored. Treating all stakeholders the same, communicating only with the sponsor, or being purely reactive all reduce the PM's ability to lead and influence effectively.
- A project manager wants to influence a key stakeholder who controls a critical resource but reports outside the project's authority. Lacking formal authority over this person, which form of power is the project manager most likely relying on?
- Reward power through control of the stakeholder's compensation
- Coercive power through threats of penalties
- Referent or expert power, built through relationships and credibility
- Legitimate (formal positional) power over the stakeholder
Correct answer: Referent or expert power, built through relationships and credibility
When a PM lacks formal authority, influence comes from referent power (relationships, respect) and expert power (knowledge, credibility). Legitimate, coercive, and reward power all depend on positional authority the PM does not have over an external stakeholder.
- During team formation, members are polite but uncertain about roles and rely heavily on the project manager for direction. According to Tuckman's model, which stage is the team in, and what leadership emphasis fits best?
- Forming, where the leader provides clear direction and orientation
- Norming, where the leader reinforces established ways of working
- Performing, where the leader delegates and steps back
- Adjourning, where the leader focuses on closure and recognition
Correct answer: Forming, where the leader provides clear direction and orientation
In Tuckman's forming stage, members are new, uncertain, and dependent on the leader, so directive guidance and orientation are most helpful. Performing warrants delegation, adjourning focuses on closure, and norming reinforces agreed norms—each requiring a different leadership emphasis.
- A project manager learns that a team has just entered the storming stage, with members challenging approaches and competing for influence. What leadership behavior best helps the team move forward productively?
- Facilitate open discussion of differences and coach the team toward shared agreements
- Replace the most outspoken members to reduce friction
- Suppress all disagreement to maintain a calm appearance
- Step back completely and let the conflicts resolve on their own
Correct answer: Facilitate open discussion of differences and coach the team toward shared agreements
During storming, conflict is natural; the leader should facilitate and coach the team to work through differences toward norming. Suppressing disagreement, removing members, or fully withdrawing prevents the team from developing the trust and norms needed to reach the performing stage.
- A project manager must choose how to lead a team that is competent but lacks confidence on a new type of project. Applying situational leadership, which approach is most appropriate?
- A fully delegating style that leaves the team entirely on its own
- A detached style that provides neither direction nor support
- A supportive, coaching style that builds confidence while involving the team in decisions
- A purely directive style that dictates every step without input
Correct answer: A supportive, coaching style that builds confidence while involving the team in decisions
Situational leadership tailors style to readiness. A competent but low-confidence team benefits from a supportive/coaching style that encourages and involves them. Pure direction ignores their competence, full delegation overwhelms their low confidence, and a detached style offers no help.
- A project manager wants the team to feel ownership and stay motivated on a long, demanding initiative. Which leadership action best inspires and motivates the team over time?
- Rely solely on the contractual obligations in members' job descriptions
- Promise large rewards but defer all recognition until project close
- Monitor activity closely and correct mistakes without acknowledging successes
- Connect daily work to a meaningful purpose and recognize contributions regularly
Correct answer: Connect daily work to a meaningful purpose and recognize contributions regularly
Sustained motivation comes from purpose and timely recognition, which reinforce intrinsic drivers and engagement. Relying only on obligations is uninspiring, focusing only on mistakes erodes morale, and deferring all recognition until the end fails to motivate during the work.
- A project manager is deciding how to lead two very different team members: a junior member needing guidance and a senior expert who values autonomy. What is the most effective leadership approach?
- Delegate fully to both to treat everyone equally
- Adapt the leadership style to each individual's experience and needs rather than applying one uniform approach
- Lead only the senior member and let them manage the junior member
- Apply the same directive style to both to ensure consistency
Correct answer: Adapt the leadership style to each individual's experience and needs rather than applying one uniform approach
Effective leaders distinguish among team members and tailor their approach—more guidance for the junior member, more autonomy for the expert. A single uniform style ignores individual needs, blanket delegation may overwhelm the junior, and offloading leadership abdicates the PM's responsibility.
- A newly assigned project manager wants to establish credibility and the ability to influence a skeptical team early in the project. Which action most effectively builds the relational foundation for influence?
- Demonstrate competence, follow through on commitments, and show genuine interest in team members' concerns
- Avoid engaging until the team proves its reliability
- Make ambitious promises about outcomes to win quick support
- Immediately assert positional authority and emphasize the reporting hierarchy
Correct answer: Demonstrate competence, follow through on commitments, and show genuine interest in team members' concerns
Influence grows from trust, built through demonstrated competence (expert power), reliability, and genuine concern (referent power). Asserting hierarchy alone breeds resistance, withholding engagement delays trust, and overpromising risks credibility when commitments cannot be met.
- A project sponsor pressures the project manager to adopt an autocratic, command-and-control style, but the team is experienced and works in an agile environment. How should the project manager respond?
- Delegate the leadership decision entirely to the team
- Ignore the sponsor and continue without any discussion
- Explain how an empowering, servant-leadership style better suits the team and environment, while addressing the sponsor's underlying concerns
- Immediately adopt the autocratic style to satisfy the sponsor
Correct answer: Explain how an empowering, servant-leadership style better suits the team and environment, while addressing the sponsor's underlying concerns
Determining an appropriate leadership style requires matching it to the team and context; an experienced agile team performs best under empowerment. The PM should educate the sponsor and address their concerns rather than blindly comply, ignore the sponsor, or abdicate the decision.
- A project manager notices that one team member quietly dominates technical decisions, leaving others disengaged. To lead the team toward better balance, what should the project manager do?
- Allow the dominant member to continue since the work still gets done
- Direct all technical decisions personally to bypass the team
- Facilitate inclusive decision-making so all members contribute and feel ownership
- Remove the dominant member to reduce their influence
Correct answer: Facilitate inclusive decision-making so all members contribute and feel ownership
Leading a team includes fostering inclusion and shared ownership so all members engage. Allowing dominance disengages others, removing the member is disproportionate and loses expertise, and centralizing decisions undermines team empowerment and growth.
- A conflict between two functional managers escalates to the point where each is actively trying to undermine the other's standing rather than solve the original issue. Which stage of conflict does this represent, and what does it imply for resolution?
- An early problem-to-solve stage easily handled by the team
- The most severe stage, where resolution is very difficult and may require higher-level intervention
- A minor disagreement that will dissipate without action
- A constructive debate that should be encouraged to continue
Correct answer: The most severe stage, where resolution is very difficult and may require higher-level intervention
When parties shift from resolving the issue to defeating each other, the conflict has reached its most destructive stage, where collaborative resolution is unlikely and escalation or higher-level intervention may be required. This is the opposite of the manageable early problem-to-solve stage.
- A project manager notices that one experienced developer consistently produces high-quality code ahead of schedule, while the rest of the team relies on detailed daily direction. To support overall team performance, what is the BEST approach for the project manager to take with the high performer?
- Reassign the developer to mentor the slower members so the team's average velocity rises
- Increase the number of status reviews to ensure the high quality is maintained
- Delegate ownership of a complex module and reduce check-in frequency, giving the developer greater autonomy
- Move the developer's tasks to the critical path so the project finishes sooner
Correct answer: Delegate ownership of a complex module and reduce check-in frequency, giving the developer greater autonomy
Empowering team members means matching the level of autonomy to demonstrated capability. A proven high performer benefits from delegated ownership and fewer check-ins, which builds engagement and accountability. Forcing mentoring, adding reviews, or reshuffling the schedule does not reflect appropriately empowering a capable individual.
- During a performance discussion, a team member tells the project manager that she feels her contributions go unnoticed because recognition only happens at major milestones. What should the project manager do to BEST support this team member's performance?
- Ask her to document her own accomplishments and present them at the next review
- Introduce timely, specific recognition for meaningful day-to-day contributions, not just milestones
- Explain that milestone-based recognition is standard and cannot be changed
- Promise her a larger bonus at the end of the project to compensate
Correct answer: Introduce timely, specific recognition for meaningful day-to-day contributions, not just milestones
Effective recognition is timely and specific, reinforcing desired behaviors close to when they occur. Reserving recognition for milestones or deferring it weakens its motivational value. Telling her nothing can change or shifting the burden to her does not address the gap.
- A project manager wants to empower the team to make more decisions without escalating every issue. Which action MOST directly supports this goal?
- Clearly define the boundaries within which the team can decide on its own and what must be escalated
- Require the team to submit a written justification for every decision they make
- Schedule a daily meeting where the project manager approves all pending decisions
- Tell the team they may decide anything as long as the project manager is not blamed
Correct answer: Clearly define the boundaries within which the team can decide on its own and what must be escalated
Empowerment requires clarity about decision authority. Defining the boundaries of autonomy lets the team act confidently while knowing when escalation is required. Mandatory justifications or daily approvals re-centralize control, and vague open-ended permission without boundaries creates risk and confusion.
- A team member has met all assigned objectives but expresses that the work has become routine and unchallenging. To support both performance and engagement, what should the project manager do FIRST?
- Reassign the member to less critical work to avoid burnout
- Wait until the next formal appraisal cycle to raise development options
- Increase the volume of routine tasks to keep the member fully utilized
- Discuss the member's career interests and identify stretch assignments aligned with development goals
Correct answer: Discuss the member's career interests and identify stretch assignments aligned with development goals
Supporting individual performance includes developing team members. Understanding the person's goals and offering challenging, development-oriented work sustains engagement. Adding routine volume, sidelining the person, or waiting for a formal cycle fails to address the disengagement promptly.
- A project manager delegates a critical vendor coordination task to a team member but later discovers the member made a poor decision that delayed a deliverable. What is the BEST response to preserve empowerment while protecting the project?
- Tell the member to escalate every vendor decision going forward
- Document the failure formally and reduce the member's responsibilities
- Revoke the member's authority and personally handle all future vendor coordination
- Review what happened with the member, treat it as a learning opportunity, and clarify guidance for similar future decisions
Correct answer: Review what happened with the member, treat it as a learning opportunity, and clarify guidance for similar future decisions
Empowerment includes allowing room for mistakes and using them as coaching opportunities. Pulling authority, punishing, or forcing constant escalation undermines trust and the development the project manager was trying to build. Clarifying guidance balances learning with project protection.
- While appraising team performance, the project manager realizes that one objective measure of productivity is making team members compete against each other and harming collaboration. What should the project manager do?
- Keep the measure because it objectively increases individual output
- Adjust the performance measures to reward collaborative outcomes alongside individual contributions
- Privately tell top performers to stop sharing knowledge to maintain their ranking
- Remove all performance measurement to eliminate competition
Correct answer: Adjust the performance measures to reward collaborative outcomes alongside individual contributions
Performance measures should reinforce the behaviors the project needs, including collaboration. If a metric drives counterproductive competition, the project manager should rebalance it to reward team outcomes. Eliminating measurement entirely or discouraging knowledge sharing harms the project.
- A self-organizing agile team has been empowered to select how it accomplishes its work. A senior stakeholder pressures the project manager to dictate the team's technical approach. How should the project manager respond?
- Make the technical decision personally to satisfy both parties
- Ask the stakeholder to attend daily standups and direct the team in person
- Direct the team to follow the stakeholder's technical approach to avoid conflict
- Protect the team's autonomy by communicating constraints and goals to the team and letting them choose the approach
Correct answer: Protect the team's autonomy by communicating constraints and goals to the team and letting them choose the approach
A self-organizing team is empowered to determine how work gets done. The project manager shields the team from external direction while ensuring goals and constraints are clear. Imposing the stakeholder's approach or directing the team personally violates the empowerment the team was given.
- A project manager observes that two team members have grown significantly in skill and now consistently solve problems independently. To continue supporting their development, what is the MOST appropriate next step?
- Keep their responsibilities stable to avoid disrupting the team
- Assign them more of the same tasks they already perform well
- Hold them to stricter oversight since they now handle critical work
- Increase their level of responsibility and authority to match their demonstrated competence
Correct answer: Increase their level of responsibility and authority to match their demonstrated competence
Supporting team performance involves growing members as their capability grows. Increasing responsibility and authority recognizes their development and sustains motivation. Holding responsibility flat, repeating the same work, or adding oversight contradicts their proven readiness for more.
- A team member confides that he is unsure whether he has the authority to approve a minor scope clarification with a customer. The project manager wants to empower the team to act decisively. What is the BEST action?
- Suggest he avoid customer conversations until the project ends
- Confirm and document the decision authority the member holds so he can act within clear limits
- Advise him to approve whatever the customer requests to keep them satisfied
- Tell him to bring all customer interactions to the project manager
Correct answer: Confirm and document the decision authority the member holds so he can act within clear limits
Empowerment depends on the team understanding the scope of their authority. Confirming and documenting the member's decision rights lets him act confidently within defined limits. Routing everything to the project manager, deferring to the customer blindly, or avoiding contact all undercut empowerment.
- A high-performing team has just delivered a difficult release on time. The organization offers only annual monetary bonuses, which are months away. What should the project manager do to recognize the team NOW?
- Wait for the annual bonus cycle since formal rewards are most valued
- Provide immediate, meaningful non-monetary recognition such as public acknowledgment and a team appreciation event
- Send a brief email to the sponsor noting the team met the date
- Recognize only the two members who contributed the most
Correct answer: Provide immediate, meaningful non-monetary recognition such as public acknowledgment and a team appreciation event
Recognition is most effective when it is timely. When monetary rewards are constrained or delayed, prompt non-monetary recognition reinforces the achievement immediately. Waiting months, recognizing only a few, or sending an internal note that the team never sees diminishes the impact.
- A project manager is building a reward system for the team. To ensure the system actually motivates the team, which characteristic is MOST important?
- Rewards are given equally to everyone regardless of contribution to ensure fairness
- Rewards are kept secret so they create surprise and excitement
- Rewards are tied to behaviors and outcomes the team can influence through their own actions
- Rewards are based purely on factors outside the team's control to ensure objectivity
Correct answer: Rewards are tied to behaviors and outcomes the team can influence through their own actions
A win-win reward system reinforces behaviors team members can control and want to repeat. Tying rewards to uncontrollable factors removes motivation, secrecy prevents people from working toward the reward, and uniform rewards regardless of contribution fail to reinforce desired performance.
- A team member with strong potential repeatedly hesitates to make decisions and waits for the project manager's approval even on routine matters. What is the BEST way to empower this member?
- Make the routine decisions for the member to keep work moving
- Tell the member that future hesitation will be noted in performance reviews
- Gradually delegate decisions, coach through early ones, and build the member's confidence to act independently
- Assign the member only tasks that never require decisions
Correct answer: Gradually delegate decisions, coach through early ones, and build the member's confidence to act independently
Empowerment of a hesitant but capable member is best achieved through progressive delegation and coaching, which builds confidence and competence. Making decisions for them, removing all decision-making, or threatening consequences does not develop the member's independence.
- During a sprint retrospective, the team proposes changing their own working agreement to improve flow. The project manager believes the current process is fine. What should the project manager do to support the empowered team?
- Override the proposal and require the team to keep the current process
- Tell the team that process decisions belong to the project manager
- Allow the change only if the sponsor approves it first
- Encourage the team to try their proposed change and evaluate the results in a future retrospective
Correct answer: Encourage the team to try their proposed change and evaluate the results in a future retrospective
An empowered, self-organizing team owns its process improvements. Supporting their experimentation and evaluating the outcome reinforces ownership and continuous improvement. Overriding them, requiring sponsor approval for an internal process tweak, or claiming process authority undermines empowerment.
- A project manager wants to appraise individual team performance fairly across a diverse, distributed team. What practice BEST supports a fair appraisal?
- Rely on input only from the most vocal team members about their peers
- Establish clear, agreed-upon performance expectations and assess each member against them consistently
- Rank members against one another based on the manager's general impressions
- Evaluate members primarily on hours logged regardless of results delivered
Correct answer: Establish clear, agreed-upon performance expectations and assess each member against them consistently
Fair appraisal depends on clear, agreed expectations applied consistently to each individual. Subjective ranking, biased peer input, or measuring hours instead of outcomes introduces unfairness and fails to reflect actual contribution to project objectives.
- A team member completes a delegated task differently than the project manager would have, but the result fully meets the requirements. How should the project manager respond to reinforce empowerment?
- Acknowledge the successful outcome and respect the member's chosen approach
- Note that the approach was nonstandard and require approval next time
- Take over the next similar task to ensure it is done the preferred way
- Explain the method the project manager would have preferred and ask the member to redo it
Correct answer: Acknowledge the successful outcome and respect the member's chosen approach
When delegating, the project manager empowers members to choose how to achieve outcomes. If requirements are met, the method is the member's to own. Asking for a redo, requiring future approval, or taking over signals distrust and erodes the empowerment that delegation establishes.
- A project manager realizes that the team has the skills to resolve a recurring technical issue but keeps escalating it. Investigation shows the team fears blame if a fix fails. What should the project manager do FIRST to empower the team?
- Issue a directive that the team must resolve the issue without escalating
- Create a psychologically safe environment where reasonable attempts to solve problems are supported, not punished
- Assign blame for the recurring issue to motivate faster resolution
- Take the issue away from the team and resolve it personally
Correct answer: Create a psychologically safe environment where reasonable attempts to solve problems are supported, not punished
Empowerment requires psychological safety; teams will not exercise authority if they fear punishment for honest attempts. Building that safety addresses the root cause. A directive, assigning blame, or removing the work reinforces the fear or strips the team of the ownership being sought.
- A team has been delivering steadily, and the project manager wants to sustain high performance. Which ongoing practice MOST directly supports continued strong team performance?
- Withhold positive feedback so the team does not become complacent
- Regularly provide constructive feedback and remove the need for the team to repeatedly prove themselves
- Reduce communication to avoid disrupting the team's flow
- Increase oversight as performance improves to protect the gains
Correct answer: Regularly provide constructive feedback and remove the need for the team to repeatedly prove themselves
Supporting team performance involves ongoing feedback and trust. Regular constructive feedback keeps the team aligned and motivated. Going silent, withholding praise to prevent complacency, or tightening oversight as the team improves all undermine the trust that sustains high performance.
- A stakeholder who owns a key business decision is disengaged and slow to respond, stalling the team. To empower this stakeholder to contribute effectively, what should the project manager do?
- Escalate the stakeholder's slowness to their manager immediately
- Make the business decision on the stakeholder's behalf to keep the team moving
- Remove the decision point from the project to avoid waiting
- Clarify the stakeholder's decision authority and the impact of timely input, then enable them to act
Correct answer: Clarify the stakeholder's decision authority and the impact of timely input, then enable them to act
Empowering a stakeholder means ensuring they understand their authority and the consequences of their input, enabling them to engage meaningfully. Making the decision for them, escalating prematurely, or eliminating the decision bypasses rather than empowers the stakeholder.
- During performance development, the project manager identifies that a team member lacks a specific skill needed for upcoming work but is eager to learn. What action BEST supports this member's performance and development?
- Wait to see if the member can figure it out independently during the work
- Lower the member's responsibilities to match current skills only
- Reassign the upcoming work to a member who already has the skill
- Arrange targeted skill-building and pair the member with someone experienced in that area
Correct answer: Arrange targeted skill-building and pair the member with someone experienced in that area
Supporting team performance includes developing members. Providing targeted training and pairing the eager member with an experienced colleague builds capability for the project. Reassigning the work, hoping they self-teach during critical work, or shrinking responsibilities does not develop the willing member.
- A project manager empowers a team to manage its own task assignments. Soon, two members both want the same desirable assignment. What is the BEST way for the project manager to handle this while preserving empowerment?
- Assign the task personally to the more senior of the two members
- Let the team work out the assignment within their agreed process, intervening only if they cannot resolve it
- Reassign the desirable task to a third member to be fair
- Tell both members the project manager will make all assignments going forward
Correct answer: Let the team work out the assignment within their agreed process, intervening only if they cannot resolve it
An empowered, self-organizing team should resolve its own assignments using its process, with the project manager stepping in only if needed. Immediately assigning it, giving it to someone else, or revoking self-assignment authority over one disagreement undermines the team's empowerment.
- A team consistently meets deadlines but quality defects are rising. The project manager is appraising performance. What is the MOST appropriate way to address this?
- Provide feedback that balances both speed and quality expectations and adjust recognition to value quality outcomes
- Increase the deadline pressure to motivate more careful work
- Praise the team only for meeting deadlines to keep morale high
- Penalize the team financially for the defects
Correct answer: Provide feedback that balances both speed and quality expectations and adjust recognition to value quality outcomes
Appraisal should reflect the full set of objectives, including quality. Giving balanced feedback and ensuring recognition values quality realigns behavior. Praising only speed reinforces the wrong trade-off, financial penalties damage trust, and more pressure typically worsens quality.
- A project manager wants a team member to take ownership of stakeholder communications for one workstream. Which approach BEST empowers the member to succeed?
- Require the member to copy the project manager on every message for approval
- Limit the member to forwarding messages the project manager writes
- Draft each communication for the member to send under their name
- Define the goal and authority, ensure the member has needed information, and let them manage the communications
Correct answer: Define the goal and authority, ensure the member has needed information, and let them manage the communications
True empowerment grants both responsibility and the authority and resources to act. Defining the goal, granting authority, and supplying information lets the member own the work. Ghost-writing, mandatory approvals, or restricting them to forwarding keeps control with the project manager and is not empowerment.
- A long-tenured team member's performance has recently declined. During a one-on-one, the project manager learns the member feels unchallenged and undervalued. What should the project manager do to BEST support performance recovery?
- Reassign the member to a different project to reset expectations
- Issue a formal performance warning to prompt improvement
- Collaborate with the member to find more meaningful work and recognize past contributions
- Reduce the member's workload until performance naturally improves
Correct answer: Collaborate with the member to find more meaningful work and recognize past contributions
Supporting performance means understanding and addressing root causes. Since the decline stems from feeling unchallenged and undervalued, providing meaningful work and recognition directly addresses it. A warning, reducing workload, or transferring the person ignores the underlying motivation issue.
- A project manager has fully delegated a deliverable to a competent team member, including the authority to make decisions about it. Midway, the project manager feels tempted to closely monitor every step. To maintain effective empowerment, what should the project manager do?
- Reduce the scope delegated to the member to lower the risk
- Begin reviewing the member's daily progress in detail to ensure quality
- Step back, remain available for support, and trust the member to deliver within the agreed expectations
- Quietly redo parts of the work to be sure it meets the standard
Correct answer: Step back, remain available for support, and trust the member to deliver within the agreed expectations
Effective delegation means granting authority and then trusting the member while remaining available. Reverting to detailed daily monitoring, secretly redoing work, or clawing back scope are forms of micromanagement that contradict the empowerment already established.
- A new project requires the team to use a cloud data platform that no current team member has worked with. Before committing to a training plan, what should the project manager do first?
- Add a contingency reserve to the budget to cover anticipated rework
- Hire external contractors who already hold the platform certification
- Schedule a vendor-led certification bootcamp for the entire team immediately
- Assess the gap between the team's current competencies and the skills the project requires
Correct answer: Assess the gap between the team's current competencies and the skills the project requires
A training needs assessment begins by comparing the competencies the project demands against what the team currently possesses. Only after the gap is understood can the PM choose the right training option and allocate resources appropriately.
- During a skills assessment, the project manager finds that two senior engineers already master a tool the rest of the team lacks. Which approach best builds team capability at the lowest cost?
- Arrange internal knowledge-sharing sessions led by the two experienced engineers
- Postpone the work that needs the tool until budget for training is approved
- Send the entire team, including the two experts, to an external paid course
- Reassign all related work exclusively to the two engineers
Correct answer: Arrange internal knowledge-sharing sessions led by the two experienced engineers
When in-house expertise exists, peer-led or mentoring sessions transfer knowledge efficiently and economically, leveraging existing resources rather than paying for redundant external training or creating a single point of failure.
- A project manager wants to track each team member's proficiency across the technical and interpersonal skills the project needs. Which tool most directly supports this?
- A stakeholder engagement assessment matrix
- A skills matrix mapping required competencies against each member's current level
- A risk register with probability and impact scores
- A responsibility assignment matrix (RACI) for the deliverables
Correct answer: A skills matrix mapping required competencies against each member's current level
A skills (or competency) matrix lays out the competencies required and rates each team member, making gaps visible so training and assignments can be planned. RACI assigns responsibility, not skill levels.
- Midway through execution, a regulatory change introduces a new compliance requirement the team is untrained for. What is the most appropriate response?
- Document the gap in the issue log and revisit it at project closure
- Continue as planned and address compliance issues during the next phase
- Reassess team training needs and arrange targeted training on the new requirement
- Escalate to the sponsor to remove the compliance requirement from scope
Correct answer: Reassess team training needs and arrange targeted training on the new requirement
Training needs are not assessed only once; when conditions change the PM must continuously reassess and provide targeted training so the team can meet the new requirement promptly.
- The training budget is limited, and only some of five identified skill gaps can be addressed now. How should the project manager decide which training to fund first?
- Prioritize the gaps whose skills are needed soonest and pose the greatest risk to deliverables
- Distribute the budget evenly across all five gaps
- Defer all training until more budget becomes available
- Fund the cheapest training options regardless of when the skills are needed
Correct answer: Prioritize the gaps whose skills are needed soonest and pose the greatest risk to deliverables
With constrained resources the PM allocates training to the competencies that are most urgent and most consequential to upcoming deliverables, sequencing investment by need and risk rather than spreading thin or choosing by price alone.
- A project manager identifies that a key stakeholder from the client side lacks the technical understanding to review interim deliverables effectively. What should the PM do?
- Provide tailored orientation or training so the stakeholder can engage meaningfully
- Simplify the deliverables so no technical understanding is required
- Wait until the stakeholder requests help before offering any training
- Bypass the stakeholder and route reviews to a more technical colleague
Correct answer: Provide tailored orientation or training so the stakeholder can engage meaningfully
Ensuring adequate training extends to stakeholders, not just internal team members. Equipping the stakeholder to participate in reviews keeps engagement effective and avoids decision delays.
- After a paid external course, the project manager wants to confirm the team can now perform the targeted work. What is the best way to validate training effectiveness?
- Collect attendance records confirming everyone completed the course
- Ask the training vendor for a satisfaction survey summary
- Assume competency because the course covered the required topics
- Observe the team applying the new skills on real tasks and measure their performance
Correct answer: Observe the team applying the new skills on real tasks and measure their performance
Effectiveness is demonstrated by performance on actual work, not by attendance or satisfaction. Observing application of the skill confirms the gap is closed and identifies any residual need.
- A project manager is staffing a project and must determine how many resources, with what skills, are needed for each work package. Which planning activity produces this information?
- Performing a make-or-buy analysis for the deliverables
- Creating the stakeholder register
- Building the project budget baseline
- Estimating resource requirements from the activity definitions and effort
Correct answer: Estimating resource requirements from the activity definitions and effort
Deducing project resource requirements means estimating, per activity or work package, the type and quantity of resources (including specific skills) required. This drives staffing and acquisition decisions.
- The PM discovers that a critical specialty skill exists in only one team member, creating a single point of failure. What is the most proactive team-building action?
- Increase the specialist's salary to improve retention
- Forbid the specialist from taking vacation during the project
- Document the dependency in the risk register and take no further action
- Establish cross-training so a second member can perform the specialty work
Correct answer: Establish cross-training so a second member can perform the specialty work
Continuously assessing and refreshing team skills includes building redundancy. Cross-training removes the single point of failure and strengthens overall team resilience, which is a core team-building objective.
- When appraising stakeholder skills to staff a project, the project manager wants the most accurate picture of an individual's actual capabilities. Which source is generally most reliable?
- The individual's job title and tenure
- The number of certifications the individual lists
- Demonstrated performance on prior comparable work and validated references
- The individual's self-rating on a questionnaire
Correct answer: Demonstrated performance on prior comparable work and validated references
Appraising skills accurately relies on evidence of demonstrated performance and validated references rather than self-reported ratings, titles, or certificate counts, which may not reflect real applied ability.
- A project team has been working together for several months. The PM notices skills that were strong early on are now outdated due to evolving project tools. What should the PM do?
- Lower the quality standards to match the team's current skills
- Wait for the team to raise the issue during a retrospective
- Continuously reassess the team's skills and arrange refresher training where needed
- Replace team members whose skills have become outdated
Correct answer: Continuously reassess the team's skills and arrange refresher training where needed
Team skills are not static; the PM must continuously assess and refresh competencies as project needs evolve, providing refreshers so the existing team stays effective rather than churning members or lowering standards.
- A project manager wants to ensure that critical knowledge held by a team member who is rotating off the project is not lost. Which action best supports this?
- Note in the issue log that the member is leaving
- Facilitate structured knowledge transfer sessions and document key information before departure
- Ask the departing member to remain reachable by phone after leaving
- Restrict the member's access so no further changes can be made
Correct answer: Facilitate structured knowledge transfer sessions and document key information before departure
Maintaining team and knowledge transfer means proactively capturing and transferring expertise—through documentation and handover sessions—before a member departs, so the project retains the knowledge.
- In a matrixed organization, the project manager learns that several needed specialists are committed to other projects. To deduce realistic resource availability, what should the PM do?
- Assume the specialists will be free when the schedule requires them
- Recruit external hires for every specialist role to avoid conflicts
- Negotiate with functional managers to confirm the availability and allocation of specialists
- Reduce the project scope so specialists are not needed
Correct answer: Negotiate with functional managers to confirm the availability and allocation of specialists
In a matrix environment resources are shared, so determining real availability requires negotiating with functional managers. Assuming availability creates scheduling risk; confirming it produces an accurate resourcing picture.
- A project manager assesses the team early and finds that, beyond technical gaps, several members lack experience with the agile ceremonies the project will use. What is the best response?
- Assume members will learn the ceremonies as the project proceeds
- Hire an external scrum master and have the team observe only
- Provide training and coaching on the agile practices the project will adopt
- Switch the project to a predictive approach to avoid the gap
Correct answer: Provide training and coaching on the agile practices the project will adopt
Adequate training covers both technical and process competencies. If the team lacks experience with the chosen way of working, coaching and training on those practices closes the gap and enables effective delivery.
- A project manager builds a development plan for each team member based on the skills assessment. What is the primary benefit of this approach to the project?
- It aligns individual skill growth with the competencies the project needs while improving engagement
- It eliminates the need for any external training spending
- It guarantees that no team member will ever leave the project
- It removes the requirement to estimate resources for activities
Correct answer: It aligns individual skill growth with the competencies the project needs while improving engagement
Linking individual development plans to project skill needs closes capability gaps and boosts motivation and retention. It supports rather than replaces resource estimating and does not guarantee retention or zero training cost.
- To staff an upcoming high-complexity work package, the project manager must match available people to the work. What should the PM consider together?
- Only which candidates have the lowest hourly cost
- Only the candidates' seniority within the organization
- Each candidate's skill level, availability, and the competency the work package requires
- Only the personal preferences of the candidates
Correct answer: Each candidate's skill level, availability, and the competency the work package requires
Assigning the right people requires weighing the required competency against each candidate's actual skill level and availability. Seniority, cost, or preference alone do not ensure the work package's skill needs are met.
- During team building, a project manager wants to identify what training the team will need over the whole project, not just for the current phase. What is the best practice?
- Plan training needs across the project timeline and revisit them as work progresses
- Schedule all conceivable training at project start to be safe
- Address training only when a skill gap blocks current work
- Delegate all training decisions to individual team members
Correct answer: Plan training needs across the project timeline and revisit them as work progresses
Training should be planned forward-looking across the project and revisited periodically. Reacting only when work is blocked causes delays, while front-loading all possible training wastes resources on skills not yet needed.
- A project manager reviews resource estimates and finds the planned skill mix cannot deliver a key milestone on time. What is the most appropriate next step?
- Assign existing members extra hours and hope productivity increases
- Quietly extend the milestone date without informing stakeholders
- Proceed and report the milestone as at risk during status reporting
- Revise the resource plan—through additional staff, training, or schedule adjustment—and discuss with the sponsor
Correct answer: Revise the resource plan—through additional staff, training, or schedule adjustment—and discuss with the sponsor
When resource requirements reveal a capability shortfall, the PM addresses it by adjusting staffing, training, or schedule and engages the sponsor as needed. Ignoring it or silently changing dates is not appropriate stewardship.
- A junior analyst on the team has potential but limited experience. The project manager assigns the analyst to work alongside a senior mentor on key tasks. This action primarily supports which objective?
- Eliminating the need to estimate resources for the tasks
- Reducing the project's labor cost by using a junior resource
- Transferring all accountability for the tasks to the senior mentor
- Continuously building and refreshing the team's skills through mentoring
Correct answer: Continuously building and refreshing the team's skills through mentoring
Pairing a junior member with a mentor develops skills on the job, directly supporting ongoing team capability building. It is a development tactic, not primarily a cost-cutting or accountability-shifting measure.
- A project manager wants the team's skill assessment to reflect interpersonal capabilities, not only technical ones. Why does this matter for building the team?
- Interpersonal skills are irrelevant to project delivery outcomes
- Interpersonal skills affect collaboration and team performance and may also reveal training needs
- Only technical skills can be improved through training
- Interpersonal skills are the sponsor's responsibility, not the PM's
Correct answer: Interpersonal skills affect collaboration and team performance and may also reveal training needs
High-performing teams need both technical and interpersonal competencies. Assessing soft skills surfaces gaps (e.g., communication, collaboration) that can be developed through coaching and training, improving overall team effectiveness.
- After acquiring team members from several departments, the project manager wants them to function as a cohesive unit quickly. Which early team-building activity is most effective?
- Wait until conflicts arise and then intervene
- Have each member work independently to avoid friction
- Assign tasks by email without a group meeting
- Hold a kickoff and team-chartering session to align on goals, roles, and working agreements
Correct answer: Hold a kickoff and team-chartering session to align on goals, roles, and working agreements
A kickoff combined with developing a team charter and working agreements accelerates cohesion by clarifying shared goals, roles, and norms early—far more effective than waiting for problems or keeping members isolated.
- A team member completed external training but the project manager observes no improvement in their work output. What should the PM do first?
- Conclude that the member is incapable of learning the skill
- Repeat the same external course for the member
- Immediately remove the member from the project
- Investigate the cause—such as misaligned training content or need for coaching—before deciding next steps
Correct answer: Investigate the cause—such as misaligned training content or need for coaching—before deciding next steps
When training does not yield expected performance, the PM should diagnose why—perhaps the course did not match the need, or on-the-job coaching is required—before taking corrective action, rather than reacting punitively or repeating an ineffective course.
- The project manager needs to determine which specific competencies are required to complete the project's deliverables. Which document or input is most useful to derive these requirements?
- The communications management plan
- The scope baseline and activity list, which define the work to be performed
- The lessons-learned register from a different program
- The procurement statement of work for unrelated vendors
Correct answer: The scope baseline and activity list, which define the work to be performed
Resource and skill requirements are deduced from the defined work—captured in the scope baseline and activity list. Knowing what work must be done lets the PM determine the competencies and quantity of resources needed.
- A project manager records each team member's current and target skill levels and updates them throughout the project. What is the main purpose of maintaining this living record?
- To create a permanent performance file for HR disciplinary use
- To replace the need for one-on-one conversations with the team
- To justify reducing the team size as the project progresses
- To continuously identify gaps and guide ongoing training and assignment decisions
Correct answer: To continuously identify gaps and guide ongoing training and assignment decisions
A maintained skills record is a living tool for continuously spotting gaps and informing training and work-assignment choices as the project evolves—supporting development, not serving as an HR disciplinary file or a substitute for direct communication.
- During daily standups, a developer repeatedly reports being blocked because a vendor has not delivered API credentials that were promised two weeks ago. The project manager has reminded the vendor by email twice with no response. What should the project manager do next to remove this impediment?
- Add the missing credentials to the risk register as a low-probability risk and revisit it at the next monthly review
- Reassign the developer to other backlog items and stop tracking the blocker until the vendor responds on their own
- Escalate to the vendor's account manager and the project sponsor, framing the delay's quantified impact on the schedule and requesting a committed delivery date
- Instruct the developer to build the integration against mock credentials and skip vendor testing entirely
Correct answer: Escalate to the vendor's account manager and the project sponsor, framing the delay's quantified impact on the schedule and requesting a committed delivery date
Removing impediments means taking active, escalating action through the right channels when lower-touch attempts fail. Quantifying the schedule impact and engaging both the vendor's escalation contact and the sponsor pressures a resolution. Ignoring, working around with mocks indefinitely, or downgrading an active blocker to a passive risk all leave the team blocked.
- A Scrum team's velocity has dropped for three consecutive sprints. In the retrospective, members reveal that a shared test environment is constantly unavailable because another team keeps overwriting it. What is the BEST first action for the project manager acting as a servant leader?
- Document the slow velocity in the performance reviews of the team members
- Remove the affected test cases from the sprint so the velocity numbers improve
- Tell the team to work harder to recover the lost velocity in the next sprint
- Facilitate an agreement between the two teams on environment scheduling or secure a dedicated environment, then track the obstacle to closure
Correct answer: Facilitate an agreement between the two teams on environment scheduling or secure a dedicated environment, then track the obstacle to closure
A servant leader clears the path for the team. The root cause is a shared-resource conflict, so the PM should resolve it through inter-team negotiation or a dedicated environment and verify the obstacle is removed. Blaming the team, punishing members, or hiding the symptom by cutting scope does not address the real blocker.
- Midway through a project, a key engineer tells the project manager privately that an organizational policy requiring three sign-offs for any code merge is slowing the team to a crawl. The policy comes from a department outside the project. What should the project manager do?
- Engage the department owner of the policy to explore a streamlined approval path for the project, documenting the business case for the change
- Override the policy within the team since the project deadline takes priority
- Tell the engineer that organizational policies are out of scope and cannot be changed
- Add more team members to absorb the delay caused by the sign-offs
Correct answer: Engage the department owner of the policy to explore a streamlined approval path for the project, documenting the business case for the change
Some impediments are organizational and require the PM to work across boundaries with the policy owner, presenting a business case to relieve the constraint for the project. Unilaterally overriding a policy creates governance risk, dismissing the concern fails the team, and adding people does not remove the structural bottleneck.
- A team member raises an impediment that the project manager cannot resolve within the team's authority. The PM decides to escalate. To make the escalation effective, what information should accompany it?
- A clear description of the blocker, its impact on objectives, options already attempted, and a specific decision or action being requested
- A request for additional budget regardless of the nature of the impediment
- Only the name of the team member who reported the issue so leadership can follow up
- A general statement that the team is behind schedule without specifics
Correct answer: A clear description of the blocker, its impact on objectives, options already attempted, and a specific decision or action being requested
Effective escalation gives decision-makers what they need to act quickly: the issue, its impact, what has been tried, and the specific ask. Naming an individual, vague statements, or defaulting to a budget request fail to enable a targeted decision and slow resolution.
- On a hybrid project, the team logs impediments on a visible board. Several impediments have sat untouched for weeks because no one owns them. What practice should the project manager institute to keep blockers from stagnating?
- Move all impediments to the project sponsor regardless of severity
- Assign an owner and a target resolution date to each impediment and review aging items in a recurring cadence
- Delete impediments that are older than two weeks to keep the board clean
- Allow any team member to close any impediment without verifying resolution
Correct answer: Assign an owner and a target resolution date to each impediment and review aging items in a recurring cadence
Impediments need clear ownership, due dates, and a review cadence so aging items get attention. Deleting unresolved blockers, closing them without verification, or escalating everything to the sponsor either hides problems or floods leadership and prevents real resolution.
- A project manager notices that a recurring impediment — flaky automated tests causing failed builds — keeps reappearing after being marked resolved. What is the most effective response?
- Disable the automated tests so builds stop failing
- Ask the team to ignore failed builds caused by these tests
- Treat it as a systemic issue, perform root-cause analysis with the team, and implement a permanent fix rather than repeatedly clearing the symptom
- Mark the impediment as resolved each time it appears since builds eventually pass
Correct answer: Treat it as a systemic issue, perform root-cause analysis with the team, and implement a permanent fix rather than repeatedly clearing the symptom
A recurring blocker signals an unaddressed root cause. The PM should facilitate root-cause analysis and a durable fix so the impediment stops returning. Repeatedly clearing the symptom, disabling tests, or ignoring failures degrades quality and leaves the obstacle in place.
- Two functional managers each want their resource pulled off the project for competing priorities, and both blockers are stalling the project's critical path. The project manager has limited authority in a weak matrix. What is the BEST approach?
- Convene the affected stakeholders and the sponsor to prioritize the work against organizational goals and secure a committed resourcing decision
- Halt the project until the functional managers resolve the conflict themselves
- Proceed without the resource and accept whatever schedule slip results
- Choose one manager's request to honor based on personal relationship
Correct answer: Convene the affected stakeholders and the sponsor to prioritize the work against organizational goals and secure a committed resourcing decision
In a weak matrix the PM must use influence and bring decision-makers together, anchoring the discussion in organizational priorities to obtain a resourcing commitment. Picking favorites, passively halting the project, or absorbing schedule slip without action all fail to remove the obstacle responsibly.
- A project manager identifies an obstacle: a dependency on a legacy system that the owning team rarely supports. To proactively prevent this from blocking delivery, what should the PM do early?
- Negotiate a service-level agreement and a named point of contact with the owning team before the dependency becomes critical
- Remove the dependency from the project scope without analysis
- Wait until the dependency blocks the team before contacting the owning team
- Build a parallel copy of the legacy system without the owners' knowledge
Correct answer: Negotiate a service-level agreement and a named point of contact with the owning team before the dependency becomes critical
Proactively addressing potential blockers means securing commitments — such as an SLA and a contact — before the obstacle materializes. Waiting for a block, secretly duplicating systems, or cutting scope without analysis are reactive or harmful and do not responsibly manage the dependency.
- A project manager is about to negotiate a statement of work with an external supplier. To prepare for the negotiation, what should the PM determine first?
- The project's objectives, must-haves versus nice-to-haves, and the walk-away point or best alternative
- The personal preferences of the supplier's lead negotiator
- The supplier's internal profit margins so they can be undercut in talks
- A single fixed price with no flexibility regardless of terms offered
Correct answer: The project's objectives, must-haves versus nice-to-haves, and the walk-away point or best alternative
Sound negotiation preparation means understanding your priorities, distinguishing requirements from preferences, and knowing your walk-away point and alternatives. Trying to learn proprietary margins, focusing on personalities, or refusing any flexibility undermines reaching a mutually acceptable, value-driven agreement.
- During contract negotiations, the supplier proposes a clause that shifts all schedule-delay penalties to the buyer even when the supplier is at fault. The project manager believes this is unacceptable. What is the most professional negotiation response?
- Explain the concern, propose alternative language that allocates risk to the party best able to control it, and seek a mutually acceptable revision
- End negotiations immediately and report the supplier for bad faith
- Accept the clause but plan to ignore it if a dispute arises
- Sign the agreement to avoid conflict and address penalties informally later
Correct answer: Explain the concern, propose alternative language that allocates risk to the party best able to control it, and seek a mutually acceptable revision
Effective negotiation aims for fair, mutually acceptable terms; allocating risk to the party best able to control it is a sound principle. The PM should articulate the concern and counter-propose. Signing a bad term, abruptly ending talks, or accepting a clause intending to violate it are unprofessional and create downstream risk.
- A project manager is negotiating an internal agreement with another department for shared resources. The other manager opens with a demand far beyond what the project needs. What is the BEST way to move toward a workable agreement?
- Match the aggressive opening with an equally extreme counter-demand
- Focus the discussion on the underlying interests and needs of both groups rather than the opening positions, and search for options that satisfy both
- Immediately concede to the demand to preserve the relationship
- Refuse to negotiate and escalate to senior leadership at once
Correct answer: Focus the discussion on the underlying interests and needs of both groups rather than the opening positions, and search for options that satisfy both
Interest-based (principled) negotiation shifts away from positional bargaining toward shared interests and creative options that satisfy both parties. Conceding fully, escalating positional warfare, or escalating prematurely without first attempting a good-faith resolution all reduce the chance of a durable internal agreement.
- After reaching a verbal understanding with a vendor on scope and pricing, what should the project manager do to protect the project before work begins?
- Forward an informal email summary without seeking the vendor's confirmation
- Begin work immediately based on the verbal agreement to save time
- Capture the agreed terms in a written, signed agreement that both parties confirm reflects the negotiation
- Assume the vendor will honor the verbal terms and skip documentation
Correct answer: Capture the agreed terms in a written, signed agreement that both parties confirm reflects the negotiation
Negotiated agreements should be formalized in writing and confirmed by both parties to prevent disputes over what was agreed. Starting work on a verbal deal, assuming good faith without documentation, or sending an unconfirmed summary leaves the project exposed to misalignment and contractual risk.
- A project manager is negotiating a change to a fixed-price contract because the customer requested additional features. The customer expects the new features at no extra cost. What should the project manager emphasize during the negotiation?
- That the customer should have specified everything in the original requirements
- That the additional features represent scope beyond the original baseline and require a formal change with corresponding cost and schedule adjustment
- That the request is impossible and cannot be accommodated under any terms
- That the team will absorb the work to keep the customer satisfied
Correct answer: That the additional features represent scope beyond the original baseline and require a formal change with corresponding cost and schedule adjustment
New features beyond the baseline are added scope that warrants a documented change to cost and schedule. The PM negotiates this professionally by explaining the change-control basis. Absorbing the work erodes value, refusing outright damages the relationship, and blaming the customer is unproductive.
- In negotiating a partnership agreement, the project manager realizes the other party holds significantly more leverage. To negotiate effectively from a weaker position, what is the most useful preparation?
- Delay the negotiation indefinitely hoping the leverage shifts
- Conceal all project weaknesses and bluff about nonexistent options
- Agree to whatever terms are offered to avoid losing the deal
- Strengthen the project's best alternative to a negotiated agreement so there is a credible fallback if talks fail
Correct answer: Strengthen the project's best alternative to a negotiated agreement so there is a credible fallback if talks fail
The strength of your best alternative (BATNA) determines your real negotiating power; improving it gives you credible options and reduces pressure to accept poor terms. Bluffing risks credibility, capitulating yields bad terms, and stalling forfeits progress without changing the underlying leverage.
- A project manager and a stakeholder reach an impasse during negotiation of acceptance criteria for a deliverable. Both sides are entrenched. What technique can help break the deadlock while preserving the relationship?
- Accept the stakeholder's criteria entirely to end the disagreement
- Reframe the conversation around shared goals and invite joint problem-solving to generate new options beyond the disputed points
- Suspend all communication with the stakeholder until they reconsider
- Insist on the project's position until the stakeholder yields
Correct answer: Reframe the conversation around shared goals and invite joint problem-solving to generate new options beyond the disputed points
When negotiation stalls, reframing around common objectives and collaboratively expanding the option set can unlock agreement without damaging trust. Refusing to move, going silent, or fully capitulating each sacrifice either the relationship or the project's legitimate interests.
- A team member is blocked because a required security review can only be performed by a single overloaded specialist with a multi-week backlog. What should the project manager do to remove this obstacle?
- Wait passively in the specialist's queue without intervention
- Skip the security review to keep the project moving
- Negotiate prioritization of the project's review with the specialist's manager and explore cross-training or additional reviewer capacity
- Have an untrained team member perform the security review
Correct answer: Negotiate prioritization of the project's review with the specialist's manager and explore cross-training or additional reviewer capacity
A capacity bottleneck is an obstacle the PM should actively remove by negotiating priority and pursuing capacity solutions like cross-training or added reviewers. Skipping a required security review, waiting passively, or assigning unqualified people introduces unacceptable risk and does not resolve the blocker properly.
- During negotiation of a project agreement, the project manager discovers the supplier misunderstood a key technical requirement, which would lead to a defective deliverable. What is the most appropriate action?
- Reduce the requirement to match the supplier's misunderstanding to avoid renegotiation
- Sign the agreement quickly before the supplier raises the price for the corrected requirement
- Let the supplier proceed on their misunderstanding and request rework later
- Pause to clarify the requirement and reach a shared understanding before finalizing the agreement so both parties commit to the correct scope
Correct answer: Pause to clarify the requirement and reach a shared understanding before finalizing the agreement so both parties commit to the correct scope
A negotiated agreement must rest on a shared, accurate understanding of scope; the PM should clarify before signing so commitments are correct. Exploiting the misunderstanding, allowing predictable rework, or quietly downgrading the requirement all produce a defective outcome and breach professional responsibility.
- A project manager maintains a visible impediment board so the team and stakeholders can see blockers. A senior stakeholder objects that publicly displaying problems makes the project look troubled. How should the PM respond?
- Keep the board but stop adding new impediments to it
- Explain that transparency surfaces obstacles early so they can be removed quickly, which protects delivery rather than signaling failure
- Move the board to a private location only the PM can see
- Take down the board to avoid upsetting the stakeholder
Correct answer: Explain that transparency surfaces obstacles early so they can be removed quickly, which protects delivery rather than signaling failure
Visible impediment tracking is a transparency practice that accelerates obstacle removal; the PM should explain this value rather than hide problems. Removing or privatizing the board, or ceasing to log blockers, undermines the team's ability to identify and clear impediments quickly.
- A project manager negotiates a memorandum of understanding with a partner organization. After agreement, the PM wants to ensure both sides honor their commitments throughout the project. What should the agreement include?
- A general expression of goodwill with no specific obligations
- An indefinite term with no checkpoints or review dates
- Only the partner organization's obligations, leaving the PM's side open
- Defined roles, responsibilities, measurable commitments, and a mechanism for monitoring and addressing non-performance
Correct answer: Defined roles, responsibilities, measurable commitments, and a mechanism for monitoring and addressing non-performance
A durable negotiated agreement specifies clear obligations for both parties and a way to monitor performance and handle shortfalls. Vague goodwill, one-sided obligations, or open-ended terms without checkpoints leave commitments unenforceable and make it hard to address non-performance.
- During a sprint, a developer is blocked waiting on a design decision that the product owner keeps deferring. The blocker has stalled two stories. As servant leader, what should the project manager do?
- Facilitate a focused decision session with the product owner to resolve the design choice and unblock the stories promptly
- Let the stories carry over to future sprints indefinitely without raising the issue
- Make the design decision unilaterally without the product owner
- Remove the blocked stories from the product backlog entirely
Correct answer: Facilitate a focused decision session with the product owner to resolve the design choice and unblock the stories promptly
A servant-leader PM removes blockers by facilitating timely decisions from the accountable party — here, getting the product owner to decide. Letting stories languish, overstepping the product owner's authority, or deleting needed backlog items all fail to resolve the impediment appropriately.
- A project manager is negotiating resource commitments with three functional managers in a planning meeting. To increase the chance everyone follows through, what should the PM do at the end of the negotiation?
- Confirm and document each party's specific commitments and have the managers explicitly agree to them before closing
- Assume verbal nods during the meeting are sufficient commitment
- Send the managers a list of demands after the meeting without prior agreement
- Let each manager decide later how much to contribute
Correct answer: Confirm and document each party's specific commitments and have the managers explicitly agree to them before closing
Closing a negotiation by confirming and documenting explicit, agreed commitments increases accountability and follow-through. Relying on ambiguous nods, issuing post-hoc demands, or leaving contributions open-ended produces unclear obligations and weakens the agreement reached.
- An impediment arises that the project manager can resolve internally but doing so would consume significant management reserve. Before acting, what should the PM consider?
- Ignoring the impediment to preserve the reserve regardless of impact
- Hiding the reserve drawdown from the sponsor to avoid scrutiny
- Whether resolving it internally is the most cost-effective option versus escalating or negotiating a shared solution, and the impact on reserves
- Spending the reserve immediately since the blocker must be cleared at any cost
Correct answer: Whether resolving it internally is the most cost-effective option versus escalating or negotiating a shared solution, and the impact on reserves
Removing impediments still requires judgment about cost-effectiveness and stewardship of project resources; the PM should weigh internal resolution against escalation or shared solutions and the reserve impact. Spending blindly, ignoring the blocker, or concealing reserve use all reflect poor stewardship and transparency.
- A project manager negotiating with a vendor senses rising tension as both sides repeat their positions. To keep the negotiation productive, what is the BEST move?
- Concede the disputed points to defuse the tension immediately
- Pause to acknowledge each side's concerns, separate the people from the problem, and refocus on objective criteria for a fair outcome
- Continue restating the project's position more firmly
- Raise the stakes by threatening to cancel the vendor relationship
Correct answer: Pause to acknowledge each side's concerns, separate the people from the problem, and refocus on objective criteria for a fair outcome
Principled negotiation separates people from the problem and uses objective criteria to reach fair agreements, which lowers tension and keeps talks productive. Threats, premature concession, and stubborn repetition each escalate conflict or sacrifice the project's interests without resolving the underlying issue.
- A blocker is reported: the team cannot deploy because they lack production access, which is controlled by an external operations group with a strict request process. The project manager has never engaged this group before. What is the BEST first step to remove the impediment?
- Identify and contact the operations group's intake owner to understand the access process and negotiate timely provisioning for the team
- Wait for the operations group to notice the project and offer access
- Have the team deploy through an unauthorized workaround to avoid the process
- Assume access cannot be obtained and descope the deployment
Correct answer: Identify and contact the operations group's intake owner to understand the access process and negotiate timely provisioning for the team
Removing a process-based obstacle starts with identifying the right owner and working through the legitimate channel to negotiate timely access. Unauthorized workarounds create security and compliance risk, descoping abandons project value, and waiting passively leaves the team blocked indefinitely.
- Midway through a system migration, the project manager notices the finance director has stopped attending steering meetings and rarely responds to status emails, though she was an enthusiastic supporter at kickoff. What should the project manager do FIRST to keep this stakeholder engaged?
- Meet with the finance director privately to reassess her current interest, concerns, and preferred communication approach
- Remove her from the steering committee distribution list since she is no longer participating
- Continue sending the same status reports and assume she will re-engage when a decision affects her
- Escalate her disengagement to the project sponsor and request that attendance be made mandatory
Correct answer: Meet with the finance director privately to reassess her current interest, concerns, and preferred communication approach
Stakeholder engagement needs change over the life of a project. The project manager should first reassess this stakeholder's evolving needs and expectations through direct dialogue before escalating, removing her, or assuming nothing has changed. Re-evaluating engagement needs is the core enabler of collaborating with stakeholders.
- A project manager is building an initial engagement approach and wants to understand which stakeholders can most strongly affect project outcomes and which are most affected by them. Which technique BEST supports tailoring engagement effort to each stakeholder?
- Sending every stakeholder the same detailed weekly report to ensure no one feels excluded
- Analyzing stakeholders using a power/interest grid to classify them and set engagement intensity accordingly
- Waiting until stakeholders raise concerns before deciding how much to engage them
- Engaging only the stakeholders who hold formal authority over the project budget
Correct answer: Analyzing stakeholders using a power/interest grid to classify them and set engagement intensity accordingly
A power/interest (or power/influence) grid lets the project manager classify stakeholders and tailor the intensity and style of engagement to each group. Uniform reporting wastes effort and ignores differing needs; limiting engagement to budget authorities or waiting for complaints fails to proactively manage engagement.
- Two key stakeholders give the project manager conflicting direction: the operations VP wants the new tool optimized for speed, while the compliance officer insists on additional approval gates that slow it down. Both are essential to project success. What is the project manager's BEST course of action?
- Default to the compliance officer's requirements since compliance overrides operational efficiency
- Facilitate a joint session to align both stakeholders' needs with the project's objectives and find a balanced solution
- Implement the operations VP's preference because operations is the primary end user of the tool
- Document both requests and let the sponsor unilaterally decide without involving the two stakeholders
Correct answer: Facilitate a joint session to align both stakeholders' needs with the project's objectives and find a balanced solution
Collaborating with stakeholders includes optimizing alignment between stakeholder needs and the project's objectives. Bringing both parties together to reconcile their interests against the project goals is preferable to arbitrarily favoring one, applying a blanket rule, or excluding them from the resolution.
- A vendor stakeholder has been skeptical of the project manager since a prior engagement went poorly. The project manager wants to influence this vendor to commit additional resources for a critical phase. What approach is MOST likely to succeed?
- Build trust first by reliably delivering on small commitments and being transparent before asking for the larger commitment
- Bypass the skeptical vendor contact and appeal directly to their executive for the resources
- Offer to overlook minor contract deviations in exchange for the additional resources
- Remind the vendor that the contract obligates cooperation and threaten escalation if they resist
Correct answer: Build trust first by reliably delivering on small commitments and being transparent before asking for the larger commitment
Influencing stakeholders to accomplish objectives depends on first building trust. Demonstrating reliability and transparency on smaller commitments earns the credibility needed for a larger ask. Threats, end-runs, and improper trades damage relationships and undermine influence.
- During execution, the project manager realizes that what the marketing stakeholder calls the 'launch date' and what the engineering stakeholder calls the 'launch date' are actually two different milestones, and this has caused repeated friction. What should the project manager do to resolve the recurring conflict?
- Break down the situation to identify the root cause of the misunderstanding, then align both groups on a single shared definition
- Ask the sponsor to mediate every future scheduling dispute between the two groups
- Treat each disagreement as it arises and re-explain the schedule each time it comes up
- Pick one definition and instruct both teams to adopt it without discussion to save time
Correct answer: Break down the situation to identify the root cause of the misunderstanding, then align both groups on a single shared definition
Building a shared understanding starts with breaking down the situation to find the root cause of the misunderstanding. Here the root cause is divergent definitions of a term; resolving that and establishing one shared definition prevents recurrence, unlike imposing a definition, repeatedly re-explaining, or escalating each instance.
- A project manager needs the design, legal, and finance teams to agree on the acceptance criteria for a deliverable, but each team has a different perspective on what 'done' means. Which action BEST helps the project manager reach a shared agreement?
- Survey all necessary parties, facilitate discussion of their views, and guide them toward consensus on the criteria
- Document each team's separate criteria and let each verify the deliverable against its own
- Take an anonymous vote and adopt whichever single definition receives the most support
- Have the design team set the criteria since they are responsible for producing the deliverable
Correct answer: Survey all necessary parties, facilitate discussion of their views, and guide them toward consensus on the criteria
Building shared understanding involves surveying all necessary parties to reach consensus on the project approach. Facilitating a discussion that brings perspectives together produces genuine alignment, whereas letting one team dictate, voting away dissent, or maintaining separate criteria leaves the misalignment unresolved.
- After a difficult negotiation, two stakeholder groups verbally agree on a revised integration approach during a meeting facilitated by the project manager. What should the project manager do to support the outcome of the parties' agreement?
- Consider the matter closed once the verbal agreement is reached and move on to the next issue
- Document the agreed approach, confirm it with both parties, and follow up to ensure the agreement is honored in practice
- Wait to see whether either party raises the issue again before recording anything
- Let each group implement its own interpretation of the agreement to maintain goodwill
Correct answer: Document the agreed approach, confirm it with both parties, and follow up to ensure the agreement is honored in practice
Supporting the outcome of parties' agreement means capturing what was agreed, confirming mutual understanding, and verifying it is upheld. A purely verbal agreement that is never documented or followed up is likely to erode, and allowing separate interpretations recreates the original misalignment.
- A project manager senses tension between the QA lead and the development lead but cannot pinpoint the issue; their interactions are polite yet unproductive. Before the situation escalates, what should the project manager do?
- Wait until the tension produces a measurable schedule impact before intervening
- Reassign one of the leads to a different project to eliminate the friction
- Publicly ask both leads in the next team meeting to explain why they are not cooperating
- Investigate the potential misunderstanding by speaking with each party to surface the underlying concern
Correct answer: Investigate the potential misunderstanding by speaking with each party to surface the underlying concern
Building shared understanding includes investigating potential misunderstandings before they grow. Proactively and privately surfacing the underlying concern lets the project manager address it early, unlike waiting for damage, removing a team member, or confronting them publicly, which can worsen the conflict.
- A project manager creates a stakeholder engagement assessment matrix that maps where each stakeholder currently is (Unaware, Resistant, Neutral, Supportive, Leading) versus where they need to be. The primary value of this matrix is that it helps the project manager:
- Permanently classify stakeholders so the same communications can be reused for the rest of the project
- Identify gaps between current and desired engagement so targeted actions can move stakeholders to the needed level
- Determine which stakeholders can be removed from the project to reduce communication overhead
- Rank stakeholders by seniority to decide whose requests receive priority
Correct answer: Identify gaps between current and desired engagement so targeted actions can move stakeholders to the needed level
The stakeholder engagement assessment matrix compares current versus desired engagement levels, revealing gaps so the project manager can plan targeted actions to close them. It is not a static label, a seniority ranking, or a tool for cutting stakeholders.
- A newly added executive stakeholder has a great deal of power but has shown little interest in the project so far. According to a power/interest classification, how should the project manager engage this stakeholder?
- Monitor them with minimal effort since their current interest is low
- Manage them closely with detailed daily reports because of their high power
- Keep them satisfied with periodic high-level updates while monitoring for shifts in their interest
- Keep them informed with the same general updates sent to low-power stakeholders
Correct answer: Keep them satisfied with periodic high-level updates while monitoring for shifts in their interest
High-power, low-interest stakeholders should be kept satisfied with appropriate-level engagement while watching for changes, since their power means rising interest could significantly affect the project. They do not warrant the close, detailed management reserved for high-power/high-interest stakeholders, nor the minimal effort given to low-power/low-interest stakeholders.
- A community group opposing a construction project has limited formal authority but strong media influence. The project manager wants to convert their resistance into at least neutral support. What is the MOST effective first step?
- Meet with the group to understand their concerns and identify shared interests that can align with project objectives
- Offer the group compensation in exchange for ending their public opposition
- Issue a public statement defending the project to counter their messaging
- Ignore them because they have no contractual or formal authority over the project
Correct answer: Meet with the group to understand their concerns and identify shared interests that can align with project objectives
Influencing and aligning a resistant stakeholder starts with understanding their concerns and finding common ground with project objectives. Ignoring an influential group, issuing combative statements, or attempting to buy silence are likely to deepen resistance and damage trust.
- Throughout the project, the project manager wants to ensure stakeholder needs and expectations stay aligned with project objectives even as conditions change. Which practice BEST achieves this on an ongoing basis?
- Delegating all expectation management to functional managers of each stakeholder
- Periodically revisiting stakeholder needs and the project objectives together, and adjusting engagement as either evolves
- Aligning expectations only at major milestones such as phase gates
- Locking stakeholder expectations during initiation so the baseline does not change
Correct answer: Periodically revisiting stakeholder needs and the project objectives together, and adjusting engagement as either evolves
Optimizing alignment between stakeholder needs and project objectives is continuous because both can shift. Regularly revisiting them and adjusting engagement keeps them aligned, whereas freezing expectations, aligning only at gates, or fully delegating the work fails to manage the dynamic relationship.
- Two departments repeatedly disagree on a process change, and each accuses the other of 'not understanding the requirements.' The project manager facilitates a session and discovers both departments are actually working from different versions of the requirements document. What was the true root cause of the conflict?
- A lack of motivation in one department to comply with the process change
- A personality clash between the two department leads that requires a team-building intervention
- An information gap caused by uncontrolled document versions, not a genuine disagreement about the requirements
- Insufficient authority of the project manager to enforce a single decision
Correct answer: An information gap caused by uncontrolled document versions, not a genuine disagreement about the requirements
Breaking down the situation revealed that the parties were not truly in disagreement; they were misaligned because of different document versions. The root cause is an information/version-control gap, so correcting it resolves the conflict. The other options misattribute the cause and would lead to ineffective interventions.
- A project manager is preparing to brief a diverse stakeholder group that includes a technical architect, a non-technical sponsor, and an end-user representative. To build a shared understanding of the proposed solution, the project manager should:
- Deliver one highly technical briefing so the architect is satisfied and let the others follow as best they can
- Tailor the message and level of detail to each audience while ensuring all converge on the same core understanding
- Provide only a high-level summary to everyone to avoid confusing the non-technical stakeholders
- Send separate briefings and avoid bringing the groups together to prevent disagreement
Correct answer: Tailor the message and level of detail to each audience while ensuring all converge on the same core understanding
Building shared understanding requires that diverse stakeholders reach the same core understanding, which is best achieved by tailoring detail to each audience while converging on common meaning. Catering only to one audience, oversimplifying for all, or keeping groups apart prevents genuine shared understanding.
- A stakeholder who was 'Supportive' on the engagement assessment matrix has recently become 'Resistant' after an organizational change reassigned her reporting line. What should the project manager do?
- Re-evaluate her current engagement needs and concerns, then adjust the engagement approach to address the change
- Assume the resistance is temporary and continue the existing engagement plan unchanged
- Report her changed attitude to her new manager and request that she be replaced
- Update the matrix to show 'Resistant' and reduce communication with her accordingly
Correct answer: Re-evaluate her current engagement needs and concerns, then adjust the engagement approach to address the change
A shift in engagement signals that the stakeholder's needs or context have changed. The project manager should reassess her concerns and adapt the approach to re-engage her. Merely recording the change and reducing contact, ignoring it, or trying to replace her does not address the underlying cause of the resistance.
- During a global program, the project manager observes that two regional teams interpret the same status term differently: one uses 'complete' to mean code-complete and the other to mean deployed-to-production. Which action BEST establishes a durable shared understanding?
- Facilitate agreement on a common glossary of status terms and confirm both teams adopt it going forward
- Direct each team to keep its own definition and translate between them in every report
- Have the project manager personally restate the true status whenever the term is used
- Standardize on the definition used by the larger of the two teams without consulting the other
Correct answer: Facilitate agreement on a common glossary of status terms and confirm both teams adopt it going forward
A shared glossary agreed by both parties removes the ambiguity at its source and is durable, supporting the outcome of the agreement. Maintaining separate definitions, relying on constant manual correction, or imposing one definition without consensus leaves the misunderstanding likely to recur.
- A project manager wants to influence a powerful but neutral stakeholder to actively champion the project. Which approach reflects building influence ethically and effectively?
- Wait passively for the stakeholder to recognize the project's value on their own
- Form an alliance with the stakeholder's rivals to pressure them into supporting the project
- Provide selective information that exaggerates the project's benefits to win their support
- Demonstrate how the project's success advances the stakeholder's own goals and consistently deliver on commitments to them
Correct answer: Demonstrate how the project's success advances the stakeholder's own goals and consistently deliver on commitments to them
Ethical influence is built by connecting the project to the stakeholder's interests and earning credibility through reliable delivery. Manipulating through rivalries, presenting misleading information, or passively waiting either damages trust or fails to advance engagement.
- Early in planning, the project manager identifies many stakeholders and limited time to engage them all individually. How should the project manager prioritize engagement effort?
- Postpone engagement until the stakeholder list is finalized and complete
- Classify stakeholders by their power and interest, then concentrate the most intensive engagement on the highest-priority groups
- Engage only stakeholders who have explicitly requested involvement
- Engage all stakeholders equally to guarantee fairness regardless of their influence on the project
Correct answer: Classify stakeholders by their power and interest, then concentrate the most intensive engagement on the highest-priority groups
With limited capacity, classifying stakeholders by power and interest allows the project manager to focus the most intensive engagement where it matters most. Treating everyone identically wastes scarce effort, engaging only volunteers misses key stakeholders, and postponing engagement risks early misalignment.
- A conflict between two stakeholder groups appears to be about budget allocation, but after probing, the project manager learns that one group simply feels its contributions have not been acknowledged. What is the project manager's BEST next step?
- Proceed to renegotiate the budget split since that was the stated point of conflict
- Split the disputed budget evenly to quickly end the disagreement
- Address the real underlying concern by recognizing the group's contributions, then revisit the budget discussion
- Escalate the budget dispute to the sponsor for a binding allocation decision
Correct answer: Address the real underlying concern by recognizing the group's contributions, then revisit the budget discussion
Breaking down the situation revealed that the stated conflict (budget) masked the true root cause (lack of recognition). Addressing the genuine concern resolves the friction; reacting only to the surface issue through renegotiation, escalation, or an even split treats the symptom rather than the cause.
- A project manager has reached a working agreement with a supplier stakeholder on revised delivery dates. Weeks later, delivery patterns suggest the supplier is reverting to the old schedule. To support the outcome of the agreement, the project manager should:
- Immediately issue a contract breach notice and escalate to procurement
- Wait until a deliverable is formally late before raising the issue with the supplier
- Follow up with the supplier, reference the documented agreement, and address the deviation collaboratively
- Quietly adjust the project schedule to absorb the supplier's old dates
Correct answer: Follow up with the supplier, reference the documented agreement, and address the deviation collaboratively
Supporting the outcome of an agreement includes monitoring adherence and addressing slippage early through the documented agreement and dialogue. A premature breach notice escalates unnecessarily, silently absorbing the slip undermines the agreement, and waiting for a formal failure forfeits the chance to correct course.
- A project manager is collaborating with a stakeholder whose expectations exceed what the approved scope can deliver. To realign expectations with project objectives, the project manager should:
- Defer the conversation indefinitely and hope the stakeholder lowers their expectations
- Tell the stakeholder their expectations are unrealistic and cannot be discussed
- Engage the stakeholder in an open discussion of scope constraints and the trade-offs of any changes they want
- Quietly try to deliver the extra expectations without informing the change control process
Correct answer: Engage the stakeholder in an open discussion of scope constraints and the trade-offs of any changes they want
Optimizing alignment between stakeholder needs and project objectives requires transparently discussing constraints and trade-offs so expectations and scope converge. Silently gold-plating bypasses change control, dismissing the stakeholder damages the relationship, and deferring the conversation lets misalignment persist.
- After multiple cross-team meetings, the project manager wants to confirm that all parties truly share the same understanding of a newly agreed escalation process, not just that they were present when it was discussed. What is the BEST way to verify shared understanding?
- Rely on the head nods observed during the meeting as confirmation of agreement
- Ask representatives from each group to restate the process in their own words and reconcile any differences
- Have each group sign an attendance sheet to record that they were informed
- Distribute the meeting minutes and assume agreement because no one objected
Correct answer: Ask representatives from each group to restate the process in their own words and reconcile any differences
Verifying shared understanding requires confirming that each party genuinely interprets the agreement the same way; having them restate it in their own words surfaces hidden gaps. Minutes, observed nods, or attendance records prove only that information was delivered, not that it was understood consistently.
- A key stakeholder repeatedly receives status information through informal hallway conversations and forms inaccurate impressions of project progress. How should the project manager collaborate to keep this stakeholder's understanding accurate?
- Add this stakeholder to the mass distribution list so they receive every project email
- Instruct team members to stop discussing the project in hallways to cut off the informal flow
- Establish a regular, agreed communication channel and cadence that meets this stakeholder's information needs
- Wait for the stakeholder to ask formal questions before providing any corrected information
Correct answer: Establish a regular, agreed communication channel and cadence that meets this stakeholder's information needs
Collaborating effectively means meeting a stakeholder's information needs through an agreed, appropriate channel and cadence so their understanding stays accurate. Trying to suppress informal talk is impractical, waiting for questions is reactive, and burying them in mass emails does not target their actual needs.
- Two stakeholders reach what the project manager believes is a clear agreement, but each later acts as if a different decision was made. This is the second time such a 'phantom agreement' has occurred. What should the project manager do to prevent recurrence?
- Ask the sponsor to attend all future meetings to enforce decisions
- Record all future meetings on video so the agreements can be reviewed later if disputed
- After each agreement, summarize the decision aloud, gain explicit confirmation from both parties, and document it
- Stop holding joint meetings and instead negotiate with each stakeholder separately
Correct answer: After each agreement, summarize the decision aloud, gain explicit confirmation from both parties, and document it
Phantom agreements arise when understanding is assumed rather than confirmed. Summarizing the decision, obtaining explicit confirmation, and documenting it ensures a real shared understanding and supports the agreement's outcome. Separate negotiations, sponsor enforcement, or recordings address symptoms but not the missing confirmation step.
- A project team is distributed across offices in three countries spanning 11 time zones. Team members in one region complain they are repeatedly asked to join late-night synchronous calls. What is the project manager's best approach to support this virtual team?
- Require the complaining region to adjust their personal schedules since they joined the project voluntarily
- Keep the meeting fixed at a time convenient for the project manager's home office so the schedule stays predictable
- Cancel all synchronous meetings and communicate exclusively through email going forward
- Rotate the meeting times so the burden of inconvenient hours is shared fairly across all regions and lean on asynchronous updates where possible
Correct answer: Rotate the meeting times so the burden of inconvenient hours is shared fairly across all regions and lean on asynchronous updates where possible
Supporting a virtual team across many time zones means distributing the inconvenience equitably (rotating meeting times) and maximizing asynchronous communication so no single region bears the burden. A fixed self-serving time, blaming members, or eliminating all real-time collaboration all damage engagement.
- During the kickoff of a fully remote project, the project manager wants to reduce the isolation that virtual team members often feel. Which action most directly addresses this risk?
- Schedule regular informal virtual social check-ins and create channels for non-work conversation alongside the formal meetings
- Limit communication to the project management tool to keep everything documented
- Assign each member more individual tasks so they stay too busy to feel disconnected
- Increase the frequency of formal status reports so members always know the project state
Correct answer: Schedule regular informal virtual social check-ins and create channels for non-work conversation alongside the formal meetings
Virtual teams lack the spontaneous interaction of co-located teams, which can create isolation. Deliberate informal social touchpoints and casual channels build relationships and belonging. More reports, heavier workloads, or restricting communication channels do not address the human connection gap.
- A project manager notices that two engineers on a virtual team have very different communication styles: one prefers detailed written messages, the other prefers quick video calls. Tension is rising over how work is coordinated. What should the project manager do first?
- Reassign one engineer to reduce the friction between the two
- Escalate the personality conflict to their functional managers for resolution
- Direct both engineers to use only written communication so there is always a record
- Facilitate a discussion where the team agrees on shared communication norms that accommodate both preferences
Correct answer: Facilitate a discussion where the team agrees on shared communication norms that accommodate both preferences
Differing communication preferences on a virtual team are best resolved by collaboratively establishing agreed norms (a ground-rules/engagement matter). Mandating one style ignores the other's needs, reassignment is premature, and escalation is unnecessary for a coordination issue the team can resolve itself.
- A project manager is forming a new virtual team and wants members to feel comfortable raising concerns despite never having met in person. Which practice best builds the psychological safety needed for an effective virtual team?
- Keep cameras off during meetings so quieter members are not put on the spot
- Model openness by inviting and acknowledging concerns early, and respond to mistakes as learning opportunities rather than blame
- Wait until the team has worked together for several months before encouraging open dialogue
- Have all concerns submitted anonymously through a suggestion box
Correct answer: Model openness by inviting and acknowledging concerns early, and respond to mistakes as learning opportunities rather than blame
Psychological safety on a virtual team is built when the leader actively models openness, welcomes concerns, and treats errors as learning. Cameras-off reduces engagement, anonymous-only channels signal distrust, and delaying open dialogue lets problems fester. Visible, early modeling is most effective.
- On a virtual team, the project manager observes that one member rarely contributes in synchronous meetings but produces high-quality written input afterward. What does this most likely indicate the project manager should do?
- Remove the member from synchronous meetings entirely
- Interpret the silence as disengagement and document a performance concern
- Provide multiple participation channels, including asynchronous written contribution, so the member can engage in their most effective way
- Insist the member speak up in every live meeting to ensure equal participation
Correct answer: Provide multiple participation channels, including asynchronous written contribution, so the member can engage in their most effective way
Effective virtual team support recognizes diverse engagement styles; offering both synchronous and asynchronous channels lets members contribute where they are strongest. Forcing live participation, excluding them, or assuming disengagement misreads a productive contributor and harms inclusion.
- A globally distributed virtual team is using a shared online collaboration platform, but members are saving files locally and emailing versions, causing confusion over which document is current. What ground rule would best resolve this?
- Switch back to email-only document sharing since members are comfortable with it
- Require the project manager to manually merge all emailed versions each day
- Ask each member to keep their own master copy and reconcile at milestones
- Establish a single source of truth on the shared platform that everyone must use, with agreed file-naming and version conventions
Correct answer: Establish a single source of truth on the shared platform that everyone must use, with agreed file-naming and version conventions
Version confusion on virtual teams is solved by a clear ground rule designating one authoritative shared location plus naming/version conventions. Manual daily merges are unsustainable, individual masters multiply the problem, and email-only sharing is the root cause of the confusion.
- A project manager leads a hybrid team where some members are co-located in an office and others are fully remote. During meetings, in-office members dominate discussion while remote members struggle to interject. What should the project manager do to create equity?
- Tell remote members to be more assertive about jumping into the conversation
- Record the meetings so remote members can review what they missed afterward
- Hold the important decision meetings only with the in-office group for efficiency
- Adopt a 'remote-first' meeting practice where everyone joins individually online and a facilitator actively invites remote voices
Correct answer: Adopt a 'remote-first' meeting practice where everyone joins individually online and a facilitator actively invites remote voices
In hybrid settings, in-room participants often dominate. A remote-first approach (everyone joins individually, facilitator deliberately invites remote input) levels participation. Telling remote members to be louder, excluding them from decisions, or only recording afterward all entrench the inequity.
- While supporting a newly virtual team, the project manager wants to ensure technology issues do not derail collaboration. What is the most proactive step to take?
- Confirm all members have access to and training on the agreed collaboration tools, and establish a backup communication method
- Standardize on the most advanced tool available regardless of members' bandwidth or skills
- Require all members to purchase identical hardware before the project starts
- Assume members will report problems if they arise and address issues reactively
Correct answer: Confirm all members have access to and training on the agreed collaboration tools, and establish a backup communication method
Proactively verifying tool access, providing training, and defining a backup channel prevents technology from blocking virtual collaboration. Reacting only after failures, mandating heavy tools that exceed members' capacity, or imposing hardware purchases create avoidable barriers.
- A virtual team member in a different culture consistently agrees verbally in meetings but then does not deliver as expected. The project manager suspects a cultural difference in how disagreement is expressed. What is the best response?
- Require all commitments to be reconfirmed in writing three times before acting on them
- Publicly call out the gap between agreement and delivery to enforce accountability
- Adapt the communication approach by using private follow-ups and open-ended questions that make it safe to surface concerns
- Assume the member is being deliberately deceptive and escalate immediately
Correct answer: Adapt the communication approach by using private follow-ups and open-ended questions that make it safe to surface concerns
Cultural norms vary in how openly disagreement is voiced. A culturally aware leader adapts by creating safe, private channels and open questions to surface real concerns. Public confrontation, assuming deceit, or burdensome triple-confirmation processes damage trust and ignore the cultural dynamic.
- A project manager is setting up a virtual team that will operate primarily asynchronously across continents. To keep work flowing smoothly without constant real-time coordination, which ground rule is most important?
- Define clear expected response-time windows for different message types so members know when replies are needed
- Mandate that all decisions wait for a weekly synchronous meeting
- Require every member to be online during the project manager's working hours
- Allow members to respond whenever convenient with no agreed expectations
Correct answer: Define clear expected response-time windows for different message types so members know when replies are needed
Asynchronous virtual teams depend on agreed response-time expectations so work is not blocked while still respecting time zones. Forcing overlap defeats the asynchronous model, funneling all decisions to one weekly call creates bottlenecks, and having no expectations leads to unpredictable delays.
- Midway through a virtual project, engagement in team meetings has dropped noticeably and members keep their cameras off and rarely speak. Before the project manager can fix the problem, what should they do first?
- Replace the underperforming team members with more engaged ones
- Gather honest feedback from the team about the meeting format and what is causing the disengagement
- Immediately mandate that all cameras be turned on in every meeting
- Reduce the number of meetings without understanding the cause
Correct answer: Gather honest feedback from the team about the meeting format and what is causing the disengagement
Declining engagement should first be understood through team feedback before acting. Mandating cameras treats a symptom, cutting meetings blindly may remove needed coordination, and replacing members is a drastic overreaction. Diagnosing the root cause enables the right intervention.
- A project manager is establishing team ground rules at the start of a new project. To maximize the team's commitment to those rules, how should they be created?
- Adopt the ground rules from a previous successful project without modification
- Write the ground rules personally and distribute them for the team to follow
- Facilitate the team in collaboratively developing the ground rules so members have ownership of them
- Have the sponsor dictate the ground rules to give them authority
Correct answer: Facilitate the team in collaboratively developing the ground rules so members have ownership of them
Ground rules are most effective when the team co-creates them, because shared ownership drives genuine commitment. A manager-authored, copied, or sponsor-imposed set of rules lacks buy-in, and members are far more likely to honor norms they helped define.
- Two months into the project, the team's agreed ground rules are being routinely ignored—meetings start late and action items go untracked. What is the project manager's best course of action?
- Revisit the ground rules with the team to understand why they are not working and revise them together as needed
- Abandon the ground rules since the team clearly will not follow them
- Begin penalizing individuals each time a ground rule is broken
- Take over enforcement personally and remind people of every violation
Correct answer: Revisit the ground rules with the team to understand why they are not working and revise them together as needed
When ground rules are not being followed, the team should revisit and refine them collaboratively, since rules may be unrealistic or no longer fit. Penalizing, abandoning, or unilaterally policing them ignores the underlying issue and undermines the team-ownership that makes ground rules work.
- During ground-rule setting, the team is debating how decisions will be made when consensus cannot be reached. What is the most useful element to include in the ground rules?
- A rule that all decisions must be unanimous regardless of how long it takes
- A pre-agreed escalation and decision-making path so the team knows how unresolved issues will be settled
- A statement that the project manager alone makes every decision
- A rule that disagreements will simply be avoided to keep harmony
Correct answer: A pre-agreed escalation and decision-making path so the team knows how unresolved issues will be settled
Good ground rules anticipate deadlock by defining how decisions are made and escalated when consensus fails. Mandatory unanimity stalls progress, sole top-down decisions disempower the team, and avoiding disagreement suppresses the healthy conflict needed for good decisions.
- A project manager wants the team's ground rules to remain useful as the project evolves through different phases. How should the ground rules be treated?
- As a living agreement the team reviews and adjusts periodically to stay relevant
- As a fixed contract that cannot change once signed at kickoff
- As guidelines only for new members, not the existing team
- As an informal understanding that need not be documented
Correct answer: As a living agreement the team reviews and adjusts periodically to stay relevant
Ground rules are most valuable as a living document the team revisits and updates as circumstances change. Treating them as immutable, leaving them undocumented, or applying them only to newcomers reduces their relevance and the team's shared accountability over time.
- A new member joins an established team that has been operating under agreed ground rules for several months. What is the best way to integrate the newcomer with respect to those rules?
- Expect the new member to observe the team for a while and infer the unwritten rules
- Walk the new member through the existing ground rules and invite their input in case any should be updated
- Have the new member sign the ground rules without discussion to save time
- Suspend the ground rules until the new member is fully up to speed
Correct answer: Walk the new member through the existing ground rules and invite their input in case any should be updated
Onboarding a new member to ground rules means explaining them and inviting input, which both clarifies expectations and keeps the rules current. Letting them infer norms invites missteps, a no-discussion signature lacks understanding, and suspending the rules destabilizes the whole team.
- While defining ground rules, the team is unsure whether to include norms about respectful behavior and how to handle disagreements. What is the best guidance for the project manager to give?
- Leave behavior to individual judgment since adults should know how to behave
- Limit ground rules strictly to logistics like meeting times and tool usage
- Defer behavioral norms to the organization's HR policy instead
- Include behavioral and conflict-handling norms, since ground rules should cover how the team interacts, not only logistical procedures
Correct answer: Include behavioral and conflict-handling norms, since ground rules should cover how the team interacts, not only logistical procedures
Ground rules appropriately address both logistics and interpersonal norms—how the team communicates, resolves conflict, and treats one another. Restricting them to logistics, relying on individual judgment, or deferring entirely to HR misses the team-interaction foundation that ground rules are meant to establish.
- A project manager is leading a virtual team and notices that decisions made in chat threads are getting lost, and members later disagree about what was decided. What ground rule would best prevent this?
- Require that all decisions be captured in a designated decision log accessible to the whole team
- Move all decision-making into longer synchronous calls only
- Have the project manager keep a private record of decisions to consult when disputes arise
- Ask members to remember decisions and raise objections from memory later
Correct answer: Require that all decisions be captured in a designated decision log accessible to the whole team
A ground rule that decisions be logged in a shared, accessible decision record creates a single transparent reference, preventing 'who decided what' disputes. Relying on memory, forcing everything into calls, or keeping a private log all fail to give the team a visible shared source of truth.
- A virtual team spanning several regions is experiencing friction because members interpret deadlines differently—some assume their local time zone, others the project manager's. What is the most effective ground rule to establish?
- Have the project manager personally convert every deadline for each member
- Let each member assume their own local time zone applies to deadlines
- Set all deadlines without times, only dates, to avoid the issue
- Standardize on a single reference time zone (or always state the time zone explicitly) for all deadlines and meetings
Correct answer: Standardize on a single reference time zone (or always state the time zone explicitly) for all deadlines and meetings
Deadline ambiguity across time zones is resolved by a ground rule that fixes one reference time zone or requires explicit time-zone notation. Allowing local assumptions perpetuates confusion, date-only deadlines remain ambiguous about cutoff, and manual per-member conversion is unscalable and error-prone.
- A project manager supporting a virtual team wants members in different locations to feel like one cohesive team rather than separate sub-groups. Which approach best fosters this unity?
- Communicate primarily with each location's lead and let leads relay to their groups
- Allow each location to work independently and only integrate deliverables at the end
- Hold separate meetings for each location to respect their working hours
- Create cross-location pairings and shared goals so members collaborate across sites rather than only within their local group
Correct answer: Create cross-location pairings and shared goals so members collaborate across sites rather than only within their local group
Cohesion in distributed teams grows when members collaborate across locations toward shared goals, breaking down site silos. Independent work, leader-only relay communication, and fully separate meetings all reinforce sub-group identities and undermine the sense of one unified team.
- During virtual team meetings, a few members frequently multitask and miss key points, then ask for repeats that slow everyone down. The team agrees this is a problem. What is the most constructive ground rule to adopt?
- Have the project manager call on distracted members publicly to keep them alert
- Forbid anyone from ever asking a clarifying question during meetings
- Require all members to keep cameras on at all times to monitor attention
- Agree to a shared expectation of focused presence during meetings, supported by concise agendas and shorter meetings
Correct answer: Agree to a shared expectation of focused presence during meetings, supported by concise agendas and shorter meetings
A ground rule promoting focused presence, paired with tight agendas and shorter meetings, addresses multitasking respectfully and reduces the meeting burden that invites distraction. Banning clarifying questions, mandatory surveillance, and public shaming are punitive and erode trust without solving the underlying cause.
- A project manager is establishing ground rules for how the virtual team will give and receive feedback to one another. What characteristic of the feedback ground rule will make it most effective?
- Feedback should be saved for formal performance reviews to avoid daily friction
- Feedback should only flow from the project manager downward to team members
- Feedback should be specific, timely, and focused on behavior or work rather than personal attributes
- Feedback should always be given publicly so the whole team can learn from it
Correct answer: Feedback should be specific, timely, and focused on behavior or work rather than personal attributes
Effective feedback norms emphasize being specific, timely, and behavior-focused. Restricting feedback to top-down only removes peer learning, deferring it to formal reviews loses timeliness, and mandating all feedback be public ignores that corrective feedback is often best delivered privately.
- A virtual team has set ground rules, but the project manager realizes nothing was agreed about how and when members should be reachable outside of scheduled meetings. Members are messaging each other at all hours, causing burnout concerns. What should the project manager facilitate?
- No rule, since adults can manage their own boundaries individually
- A rule that members only communicate during the project manager's office hours
- A ground rule defining reasonable availability and 'right to disconnect' expectations that respect members' time zones and personal time
- A rule requiring all members to be reachable at any time to maximize responsiveness
Correct answer: A ground rule defining reasonable availability and 'right to disconnect' expectations that respect members' time zones and personal time
Across time zones, an availability and right-to-disconnect ground rule protects members from after-hours pressure and burnout while setting clear expectations. Demanding constant reachability harms wellbeing, restricting to one person's hours ignores distribution, and no rule leaves the burnout-inducing free-for-all unaddressed.
- A project manager observes that the virtual team's ground rules are well-written but team members do not seem to refer to them or apply them in practice. What is the most likely root cause to investigate first?
- Whether the rules were approved by the project sponsor
- Whether the rules document uses a sufficiently formal font and layout
- Whether the team genuinely participated in creating the rules and sees them as their own
- Whether enough rules were written to cover every possible situation
Correct answer: Whether the team genuinely participated in creating the rules and sees them as their own
Ground rules that go unused most often lack genuine team ownership, so the first thing to examine is whether the team truly co-created and embraced them. Formatting, sponsor approval, and exhaustive coverage do not drive adherence—shared ownership and buy-in do.
- A project manager notices that a talented junior analyst consistently produces strong technical work but avoids speaking up in stakeholder meetings, limiting her growth into a future lead role. Rather than assigning her additional tasks, the project manager begins meeting with her weekly to discuss her career goals, offers feedback on her presentation skills, and gradually introduces her to senior stakeholders. What is the project manager primarily doing?
- Delegating authority so the project manager can reduce his own workload
- Mentoring the team member to develop her long-term capabilities and confidence
- Performing a formal performance appraisal tied to compensation
- Resolving an interpersonal conflict between the analyst and stakeholders
Correct answer: Mentoring the team member to develop her long-term capabilities and confidence
Mentoring focuses on the long-term professional development of an individual, including guidance, feedback, and exposure to growth opportunities. It is distinct from delegation, formal appraisals, or conflict resolution because its core aim is developing the person's capabilities and confidence over time.
- During a one-on-one mentoring session, a project manager recognizes that the mentee is becoming defensive when receiving feedback about missed deadlines. The project manager pauses, acknowledges that the timeline pressure has been intense, and asks the mentee how she is feeling about her workload before continuing. Which emotional intelligence competency is the project manager demonstrating?
- Intrinsic motivation aligned with project objectives
- Self-assessment of his own leadership style
- Empathy combined with social awareness of the mentee's emotional state
- Self-regulation by suppressing his own frustration entirely
Correct answer: Empathy combined with social awareness of the mentee's emotional state
Recognizing and responding to another person's emotions reflects empathy and social awareness, two components of emotional intelligence. Self-regulation governs one's own reactions, motivation is about internal drive, and self-assessment concerns understanding oneself rather than reading the mentee's emotions.
- A project manager leading a newly formed team realizes that members have very different communication styles, with some dominating discussions and others withdrawing. Before the next session, the project manager reflects on how his own assertive style may be discouraging quieter members and decides to consciously create space for them to contribute. This self-awareness leading to behavioral change is best described as which combination of emotional intelligence skills?
- Self-awareness followed by self-management
- Social awareness followed by motivation
- Self-assessment followed by conflict avoidance
- Empathy followed by relationship management
Correct answer: Self-awareness followed by self-management
Recognizing how one's own behavior affects others is self-awareness; deliberately adjusting that behavior is self-management (self-regulation). The other options either start from understanding others (social awareness/empathy) or misname the regulatory action.
- A senior stakeholder asks the project manager to help a newly promoted product owner who is struggling to translate strategic vision into actionable backlog items. The project manager agrees to share lessons from past projects, role-play prioritization conversations, and review the product owner's decisions without taking over. What is the project manager's role in this arrangement?
- Sponsor who provides funding and political cover
- Mentor who transfers knowledge and builds the product owner's judgment
- Functional manager who directs the product owner's daily work
- Scrum master who enforces the team's process
Correct answer: Mentor who transfers knowledge and builds the product owner's judgment
Sharing experience, coaching judgment, and reviewing decisions without taking control is mentoring. A sponsor provides resources and authority, a functional manager directs work, and a scrum master facilitates process; none describe the knowledge-transfer relationship shown here.
- A project manager observes that whenever a critical defect is reported, one team lead reacts with visible anger, raises his voice, and sends accusatory messages, which damages team morale. The project manager wants to help this lead grow. As part of mentoring, what should the project manager focus the conversation on first?
- Reassigning the defect-prone work to a different team entirely
- Removing the lead from any defect-related communications permanently
- Documenting the behavior for a disciplinary escalation to HR
- Helping the lead recognize his emotional triggers and develop self-regulation strategies
Correct answer: Helping the lead recognize his emotional triggers and develop self-regulation strategies
Developing emotional intelligence in others, especially self-awareness of triggers and self-regulation, addresses the root behavioral issue. Removing or reassigning work avoids growth, and an immediate HR escalation is premature when a developmental mentoring approach is appropriate and could resolve the behavior.
- A project manager is mentoring two stakeholders simultaneously: a vendor account manager who needs help understanding the project's governance, and a junior internal coordinator who needs help building stakeholder relationships. The project manager realizes the time investment is becoming significant. To mentor effectively across multiple relevant stakeholders, what should the project manager do?
- Delegate all mentoring to the sponsor to free up the project manager's time
- Prioritize and tailor the mentoring focus to each stakeholder's specific development needs and the project's benefit
- Provide identical generic mentoring to both to ensure fairness
- Stop mentoring the external vendor because mentoring is only for internal staff
Correct answer: Prioritize and tailor the mentoring focus to each stakeholder's specific development needs and the project's benefit
Effective mentoring of relevant stakeholders is individualized and prioritized based on each person's needs and the value to the project. Identical generic content ignores individual needs, mentoring is not restricted to internal staff, and abdicating it to the sponsor abandons the project manager's responsibility.
- A high-performing engineer on the team has begun missing meetings and producing lower-quality work. In a private conversation, the project manager learns the engineer is caring for an ill family member. The project manager expresses genuine concern, adjusts expectations temporarily, and connects him to employee assistance resources. Which emotional intelligence application is most evident?
- Using self-motivation to push the engineer to maintain output
- Using empathy to understand the situation and relationship management to respond supportively
- Using self-awareness to evaluate the project manager's own stress
- Using self-regulation to ignore the personal issue and focus on deliverables
Correct answer: Using empathy to understand the situation and relationship management to respond supportively
Understanding the engineer's circumstances reflects empathy, and responding with support and resources reflects relationship management. The other options either push output inappropriately, focus on the manager's own emotions, or dismiss the human situation entirely.
- While mentoring a future project manager, the experienced PM is asked, 'What is the best way to handle a stakeholder who keeps changing requirements?' Rather than giving a single prescriptive answer, the mentor asks questions to help the mentee analyze the stakeholder's underlying motivations and arrive at her own solution. Why is this approach appropriate for mentoring?
- It allows the mentor to avoid responsibility for the mentee's decisions
- It develops the mentee's critical-thinking and problem-solving skills for future independence
- It is faster than directly answering the question
- It ensures the mentee always reaches the same conclusion as the mentor
Correct answer: It develops the mentee's critical-thinking and problem-solving skills for future independence
A core purpose of mentoring is to build the mentee's independent reasoning and judgment, so a Socratic, question-driven approach develops lasting skills. It is not about avoiding responsibility, is rarely faster, and is not intended to force identical conclusions.
- A project manager senses rising tension during a planning workshop: arms crossing, terse replies, and side conversations. Even though no one has voiced a complaint, the project manager calls a short break and privately checks in with two members. The ability to perceive unspoken emotional cues in the group is which emotional intelligence competency?
- Self-awareness of the project manager's own anxiety
- Self-regulation of the project manager's reactions
- Social awareness, specifically reading the emotional climate of the group
- Intrinsic motivation toward project goals
Correct answer: Social awareness, specifically reading the emotional climate of the group
Perceiving the unstated emotional and nonverbal signals of a group is social awareness. Self-awareness concerns one's own emotions, self-regulation concerns managing them, and motivation concerns internal drive, none of which describe sensing the group's mood.
- A project manager is coaching a team member who wants to become a scrum master but lacks facilitation confidence. The project manager arranges for the member to co-facilitate retrospectives, debriefs with her afterward, and gradually steps back as her skills improve. This deliberate, phased transfer of facilitation responsibility is an example of what?
- Mentoring through progressively delegated practice and reflective feedback
- Avoiding accountability by handing off facilitation duties
- Conducting a formal capability gap assessment for staffing
- Micromanaging the team member's every facilitation move
Correct answer: Mentoring through progressively delegated practice and reflective feedback
Gradually increasing responsibility paired with reflective feedback is a hallmark of developmental mentoring. Micromanagement would mean controlling each action, abandoning facilitation would not include the coaching debriefs, and this is not a formal staffing assessment.
- During a heated discussion about scope, the project manager feels his own irritation rising as a stakeholder repeatedly interrupts. Instead of reacting sharply, he takes a breath, keeps his tone neutral, and restates the stakeholder's concern to keep the conversation productive. Which emotional intelligence skill is he exercising in that moment?
- Self-regulation by managing his own emotional response under pressure
- Empathy by recognizing the stakeholder's hidden agenda
- Relationship management by reassigning the stakeholder
- Social awareness by reading the room's mood
Correct answer: Self-regulation by managing his own emotional response under pressure
Controlling one's own emotional impulses to maintain a productive response is self-regulation (self-management). Empathy and social awareness involve understanding others, and reassigning a stakeholder is neither relationship management nor an in-the-moment emotional control behavior.
- A project manager wants to grow the leadership capacity of several team members so the team becomes more self-sufficient. He pairs less-experienced members with seasoned ones, encourages knowledge-sharing sessions, and recognizes those who mentor others. What is the broader benefit of fostering this mentoring culture on the project?
- It guarantees the project will finish ahead of schedule
- It increases team capability, retention, and resilience by spreading knowledge and developing future leaders
- It eliminates the need for the project manager to communicate with stakeholders
- It removes the requirement to track individual performance
Correct answer: It increases team capability, retention, and resilience by spreading knowledge and developing future leaders
A mentoring culture builds collective capability, improves engagement and retention, and develops future leaders, strengthening the team. It does not replace stakeholder communication, guarantee schedule outcomes, or eliminate performance tracking.
- A project manager is mentoring a stakeholder from another department who will eventually take over a portion of the project's operational responsibilities. The stakeholder is initially resistant, feeling the mentoring implies she is underperforming. How should the project manager best handle this?
- Discontinue mentoring since the stakeholder is uncomfortable
- Report the stakeholder's resistance to her manager as a performance concern
- Reframe the mentoring as a collaborative knowledge-transfer partnership focused on her success and the project's continuity
- Insist on the mentoring sessions regardless of how she feels
Correct answer: Reframe the mentoring as a collaborative knowledge-transfer partnership focused on her success and the project's continuity
Reframing mentoring as a mutual, success-oriented partnership addresses the stakeholder's concern about being judged and preserves the relationship. Discontinuing abandons a valuable transfer, reporting her damages trust, and insisting without addressing her feelings ignores emotional intelligence.
- A project manager keeps a personal habit of pausing at the end of each week to reflect on which of his interactions went well, where he felt frustrated, and how his mood affected the team. This ongoing practice most directly strengthens which foundational emotional intelligence competency?
- Social awareness of organizational politics
- Relationship management across the project team
- Self-awareness of his own emotions, strengths, and their impact on others
- Empathy toward the broader stakeholder community
Correct answer: Self-awareness of his own emotions, strengths, and their impact on others
Regular reflection on one's own emotions and their effects builds self-awareness, the foundation of emotional intelligence. Empathy, relationship management, and social awareness are outward-facing competencies, not the inward self-reflection described.
- A mentee tells the project manager, 'I want to lead my own project someday, but I freeze when I have to give difficult news to executives.' To help the mentee develop, the project manager shares a framework for structuring tough messages and then has the mentee practice delivering one in a low-stakes setting before a real situation arises. What mentoring principle does this illustrate?
- Delivering the difficult news on the mentee's behalf to spare her
- Shielding the mentee from all difficult conversations indefinitely
- Providing safe opportunities to practice and build competence before high-stakes application
- Evaluating the mentee's readiness through a formal certification exam
Correct answer: Providing safe opportunities to practice and build competence before high-stakes application
Mentoring often involves creating low-risk practice opportunities so the mentee can build skill and confidence before facing real high-stakes situations. Shielding her prevents growth, doing it for her removes the learning, and a certification exam is not the developmental practice described.
- A project manager notices that team members rarely admit when they are struggling, which leads to surprises late in the schedule. The project manager begins openly acknowledging his own uncertainties and mistakes in meetings to normalize candor. By modeling vulnerability and self-awareness, what is the project manager primarily building?
- A competitive ranking of team members by reliability
- A formal escalation policy for late deliverables
- A justification for reducing the number of status meetings
- Psychological safety that encourages team members to surface problems early
Correct answer: Psychological safety that encourages team members to surface problems early
When a leader models openness about uncertainty and mistakes, it builds psychological safety, encouraging others to raise issues early. This is an emotional-intelligence-driven behavior, not a formal policy, a meeting reduction, or a ranking system.
- During mentoring, an experienced project manager realizes the mentee learns best through visual examples rather than written explanations. The mentor adapts by using diagrams and walkthroughs instead of lengthy documents. What does adapting the mentoring approach to the mentee's learning style demonstrate?
- Avoiding accountability for the mentee's progress
- Tailoring mentoring to the individual to maximize their development
- An attempt to reduce the mentor's preparation effort
- A lack of structure in the mentoring relationship
Correct answer: Tailoring mentoring to the individual to maximize their development
Adjusting methods to fit how the mentee learns best is individualized, effective mentoring that maximizes development. It reflects deliberate care rather than a lack of structure, reduced effort, or avoidance of accountability.
- A project manager who scores high in emotional intelligence is known for staying composed during crises, reading stakeholder moods accurately, and rebuilding trust after conflicts. Senior leadership asks why this matters for project outcomes. What is the strongest project-related justification?
- Emotional intelligence eliminates the need for a project schedule
- Emotional intelligence replaces the need for technical project management skills
- Emotional intelligence guarantees that no conflicts will ever arise
- High emotional intelligence improves leadership effectiveness, team engagement, and stakeholder relationships, which support project success
Correct answer: High emotional intelligence improves leadership effectiveness, team engagement, and stakeholder relationships, which support project success
Emotional intelligence enhances a leader's ability to motivate teams, manage relationships, and navigate conflict, all of which contribute to project success. It does not replace scheduling, eliminate conflict, or substitute for technical skills.
- A project manager is mentoring a team member toward a leadership role and notices the mentee is ready for more responsibility but hesitant to claim it. The project manager publicly recognizes the mentee's contributions and recommends her to lead a small initiative. What outcome is the project manager seeking through this mentoring action?
- Transferring the project manager's accountability for the initiative
- Empowering the mentee by building her confidence and visibility for growth
- Testing whether the mentee will fail under pressure
- Reducing the project manager's own visibility with leadership
Correct answer: Empowering the mentee by building her confidence and visibility for growth
Recognizing contributions and creating leadership opportunities empowers the mentee and advances her development, a key mentoring goal. It is not about offloading accountability, setting her up to fail, or diminishing the project manager's standing.
- A project manager facilitates a difficult retrospective where two members openly blame each other. Drawing on emotional intelligence, the project manager first names the tension calmly, acknowledges each person's frustration, and then redirects the group toward shared goals. Which sequence of emotional intelligence competencies did the project manager apply?
- Empathy, then delegation of the conflict to HR
- Self-motivation, then self-assessment of personal performance
- Self-regulation, then avoidance of the underlying issue
- Social awareness to perceive the tension, then relationship management to guide the group constructively
Correct answer: Social awareness to perceive the tension, then relationship management to guide the group constructively
Perceiving and naming the group's tension is social awareness; acknowledging emotions and steering toward shared goals is relationship management. The other options misorder or misidentify the competencies and include avoidance or delegation that the scenario does not involve.
- An experienced project manager is asked to mentor a peer who was recently assigned a struggling project. The peer is the same level and somewhat sensitive about needing help. To make the mentoring relationship effective, what should the project manager prioritize?
- Reporting the peer's struggles to their shared sponsor
- Asserting authority to ensure the peer follows all recommendations
- Limiting interaction to formal written guidance only
- Establishing mutual trust and a non-judgmental, confidential rapport
Correct answer: Establishing mutual trust and a non-judgmental, confidential rapport
Trust, confidentiality, and a non-judgmental tone are essential to any mentoring relationship, especially with a sensitive peer. Asserting authority is inappropriate among peers, reporting struggles breaches trust, and restricting to written guidance limits the relationship's value.
- A project manager realizes that when she is under stress she tends to become curt and stop sharing context with the team, which erodes trust. She begins setting reminders to deliberately communicate more openly during high-pressure periods. This deliberate counter-behavior best reflects the application of which two emotional intelligence components together?
- Self-awareness of her stress pattern and self-management to alter the behavior
- Social awareness and conflict avoidance
- Relationship management and intrinsic motivation
- Empathy for the team and social awareness of their needs
Correct answer: Self-awareness of her stress pattern and self-management to alter the behavior
Recognizing her own stress-driven pattern is self-awareness, and intentionally changing her behavior is self-management. The other pairings involve outward-focused competencies that do not match recognizing and regulating one's own internal pattern.
- A project manager is mentoring a junior team member and, over several months, sees the member grow capable of handling tasks independently. To continue the member's growth appropriately, what should the project manager do as the relationship matures?
- Abruptly end all contact once the member shows competence
- Shift to formally evaluating the member's compensation and ranking
- Gradually reduce direct guidance and encourage greater autonomy while remaining available for support
- Continue providing the same level of detailed direction indefinitely
Correct answer: Gradually reduce direct guidance and encourage greater autonomy while remaining available for support
As a mentee matures, effective mentoring shifts toward greater autonomy with support available as needed. Maintaining the same intensity stalls growth, abrupt withdrawal undermines the relationship, and formal compensation evaluation is a management function, not mentoring.
- In a stakeholder review, the project manager perceives that the client's discomfort is not about the data being presented but about feeling excluded from earlier decisions. The project manager addresses the underlying feeling directly and adjusts the engagement approach. The ability to accurately interpret what a stakeholder is really feeling beneath their words is best described as which emotional intelligence skill?
- Motivation to complete the review quickly
- Self-awareness of the project manager's reaction
- Self-regulation under stakeholder pressure
- Empathy, the accurate understanding of another's emotions and perspective
Correct answer: Empathy, the accurate understanding of another's emotions and perspective
Accurately sensing and understanding another person's true feelings and perspective is empathy. The other options concern the project manager's own emotions, control of them, or personal drive, not the interpretation of the stakeholder's underlying emotional state.
- A project sponsor asks the project manager to choose a delivery approach for a new product. The requirements are well understood and unlikely to change, regulatory documentation must be produced at defined gates, and the customer expects a single final delivery. Which approach best fits these conditions?
- An adaptive (agile) approach delivering small increments every two weeks
- A predictive (plan-driven) approach with phase gates and detailed up-front planning
- A purely iterative approach that reworks the entire scope each cycle
- A hybrid approach where requirements emerge through frequent customer demos
Correct answer: A predictive (plan-driven) approach with phase gates and detailed up-front planning
Stable, well-understood requirements, gated regulatory documentation, and a single final handover are the classic indicators for a predictive life cycle. Adaptive and hybrid approaches are better suited to evolving requirements and incremental delivery, so they do not match the described conditions.
- Midway through tailoring the delivery approach, a team realizes part of the work (a mobile UI) has uncertain, evolving requirements while another part (a payments backend) is highly regulated and stable. What is the most appropriate way to structure the approach?
- Use a hybrid approach: adaptive for the evolving UI work and predictive for the stable, regulated backend
- Force the entire project into a single predictive plan to keep governance simple
- Delay the project until all requirements across both components are fully fixed
- Run everything as agile so the team can change anything at any time
Correct answer: Use a hybrid approach: adaptive for the evolving UI work and predictive for the stable, regulated backend
When different components have different levels of uncertainty and constraint, tailoring a hybrid approach lets each part use the most suitable life cycle. Forcing one approach across both ignores the differing characteristics, and delaying does not resolve the inherent uncertainty in the UI work.
- During project initiation, a PMO requires the project manager to document why a particular blend of practices was selected. What is the primary purpose of tailoring the approach and practices to this specific project?
- To guarantee the project will finish ahead of its original baseline schedule
- To fit the methodology to the project's context, complexity, and constraints rather than applying a one-size-fits-all process
- To reduce the amount of documentation the project manager must produce for the PMO
- To eliminate the need for stakeholder engagement during planning
Correct answer: To fit the methodology to the project's context, complexity, and constraints rather than applying a one-size-fits-all process
Tailoring adapts processes, tools, and practices to the unique needs of the project rather than applying a rigid standard. It is not primarily about reducing paperwork, accelerating the schedule, or removing stakeholder engagement, all of which remain context-dependent.
- A newly assigned project manager inherits a complex program with many interdependent components, contracts, and regulatory deadlines. Before detailed planning, what should the project manager do first to ensure the plan components fit together coherently?
- Immediately publish the schedule baseline so the team can begin executing tasks
- Lock the budget before any scope or schedule analysis is performed
- Integrate the planning activities so the scope, schedule, budget, risk, and resource plans are consolidated and consistent with one another
- Outsource the entire planning effort to the contracted vendors
Correct answer: Integrate the planning activities so the scope, schedule, budget, risk, and resource plans are consolidated and consistent with one another
Integrating planning activities ensures the subsidiary plans are reconciled and mutually consistent, which is essential on complex, interdependent work. Publishing a schedule, outsourcing planning, or locking a budget before integrating the components risks internal contradictions in the plan.
- While consolidating subsidiary plans, the project manager finds that the schedule assumes resources that the resource plan does not provide, and the budget does not fund the planned risk responses. What does this situation most directly indicate?
- The subsidiary plans are not integrated, so the plan components must be reconciled before the baseline is set
- The schedule is automatically correct because it was built first
- The project should proceed because each individual plan is internally complete
- The risk responses should be removed to match the existing budget
Correct answer: The subsidiary plans are not integrated, so the plan components must be reconciled before the baseline is set
Conflicts between the schedule, resource, and budget plans show a lack of integration. The correct action is to reconcile the components so they are consistent, not to proceed with contradictions, arbitrarily cut risk responses, or assume one plan overrides the others.
- A stakeholder questions how all the project's separate plans (scope, quality, communications, risk, procurement) come together into a single governing document. Which artifact serves this integrating role?
- The risk register, which lists identified risks and their responses
- The stakeholder engagement assessment matrix
- The project charter, which authorizes the project and names the project manager
- The project management plan, which consolidates the subsidiary plans and baselines into one integrated whole
Correct answer: The project management plan, which consolidates the subsidiary plans and baselines into one integrated whole
The project management plan integrates all subsidiary plans and the scope, schedule, and cost baselines into one coherent document. The charter authorizes the project, the risk register tracks risks, and the engagement matrix tracks stakeholders, but none of these consolidates all subsidiary plans.
- A project is approved and the team is ready to begin building deliverables. Senior leadership stresses that the work exists to deliver measurable business value as quickly as responsibly possible. What should guide how the project manager sequences and executes the work?
- Execute tasks strictly in the order they appear in the work breakdown structure
- Defer any value delivery until the entire scope is fully complete
- Prioritize and execute the work that delivers the highest business value early, balancing value with risk and constraints
- Focus first on the lowest-effort tasks regardless of the value they produce
Correct answer: Prioritize and execute the work that delivers the highest business value early, balancing value with risk and constraints
Executing with a sense of urgency for business value means sequencing work to deliver high-value outcomes early while balancing risk and constraints. Following the WBS order mechanically, deferring all value to the end, or chasing easy tasks ignores the value-driven intent.
- An adaptive team has a long product backlog and limited capacity in the next iteration. The product owner wants the most business value realized soon. How should the project manager support execution that delivers value with urgency?
- Have the team work on every backlog item a little at a time so nothing is left out
- Wait for the full backlog to be finalized before delivering any increment
- Let the team self-select the easiest stories to maximize the number completed
- Help the team deliver the highest-priority, highest-value backlog items first in the upcoming increment
Correct answer: Help the team deliver the highest-priority, highest-value backlog items first in the upcoming increment
Delivering the highest-value backlog items first realizes business value early, which is the goal of executing with urgency. Spreading effort across everything, waiting for a finalized backlog, or optimizing for the easiest items undermines value-driven incremental delivery.
- A project manager must explain to a junior colleague the difference between a project life cycle that is predictive versus one that is adaptive. Which statement most accurately captures the distinction relevant to choosing an approach?
- Predictive life cycles fix scope early and plan in detail up front, while adaptive life cycles embrace changing requirements through short, iterative cycles
- Adaptive life cycles fix scope, cost, and schedule at the start, while predictive life cycles leave them all open
- Predictive and adaptive life cycles are identical except for the team's job titles
- Predictive life cycles never produce any documentation, while adaptive life cycles produce all of it
Correct answer: Predictive life cycles fix scope early and plan in detail up front, while adaptive life cycles embrace changing requirements through short, iterative cycles
Predictive approaches define scope and plan in detail early; adaptive approaches accommodate change through iterative, incremental cycles. The other options misstate documentation, invert the constraint behavior, or wrongly claim the approaches are identical.
- During approach selection, the project manager considers organizational factors. The organization has rigid annual funding gates, contractual fixed-scope deliverables, and low tolerance for mid-project change. Which factor most strongly pushes toward a predictive approach?
- A team co-located and trained extensively in agile ceremonies
- A highly experimental product where the market response is unknown
- A customer who wants to refine features after seeing working software
- The contractual fixed-scope deliverables combined with low tolerance for change
Correct answer: The contractual fixed-scope deliverables combined with low tolerance for change
Fixed-scope contracts and low change tolerance favor a predictive approach because the scope must be defined and controlled up front. Experimental products, customers refining features iteratively, and agile-trained teams are indicators that favor adaptive approaches instead.
- A project manager is tailoring practices and must decide which agile ceremonies, predictive controls, and tools to adopt. What input should most directly inform these tailoring decisions?
- The vendor's recommendation to buy the most expensive tool suite
- Whatever approach was used on the last unrelated project in the company
- The project's characteristics, organizational culture, governance requirements, and team capabilities
- The personal preferences of the project manager regardless of context
Correct answer: The project's characteristics, organizational culture, governance requirements, and team capabilities
Tailoring decisions are driven by the project context: its characteristics, the organization's culture and governance, and team capability. Personal preference, copying an unrelated project blindly, or following a vendor's upsell are not sound bases for tailoring.
- After integrating the plan, the project manager presents it for approval. A governance reviewer asks how changes to one baseline will be coordinated with the others once execution begins. What does an integrated plan enable in this regard?
- Changes to be applied only to the most convenient baseline
- The schedule to be changed without any documented analysis
- Coordinated change control, so a change to scope, schedule, or cost is evaluated for its impact across all plan components
- Each baseline to change independently without reviewing impacts on the others
Correct answer: Coordinated change control, so a change to scope, schedule, or cost is evaluated for its impact across all plan components
An integrated plan supports coordinated, integrated change control where a proposed change is assessed for impacts across scope, schedule, cost, and other components. Allowing baselines to change independently or without analysis defeats the purpose of integration.
- A team using a hybrid approach delivers the stable infrastructure work predictively and the customer-facing features adaptively. Stakeholders ask when they will see usable functionality. What is the most accurate expectation the project manager should set?
- All functionality, including infrastructure, will be delivered in a single release at the end
- No functionality is usable until both the predictive and adaptive portions are entirely finished
- The adaptive features will be delivered only after the entire predictive plan is fully baselined
- Usable feature increments will be delivered iteratively as adaptive cycles complete, while the predictive infrastructure follows planned milestones
Correct answer: Usable feature increments will be delivered iteratively as adaptive cycles complete, while the predictive infrastructure follows planned milestones
In a hybrid approach, the adaptive portion delivers usable increments iteratively while the predictive portion meets planned milestones. Stating that nothing is usable until everything is done, or forcing a single end release, contradicts the incremental nature of the adaptive component.
- A project manager joins an organization that mandates a specific predictive methodology, but the assigned project is small, exploratory, and has rapidly shifting requirements. What is the most appropriate first action regarding the approach?
- Apply the predictive methodology rigidly even though it poorly fits the work
- Propose tailoring the mandated methodology to fit the project's exploratory nature, documenting the rationale for governance
- Ignore the mandated methodology entirely and proceed with no defined process
- Cancel the project because the methodology does not match the requirements
Correct answer: Propose tailoring the mandated methodology to fit the project's exploratory nature, documenting the rationale for governance
Tailoring the mandated methodology to fit the project's context, with documented justification, balances organizational governance and project needs. Ignoring process entirely, applying a poor-fitting method rigidly, or canceling a viable project are all inappropriate responses.
- While executing, the project manager notices the team is producing deliverables that are technically complete but do not advance the outcomes the business case promised. What should the project manager do to keep execution aligned with business value?
- Continue producing the technically complete deliverables since the team is busy
- Stop measuring outcomes and rely solely on task completion counts
- Escalate to cancel the project because some deliverables lack value
- Refocus the work and priorities on the deliverables that realize the intended business outcomes and benefits
Correct answer: Refocus the work and priorities on the deliverables that realize the intended business outcomes and benefits
Executing with urgency for business value requires keeping work aligned to the outcomes and benefits in the business case. Continuing low-value work, ignoring outcome measures, or jumping to cancellation all fail to realign execution toward value.
- A program integrates several related projects whose individual plans were built by separate teams. Before approving the integrated program plan, what is the project/program manager's key responsibility regarding the consolidated planning?
- Approve each project plan in isolation without checking cross-project dependencies
- Eliminate any project whose plan differs from the others
- Ensure the consolidated plan resolves interdependencies and conflicts among the individual project plans
- Require all teams to use the identical schedule dates regardless of dependencies
Correct answer: Ensure the consolidated plan resolves interdependencies and conflicts among the individual project plans
Integrating planning across related projects means reconciling interdependencies and conflicts so the consolidated plan is coherent. Approving plans in isolation, forcing identical dates, or eliminating differing projects ignores the integration responsibility.
- A project manager is deciding how much process and documentation rigor to apply. The project is high-risk, high-visibility, and heavily regulated. How should this context affect the tailoring decision?
- Minimize all process and documentation to move faster regardless of the risk
- Apply the same light-touch process used on a low-risk internal tool
- Remove governance reviews to avoid slowing the team
- Increase process rigor and documentation appropriately to match the higher risk, visibility, and regulatory demands
Correct answer: Increase process rigor and documentation appropriately to match the higher risk, visibility, and regulatory demands
Tailoring scales process and documentation to the project's risk, visibility, and regulatory environment, so a high-risk regulated project warrants greater rigor. Minimizing process, reusing a light-touch standard, or removing governance would be inappropriate for this context.
- Early in execution, the product owner and project manager identify which backlog items create the most measurable benefit. They want to confirm value is actually being realized as increments ship. What practice best supports executing for value over time?
- Assess incremental value delivered after each increment and adjust priorities based on the results and stakeholder feedback
- Assume value is delivered once a backlog item is marked done, without further assessment
- Prioritize backlog items solely by their estimated effort rather than value
- Measure value only once, at the very end of the project
Correct answer: Assess incremental value delivered after each increment and adjust priorities based on the results and stakeholder feedback
Assessing incremental value after each delivery and adjusting priorities keeps execution focused on realizing benefits. Assuming value from task completion, measuring only at the end, or prioritizing by effort alone all disconnect execution from actual value realization.
- A project manager must integrate the project's plans into a baseline that will be used to measure performance. Which combination correctly identifies the performance measurement baselines that the integrated plan should consolidate?
- The stakeholder register and the lessons learned register
- The scope baseline, the schedule baseline, and the cost baseline
- The communications plan, the procurement plan, and the staffing plan only
- The risk register, the issue log, and the change log
Correct answer: The scope baseline, the schedule baseline, and the cost baseline
The integrated project management plan consolidates the scope, schedule, and cost baselines that together form the performance measurement baseline. The other options list management plans or project documents that support the plan but are not the measurement baselines themselves.
- A project manager evaluating delivery approaches asks: for which situation is a purely adaptive (agile) approach LEAST appropriate?
- An innovation effort where the final solution is not yet known
- A project with fixed scope, fixed price, and contractually mandated deliverables at defined dates
- Work where early, frequent delivery of increments is highly valued by the customer
- A product with rapidly evolving requirements and frequent customer feedback
Correct answer: A project with fixed scope, fixed price, and contractually mandated deliverables at defined dates
Fixed-scope, fixed-price contracts with mandated deliverable dates suit predictive approaches and are least appropriate for pure agile. Evolving requirements, unknown solutions, and value placed on frequent increments are precisely the conditions where adaptive approaches excel.
- During tailoring, a project manager and team decide to combine predictive milestone reporting with sprint-based delivery. A stakeholder objects that mixing methods is forbidden. How should the project manager respond?
- Explain that tailoring intentionally blends practices to fit the project, and a hybrid of predictive reporting with iterative delivery is a valid choice
- Agree that methods can never be combined and revert to a single rigid method
- Abandon predictive reporting entirely because sprints were chosen
- Escalate to remove the stakeholder from the project for raising the concern
Correct answer: Explain that tailoring intentionally blends practices to fit the project, and a hybrid of predictive reporting with iterative delivery is a valid choice
Tailoring permits blending practices, so a hybrid combining predictive reporting with iterative delivery is legitimate when it fits the project. Claiming methods can never combine, dropping needed reporting, or escalating to remove a questioning stakeholder are all incorrect responses.
- A project manager is building the integrated plan and wants to confirm that all the right subsidiary components are addressed before baselining. Which set of subsidiary management plans would the integrated project management plan typically include?
- The risk register and the issue log alone
- Only the scope and schedule management plans
- The project charter and the business case only
- Scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder engagement management plans
Correct answer: Scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder engagement management plans
The integrated project management plan typically incorporates the full set of subsidiary plans across scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder engagement. Limiting it to two plans, project documents like the risk register and issue log, or initiating documents like the charter and business case would leave the plan incomplete.
- A project manager is finalizing the scope baseline for a software platform. The sponsor keeps adding features during planning conversations, and the team is unsure which work is officially in scope. What should the project manager produce to give the team an unambiguous, hierarchical decomposition of the total work to be delivered?
- A work breakdown structure (WBS) with an accompanying WBS dictionary
- A responsibility assignment matrix mapping people to deliverables
- A requirements traceability matrix linking requirements to objectives
- A milestone list summarizing major deliverable dates
Correct answer: A work breakdown structure (WBS) with an accompanying WBS dictionary
The WBS is the deliverable-oriented hierarchical decomposition of total project work; together with the WBS dictionary (which defines each work package) it forms the scope baseline and tells the team exactly what is in scope. A milestone list, RAM, and traceability matrix serve other planning purposes.
- During a sprint, a stakeholder requests an additional report not in the product backlog. On a predictive (waterfall) project this would trigger formal change control, but this team uses an agile approach. How should the project manager handle the request to remain consistent with the agile delivery method?
- Submit a formal change request to the change control board for approval
- Add the request to the product backlog so the product owner can prioritize it for a future iteration
- Reject the request because the iteration scope is locked and changes are not permitted
- Immediately add it to the current sprint so the stakeholder is satisfied
Correct answer: Add the request to the product backlog so the product owner can prioritize it for a future iteration
In agile, scope changes are welcomed and managed through the product backlog. New requests are added to the backlog and the product owner prioritizes them for future iterations rather than disrupting the committed work of the current sprint or routing through a CCB.
- A project manager computes the schedule and finds total float on the critical path is zero, while a parallel path has 6 days of float. Midway through execution, a critical-path activity slips by 4 days. What is the most accurate immediate impact on the project?
- The critical path shifts to the parallel path and the end date is unaffected
- The 6 days of float on the parallel path absorb the slip with no end-date impact
- The project end date will slip by 4 days unless schedule compression is applied
- Total float increases by 4 days across all network paths
Correct answer: The project end date will slip by 4 days unless schedule compression is applied
Activities on the critical path have zero float, so any slip directly delays the project finish date by the same amount unless the schedule is compressed (crashing or fast tracking). Float on a different path cannot absorb a slip on the critical path.
- To shorten the schedule, a project manager is considering crashing versus fast tracking. The sponsor has authorized extra budget but is highly risk-averse about rework. Which compression technique best fits the sponsor's constraints?
- Fast tracking, by overlapping activities that were planned in sequence
- Reducing scope by removing lower-priority deliverables
- Resource leveling, by smoothing demand across the schedule
- Crashing, by adding resources to critical-path activities to reduce duration
Correct answer: Crashing, by adding resources to critical-path activities to reduce duration
Crashing adds resources to shorten duration and increases cost but does not raise rework risk. Fast tracking overlaps sequential activities and typically increases risk and rework, which conflicts with a risk-averse sponsor. Leveling and scope reduction are not schedule-compression-for-budget responses.
- A project's cost performance index (CPI) is 0.85 and the schedule performance index (SPI) is 1.10 at the midpoint. The sponsor asks for a one-sentence interpretation. Which statement is correct?
- The project is under budget and behind schedule
- The project is both over budget and behind schedule
- The project is over budget but ahead of schedule for the work performed
- The project is on budget and on schedule
Correct answer: The project is over budget but ahead of schedule for the work performed
CPI below 1.0 means actual cost exceeds earned value, so the project is over budget. SPI above 1.0 means earned value exceeds planned value, so it is ahead of schedule. Therefore the project is over budget but ahead of schedule.
- A project has a budget at completion (BAC) of $500,000. Earned value is $200,000 and actual cost is $250,000. Assuming current cost performance continues, what is the estimate at completion (EAC)?
- $500,000
- $550,000
- $450,000
- $625,000
Correct answer: $625,000
When the cost variance is typical and expected to continue, EAC = BAC / CPI. CPI = EV/AC = 200,000/250,000 = 0.8. EAC = 500,000 / 0.8 = $625,000.
- A project manager needs to establish the cost baseline so performance can be measured over time. Which artifact represents the cost baseline used for earned value comparisons?
- The total project budget including all contingency and management reserves
- The funding limit set by the finance department for the fiscal year
- The bottom-up sum of activity cost estimates before any aggregation
- The time-phased budget (S-curve) excluding management reserves
Correct answer: The time-phased budget (S-curve) excluding management reserves
The cost baseline is the approved, time-phased budget (often shown as an S-curve) against which performance is measured. It includes contingency reserves at the work package/control account level but excludes management reserves, which are held outside the baseline.
- A program of three related projects is competing for the same specialized testing lab. The project manager notices that combined demand exceeds lab capacity in week 8. To resolve the over-allocation without adding capacity, which technique should be applied?
- Reserve analysis, to release contingency for additional lab time
- Crashing, by paying overtime to compress the testing activities
- Fast tracking, by running the testing activities in parallel
- Resource leveling, adjusting start dates of activities to stay within the lab's capacity
Correct answer: Resource leveling, adjusting start dates of activities to stay within the lab's capacity
Resource leveling adjusts activity start and finish dates to keep resource demand within available limits, which directly resolves an over-allocation when capacity cannot be increased. It may extend the schedule. Crashing, fast tracking, and reserve analysis do not solve a fixed-capacity constraint.
- A project manager defines activities and then sequences them using the precedence diagramming method. One dependency is that landscaping cannot begin until the building inspection passes, but this is a regulatory requirement outside the team's control. How should this dependency be classified?
- A mandatory external dependency
- A discretionary internal dependency
- A discretionary external dependency
- A mandatory internal dependency
Correct answer: A mandatory external dependency
The dependency is mandatory (legally/contractually required, not a preference) and external (driven by a regulatory body outside the project team). Discretionary dependencies are based on best practices or preference; internal dependencies are within the team's control.
- While building the schedule, a project manager wants to apply a delay so that grouting starts 3 days after tiling finishes to allow curing, even though both could otherwise be continuous. How should this be modeled in the network diagram?
- As a finish-to-start relationship with a 3-day lead
- As a start-to-start relationship with a 3-day lag
- As a finish-to-finish relationship with no lag
- As a finish-to-start relationship with a 3-day lag
Correct answer: As a finish-to-start relationship with a 3-day lag
A lag is a deliberate delay between activities. The successor (grouting) follows the predecessor (tiling) in a finish-to-start relationship, with a 3-day lag inserted for curing. A lead would accelerate the successor, which is the opposite of what is needed.
- A project manager is determining how detailed the budget estimates should be early in the project, when little is known. The sponsor wants a number for the business case. Which estimate type and range is most appropriate at this stage?
- A parametric estimate calibrated to the exact final design
- A definitive estimate, roughly -5% to +10%
- A budget estimate, roughly -10% to +25%
- A rough order of magnitude estimate, roughly -25% to +75%
Correct answer: A rough order of magnitude estimate, roughly -25% to +75%
Early in the project, with limited information, a rough order of magnitude (ROM) estimate is appropriate, typically in the range of -25% to +75%. Definitive estimates with tighter ranges require detailed design information that is not yet available.
- A team estimates an activity using three-point estimation: optimistic 8 days, most likely 14 days, pessimistic 26 days. Using the triangular (simple average) distribution, what is the expected duration?
- 16 days
- 15 days
- 14.67 days
- 17 days
Correct answer: 16 days
The triangular distribution is (O + M + P) / 3 = (8 + 14 + 26) / 3 = 48 / 3 = 16 days. The PERT/beta distribution would weight the most likely value as (O + 4M + P)/6, giving a different result.
- A project manager validates scope at the end of a phase. The customer reviews three deliverables: two are accepted and one is rejected for not meeting a requirement. What is the project manager's correct next step for the rejected deliverable?
- Accept the deliverable anyway to keep the schedule on track
- Mark all three deliverables as incomplete and restart the phase
- Move the deliverable directly to the closing process for archiving
- Document the change/defect and route it through integrated change control or corrective action
Correct answer: Document the change/defect and route it through integrated change control or corrective action
During Validate Scope, accepted deliverables are formally signed off; a rejected deliverable is documented (as a defect/change request) and routed for corrective action or integrated change control. The other deliverables are not affected, and the project manager does not accept noncompliant work.
- A project manager must control costs and detects that the project is consistently spending faster than planned. To forecast how much more money is required to finish the remaining work given current efficiency, which value should be calculated?
- The variance at completion (VAC), as BAC - EAC
- The schedule variance (SV), as EV - PV
- The estimate to complete (ETC), as (BAC - EV) / CPI
- The to-complete performance index (TCPI), as (BAC - EV) / (BAC - AC)
Correct answer: The estimate to complete (ETC), as (BAC - EV) / CPI
ETC forecasts the additional cost needed to finish remaining work. When current cost efficiency is expected to continue, ETC = (BAC - EV) / CPI. VAC measures total expected overrun, SV measures schedule performance, and TCPI measures required future efficiency, not remaining cost.
- A project manager controls the schedule and computes a schedule variance (SV) of -$10,000 with a to-complete performance index needed of 1.2. The sponsor wants to recover the slippage without changing the end date. The critical path runs through integration testing. Which action most directly recovers schedule on the critical path?
- Re-baseline the schedule to make the variance disappear
- Fast track integration testing by overlapping it with a downstream activity, accepting added risk
- Add scope buffer to the non-critical paths to balance float
- Increase the management reserve to fund the recovery
Correct answer: Fast track integration testing by overlapping it with a downstream activity, accepting added risk
To recover schedule without moving the end date, the project manager compresses the critical path. Fast tracking integration testing overlaps activities to save time (at the cost of added risk). Re-baselining hides rather than fixes the issue, buffering non-critical paths does not help, and reserves are not a scheduling action.
- A project uses rolling wave planning. Work in the next quarter is detailed at the work-package level, while work a year out is planned only at a summary level. A stakeholder is concerned the distant work lacks detail. What is the project manager's best explanation?
- Distant work should always be planned in full detail before execution begins
- The summary-level work indicates the project is behind on its planning obligations
- The work breakdown structure is incomplete and must be fully decomposed now
- Rolling wave planning progressively elaborates near-term work in detail and leaves future work at a higher level until more is known
Correct answer: Rolling wave planning progressively elaborates near-term work in detail and leaves future work at a higher level until more is known
Rolling wave planning is an iterative technique where imminent work is planned in detail while work far in the future is kept at a higher level and elaborated as it approaches. This is a deliberate, accepted practice, not a sign the project is behind or the WBS is incomplete.
- A project manager is integrating the subsidiary management plans (scope, schedule, cost, quality, etc.) into a single coherent document that guides execution. Which document results from this integration effort?
- The project scope statement
- The project management plan
- The benefits management plan
- The project charter
Correct answer: The project management plan
The project management plan integrates all subsidiary plans and baselines into one comprehensive document describing how the project will be executed, monitored, and controlled. The charter authorizes the project, the scope statement defines scope, and the benefits management plan addresses benefits realization.
- Halfway through a project, an approved change request modifies the scope baseline. The project manager must ensure the change is reflected consistently. Which set of documents most likely needs corresponding updates as a result?
- Only the requirements documentation
- The WBS, schedule baseline, and cost baseline
- The lessons learned register and the stakeholder register only
- Only the project charter
Correct answer: The WBS, schedule baseline, and cost baseline
A scope change typically cascades: the WBS (and scope baseline) changes, which usually affects the schedule baseline and cost baseline because new or modified work alters timing and cost. The charter is generally not changed for routine scope adjustments, and limiting updates to a single document would leave the plan inconsistent.
- A project manager is estimating activity durations and has data from a similar past project plus the current project's parameters (e.g., square footage). To produce a statistically based estimate that scales with a measurable quantity, which technique is most appropriate?
- Expert judgment alone
- Analogous estimating
- Reserve analysis
- Parametric estimating
Correct answer: Parametric estimating
Parametric estimating uses a statistical relationship between historical data and other variables (such as cost or duration per unit of measure) to calculate an estimate that scales with the quantity. Analogous estimating uses values from a similar past project as a whole and is less precise.
- During Control Costs, the project manager finds that the cumulative CPI has been stable at 0.90 for several reporting periods. The sponsor asks for the most reliable forecast of total project cost. Which EAC formula best fits a stable, ongoing performance trend?
- EAC = AC + [(BAC - EV) / (CPI x SPI)]
- EAC = AC + (BAC - EV)
- EAC = BAC / CPI
- EAC = AC + bottom-up ETC from a new estimate
Correct answer: EAC = BAC / CPI
When current cost variances are expected to continue at the same rate (a stable CPI), EAC = BAC / CPI is the standard forecast. AC + (BAC - EV) assumes future work performs to plan; the CPI x SPI formula is used when schedule also influences remaining work; a bottom-up re-estimate is used when prior assumptions are no longer valid.
- A project manager needs to define scope for a new product and wants to elicit detailed requirements from a large, geographically dispersed stakeholder group quickly and at low cost. Which requirements-gathering technique best fits these constraints?
- A facilitated workshop with all stakeholders in one room
- Questionnaires and surveys
- Observation (job shadowing) of each stakeholder's workflow
- One-on-one interviews with each stakeholder
Correct answer: Questionnaires and surveys
Questionnaires and surveys are well suited to gathering information quickly and inexpensively from a large, dispersed audience. In-person workshops and observation are impractical for dispersed groups, and one-on-one interviews with everyone would be too time-consuming.
- A project manager is sequencing schedule activities and identifies that the project completion is driven by the longest path through the network. A team member asks how to determine which activities cannot be delayed without delaying the project. What should the project manager calculate?
- The resource histogram, to see who is over-allocated
- The critical path, by performing forward and backward passes to find activities with zero total float
- The cost baseline S-curve, to align spending with schedule
- The milestone chart, to display key dates to stakeholders
Correct answer: The critical path, by performing forward and backward passes to find activities with zero total float
The critical path method uses forward and backward passes to compute early/late dates and total float; activities with zero total float make up the critical path and cannot be delayed without delaying the project. A resource histogram, cost S-curve, and milestone chart serve other purposes.
- A predictive project's approved cost baseline is $480,000. Three months in, the project manager wants a single number that represents the total funding authorized for the project, including the contingency reserve but reserving an additional amount the sponsor controls outside the PM's authority. Which component describes that sponsor-controlled amount?
- Control account
- Management reserve
- Cost baseline
- Contingency reserve
Correct answer: Management reserve
Management reserve is funding held outside the cost baseline for unforeseen ('unknown unknown') work and is controlled by management/sponsor, not the PM. Contingency reserve is inside the baseline for identified risks. The total of baseline plus management reserve equals the project budget.
- Midway through execution, a project manager computes Earned Value of $120,000, Actual Cost of $150,000, and Planned Value of $135,000. The sponsor asks whether the project is currently over budget. What should the project manager report?
- The project is over budget because the cost variance is negative (EV minus AC = -$30,000)
- Budget status cannot be determined without the budget at completion
- The project is under budget because earned value exceeds planned value
- The project is on budget because actual cost is close to planned value
Correct answer: The project is over budget because the cost variance is negative (EV minus AC = -$30,000)
Cost variance = EV - AC = $120,000 - $150,000 = -$30,000, a negative value indicating the work performed cost more than budgeted, so the project is over budget. PV is used for schedule variance, not cost. BAC is not required to assess current cost performance.
- A project has a Budget at Completion of $600,000. Current Earned Value is $240,000 and Actual Cost is $300,000. Assuming the cost performance trend continues, what is the most appropriate Estimate at Completion the PM should communicate?
- $600,000, because the budget at completion is fixed
- $540,000, adding remaining work to actual cost at planned rate
- $660,000, adding the current cost overrun to the budget
- $750,000, using EAC = BAC divided by the cost performance index
Correct answer: $750,000, using EAC = BAC divided by the cost performance index
CPI = EV/AC = 240,000/300,000 = 0.8. When the current cost variance is expected to continue (typical/atypical assumption), EAC = BAC/CPI = 600,000/0.8 = $750,000. The other options misapply EAC formulas that assume the overrun was a one-time event.
- During budget planning, a project manager rolls up the cost estimates of individual work packages, then adds the contingency reserves for identified risks to arrive at a baseline against which performance will be measured. What is the PM creating through this aggregation?
- The basis of estimates
- The cost baseline
- The funding limit reconciliation
- The management reserve
Correct answer: The cost baseline
Aggregating work package cost estimates plus their contingency reserves produces the cost baseline, the time-phased budget used to measure and monitor cost performance. Management reserve sits above the baseline. Funding limit reconciliation compares expenditures against funding constraints.
- A project manager needs an early, rough order-of-magnitude budget figure for a proposal before detailed requirements exist, using costs from a similar past project adjusted by an expert. Which estimating technique fits this situation?
- Bottom-up estimating
- Three-point estimating
- Analogous estimating
- Parametric estimating
Correct answer: Analogous estimating
Analogous estimating uses values (cost or duration) from a similar prior project plus expert judgment to produce a quick, lower-accuracy estimate when little detail is available. Bottom-up requires detailed work packages, and parametric requires a statistical relationship and quantitative data.
- On an agile project, the team is funded incrementally and the product owner reprioritizes the backlog each iteration. A stakeholder asks how cost will be controlled without a detailed upfront budget. What is the project manager's best response?
- A detailed cost baseline must be created before any iterations can begin
- The team must switch to a predictive approach to enable cost control
- Cost is controlled by fixing the team size and iteration length, so spend per iteration is predictable while scope flexes within that funding
- Cost cannot be controlled on adaptive projects, so the sponsor accepts open-ended spending
Correct answer: Cost is controlled by fixing the team size and iteration length, so spend per iteration is predictable while scope flexes within that funding
On adaptive projects, a stable team working in fixed-length iterations creates a known, repeatable cost per iteration (run rate). Scope is variable but cost and time per increment are bounded, giving predictable spend while value is delivered incrementally.
- A project manager observes that the cumulative spend is approaching a quarterly funding limit, but several work packages are scheduled to start in that same period. What process should the PM apply to address this constraint?
- Management reserve drawdown to cover the gap automatically
- Funding limit reconciliation, adjusting the schedule of work to align expenditures with the funding available each period
- Earned value analysis to forecast the variance at completion
- Reserve analysis to add contingency to the affected work packages
Correct answer: Funding limit reconciliation, adjusting the schedule of work to align expenditures with the funding available each period
Funding limit reconciliation compares planned expenditures against any funding limits per period; when spending would exceed the limit, work is rescheduled to smooth expenditures within the available funding. The other options do not resolve a periodic funding constraint.
- A team member estimates a task as 8 days optimistic, 20 days most likely, and 38 days pessimistic. Using a beta (PERT) three-point calculation, what expected duration should the PM use?
- 23 days
- 21 days
- 20 days
- 22 days
Correct answer: 21 days
Beta/PERT expected duration = (O + 4M + P)/6 = (8 + 80 + 38)/6 = 126/6 = 21 days. The triangular average would be (8+20+38)/3 = 22, but PERT weights the most likely value four times.
- During schedule development, a project manager identifies that activity B can start only after activity A finishes, but the team wants B to begin two days after A completes due to a required curing period. How should this be modeled in the schedule network?
- A finish-to-finish dependency with a two-day lag
- A finish-to-start dependency with a two-day lead removed and a two-day lag added
- A start-to-finish dependency with no lag
- A start-to-start dependency with a two-day lead
Correct answer: A finish-to-start dependency with a two-day lead removed and a two-day lag added
The required waiting time between A finishing and B starting is a lag (a deliberate delay) on a finish-to-start relationship. A lead would accelerate the successor; the curing delay is the opposite. Start-to-start and finish-to-finish do not match 'B starts after A finishes.'
- A project manager has built the schedule network and needs to identify the longest path through the diagram to determine the shortest possible project duration and which activities have zero float. Which technique provides this?
- Resource leveling
- Critical chain method
- Schedule compression by fast tracking
- Critical path method
Correct answer: Critical path method
The critical path method calculates the longest path of dependent activities, yielding the minimum project duration; activities on this path have zero total float. Critical chain adds buffers around resource constraints; resource leveling and fast tracking are responses, not the path-identification technique.
- The sponsor demands the project finish three weeks earlier without reducing scope, and a small budget increase is acceptable. Which schedule compression technique should the PM consider first?
- Crashing, by adding resources to critical path activities to shorten duration
- Scope reduction, by removing lower-priority deliverables
- Fast tracking, by overlapping activities that were planned in sequence
- Resource leveling, to balance resource demand across the schedule
Correct answer: Crashing, by adding resources to critical path activities to shorten duration
Crashing shortens the schedule by adding resources to critical path activities, typically increasing cost — which matches a tolerable budget increase. Fast tracking overlaps activities and adds risk/rework rather than cost. Scope reduction is excluded because scope must remain unchanged.
- After resource leveling is applied to resolve an over-allocation of a key engineer, the project manager notices the project end date has moved out by five days. What is the most likely explanation the PM should give the team?
- The critical path was shortened, so the end date should have moved earlier
- Resource leveling never changes the project end date, so the schedule tool has an error
- Leveling added cost rather than time, so the finish date should not move
- Leveling delayed activities to fit resource availability, which can extend the critical path and change the finish date
Correct answer: Leveling delayed activities to fit resource availability, which can extend the critical path and change the finish date
Resource leveling adjusts start/finish dates to respect resource limits and frequently extends the critical path and project duration. Resource smoothing, by contrast, stays within available float and does not move the end date. The reported five-day slip is the expected outcome of leveling.
- A project manager is decomposing the schedule and wants to define the smallest units of work to be scheduled, estimated, and monitored. According to PMI scheduling practice, what are these lowest-level components called?
- Milestones, marking significant points
- Control accounts, used for cost measurement
- Activities, derived by decomposing work packages
- Work packages, taken directly from the WBS
Correct answer: Activities, derived by decomposing work packages
Activities are produced by decomposing work packages (the lowest WBS level) into the discrete actions needed to complete them; activities are what get sequenced, estimated, and scheduled. Control accounts aggregate for measurement and milestones are zero-duration markers.
- Two weeks into execution a project manager finds Schedule Performance Index of 0.9 and Cost Performance Index of 1.05. The sponsor asks for a plain-language status. What is the most accurate summary?
- The project is ahead of schedule and over budget
- The project is on schedule and on budget
- The project is behind schedule but under budget
- The project is behind schedule and over budget
Correct answer: The project is behind schedule but under budget
SPI = 0.9 (< 1.0) means work is being completed slower than planned — behind schedule. CPI = 1.05 (> 1.0) means the work earned more value than it cost — under budget. So the project is behind schedule but under budget.
- A project manager wants to validate the budget by reconciling the bottom-up cost estimates against the original analogous estimate given to the sponsor, and to document the assumptions and confidence levels behind each estimate. Which document captures this supporting detail?
- The basis of estimates
- The cost management plan
- The cost baseline
- The project funding requirements
Correct answer: The basis of estimates
The basis of estimates documents how estimates were derived, including assumptions, constraints, the estimating method, the range, and the confidence level. The cost management plan defines processes; the cost baseline is the approved time-phased budget; funding requirements derive from the baseline.
- On a hybrid project, the predictive component reports a To-Complete Performance Index based on BAC of 1.2 while CPI is currently 0.85. What does this signal to the project manager?
- The management reserve should be released to the cost baseline immediately
- Remaining work must be performed far more efficiently than past work to still meet the original budget, indicating the budget is likely unrealistic
- Schedule performance is the primary concern and cost is on track
- The project is performing better than planned and will finish under budget
Correct answer: Remaining work must be performed far more efficiently than past work to still meet the original budget, indicating the budget is likely unrealistic
A TCPI of 1.2 means remaining work must run at 120% efficiency to hit BAC, while the current CPI of 0.85 shows actual efficiency well below that. The large gap signals the budget target is probably no longer achievable and a new EAC should be communicated.
- A project manager must sequence activities and chooses to model dependencies where a successor cannot finish until a predecessor finishes — for example, testing cannot complete until the last component is delivered. Which logical relationship is this?
- Start-to-start
- Start-to-finish
- Finish-to-finish
- Finish-to-start
Correct answer: Finish-to-finish
Finish-to-finish means the successor's completion depends on the predecessor's completion; testing can be underway but cannot finish until delivery finishes. Finish-to-start ties a start to a finish, and start-to-start ties two starts together.
- During budgeting, a project manager assigns each major deliverable's costs to a management control point where scope, schedule, and cost are integrated and compared to earned value. What is this integration point called?
- A cost baseline
- A control account
- A planning package
- A work package
Correct answer: A control account
A control account is a management control point where scope, budget, actual cost, and schedule integrate and are compared to earned value for performance measurement. Each control account may contain multiple work packages. A planning package is future work not yet detailed.
- A project's parametric estimate uses a rate of $250 per square meter for installation, and the deliverable covers 1,800 square meters with a historically validated relationship. The PM defends this approach to a skeptical stakeholder. What is the strongest justification for parametric estimating here?
- It always produces more accurate results than bottom-up estimating
- It requires no historical data, making it the fastest possible method
- It eliminates the need to document assumptions in the basis of estimates
- It uses a statistically validated relationship between historical data and project variables, producing accuracy that scales with the quality of the underlying data
Correct answer: It uses a statistically validated relationship between historical data and project variables, producing accuracy that scales with the quality of the underlying data
Parametric estimating multiplies a quantity by a statistically derived rate from historical data; its accuracy depends on the data's quality and the model's validity. It does require historical data, is not automatically more accurate than bottom-up, and still needs documented assumptions.
- A project manager discovers that resource smoothing was requested instead of resource leveling because the delivery date cannot move. What constraint does resource smoothing impose that distinguishes it from leveling?
- Smoothing always reduces the project duration below the critical path
- Smoothing requires adding resources to every critical path activity
- Smoothing only adjusts activities within their available float, so the project completion date is not delayed
- Smoothing ignores resource limits entirely and only optimizes cost
Correct answer: Smoothing only adjusts activities within their available float, so the project completion date is not delayed
Resource smoothing optimizes resource usage only within the free and total float of activities, so it does not change the critical path or the completion date. Leveling can move the end date because it is not bound by float. Smoothing may not fully resolve all over-allocations.
- A project manager is forecasting and the sponsor asks: given current performance, how much more money is expected to be spent to finish the remaining work? Which earned value measure answers this directly?
- Budget at Completion (BAC)
- Estimate to Complete (ETC)
- Variance at Completion (VAC)
- Estimate at Completion (EAC)
Correct answer: Estimate to Complete (ETC)
Estimate to Complete (ETC) is the expected cost to finish the remaining work, typically EAC minus AC. EAC is the total expected cost of the whole project, VAC is the projected over/under run, and BAC is the original total budget.
- While building the schedule, a project manager must decide the order of activities and identifies that pouring a foundation must precede framing because of the physical nature of construction. This unavoidable, work-inherent relationship is best classified as which type of dependency?
- An internal resource dependency
- A mandatory dependency (hard logic)
- A discretionary dependency (preferred logic)
- An external dependency
Correct answer: A mandatory dependency (hard logic)
A mandatory dependency (hard logic) is inherent in the nature of the work or contractually required — framing physically cannot precede the foundation. Discretionary dependencies reflect best-practice preferences, and external dependencies involve parties outside the project.
- A predictive project's network diagram shows that Activity D can start as soon as Activity B finishes, but the team decides to wait three days after B completes before starting D so that materials can cure. How should the project manager represent this waiting period in the schedule?
- Add a three-day lead to the dependency so D starts earlier
- Add a three-day lag to the finish-to-start dependency between B and D
- Increase Activity D's duration estimate by three days
- Insert a separate three-day milestone activity between B and D
Correct answer: Add a three-day lag to the finish-to-start dependency between B and D
A lag is intentional delay time inserted between a predecessor and successor. A finish-to-start with a three-day lag correctly models the required wait. A lead would accelerate the successor, a milestone has zero duration and would not enforce the wait, and padding D's duration misrepresents the actual work effort.
- During schedule development the project manager finds that two activities can only begin after a government inspection that is outside the team's control and cannot be scheduled by the project. What type of dependency is this?
- External mandatory dependency
- External discretionary dependency
- Internal discretionary dependency
- Internal mandatory dependency
Correct answer: External mandatory dependency
The inspection is required (mandatory) and is driven by a party outside the project (external). Discretionary dependencies are based on best practices or preference, and internal dependencies are within the project team's control. A government inspection the team cannot control is an external mandatory dependency.
- A project is behind schedule. The sponsor will not approve additional budget but is willing to accept slightly more risk to recover the finish date. Which schedule compression technique best fits these constraints?
- Crashing the critical path by adding resources
- Reducing the project scope to remove activities
- Fast tracking activities that were originally planned in sequence
- Re-baselining the schedule to the current forecast
Correct answer: Fast tracking activities that were originally planned in sequence
Fast tracking performs sequential activities in parallel, which shortens the schedule without added cost but increases risk and possible rework. Crashing adds resources and therefore cost, which the sponsor rejected. Reducing scope changes the deliverables, and re-baselining hides the slip rather than recovering it.
- The project manager calculates that the critical path is 60 days. A near-critical path through different activities is 58 days. What is the float of the activities on the 58-day path, and why does it matter?
- Two days of free float that can never affect the project end date
- Zero float, because any path close to the critical path has no slack
- Two days of total float, meaning small delays on that path could make it critical
- Sixty days of float, equal to the project duration
Correct answer: Two days of total float, meaning small delays on that path could make it critical
Total float for a near-critical path equals the difference between it and the critical path, here 60 minus 58 equals two days. This small buffer matters because a delay greater than two days would convert it into a new critical path, so the PM must monitor it closely.
- While building the schedule using an agile approach, the team commits to a fixed two-week timebox and pulls only the work it believes it can complete. The product owner keeps requesting additional items mid-iteration. What is the most appropriate response from the project manager acting as servant leader?
- Expand the current iteration to absorb the additional requested items
- Cancel the iteration and replan all remaining work
- Ask the team to work overtime to deliver the extra items
- Protect the timebox and defer new items to the backlog for future iterations
Correct answer: Protect the timebox and defer new items to the backlog for future iterations
In iterative timeboxing, the iteration scope is protected once committed; new requests go to the backlog and are prioritized for later iterations. Expanding the timebox, canceling it, or forcing overtime all undermine sustainable pace and the predictability that timeboxing provides.
- A project manager estimates an activity as 8 days optimistic, 14 days most likely, and 26 days pessimistic. Using the PERT (beta) three-point estimate, what is the expected duration?
- 14 days
- 16 days
- 18 days
- 15 days
Correct answer: 15 days
The beta-distribution PERT formula is (optimistic + 4 x most likely + pessimistic) divided by 6, which is (8 + 56 + 26) / 6 = 90 / 6 = 15 days. The triangular average would be (8+14+26)/3 = 16, but PERT weights the most likely value, giving 15.
- Midway through execution, actual progress data shows several activities finishing later than planned. The project manager updates the schedule model and the projected completion date moves out by ten days. What document should the project manager update to communicate this revised projection?
- The activity list
- The milestone list
- The schedule baseline
- The schedule forecasts
Correct answer: The schedule forecasts
Schedule forecasts are estimates of future project conditions based on current performance, so a revised completion date is recorded there. The schedule baseline is only updated through approved change control, the activity list defines work to be done, and the milestone list records significant points, not forecasts.
- The team is using rolling wave planning. Work in the next quarter is decomposed into detailed activities, while work eighteen months out is left at a higher level. A stakeholder asks why the distant work is not yet detailed. What is the best explanation?
- The schedule tool cannot store activities beyond twelve months
- Distant work has been excluded from the project scope for now
- Distant work is elaborated progressively as more information becomes available
- Detailing distant work is the responsibility of the PMO, not the team
Correct answer: Distant work is elaborated progressively as more information becomes available
Rolling wave planning is a form of progressive elaboration where near-term work is planned in detail and future work is planned at a higher level, then elaborated as it approaches and more information is known. The distant work is still in scope, just not yet decomposed.
- A project manager wants to display the project schedule to executives in a format that emphasizes only major deliverables and key decision points across the timeline, without showing the hundreds of detailed activities. Which schedule presentation is most appropriate?
- A resource histogram
- A milestone chart
- A detailed Gantt bar chart
- A project schedule network diagram
Correct answer: A milestone chart
A milestone chart shows only major events and is well suited to executive summaries. A detailed Gantt chart shows all activities, a network diagram emphasizes logical relationships and is too detailed, and a resource histogram displays resource usage, not schedule milestones.
- During quality planning, the project manager and team decide which standards are relevant and how the project will demonstrate compliance, including the metrics that will be measured. What is the primary output of this effort?
- The quality management plan and quality metrics
- Verified deliverables
- The quality control measurements
- Accepted deliverables
Correct answer: The quality management plan and quality metrics
Planning quality management produces the quality management plan and the quality metrics that define how compliance will be measured. Quality control measurements come from controlling quality, verified deliverables come from control quality, and accepted deliverables come from validating scope.
- A manufacturing project produces components, and the team wants to detect whether the production process is staying within acceptable variation or is drifting out of control over time. Which quality tool is most appropriate?
- A control chart
- A scatter diagram
- A check sheet
- A Pareto chart
Correct answer: A control chart
Control charts plot process results over time against upper and lower control limits to detect whether a process is stable or trending out of control. Pareto charts rank defect causes, scatter diagrams show relationships between two variables, and check sheets tally occurrences.
- After several iterations, a control chart shows seven consecutive data points all falling on one side of the mean, even though every point is within the control limits. What should the project manager conclude?
- The data points should be discarded as measurement errors
- The process is in control because all points are within the limits
- The control limits should be widened to reduce false alarms
- The process should be investigated because the rule of seven indicates a non-random trend
Correct answer: The process should be investigated because the rule of seven indicates a non-random trend
The rule of seven states that seven or more consecutive points on one side of the mean signals a non-random pattern requiring investigation, even if all points are inside the control limits. Being within limits alone does not confirm the process is behaving randomly.
- The quality team identifies that 80 percent of customer complaints come from roughly 20 percent of the defect types. The project manager wants a visual that ranks defect causes by frequency to focus corrective action. Which tool fits this need?
- A control chart
- A Pareto chart
- A histogram
- A flowchart
Correct answer: A Pareto chart
A Pareto chart is a bar chart that orders causes by frequency, supporting the 80/20 principle so teams target the vital few causes. A histogram shows distribution without ranking by cause, a control chart tracks process stability, and a flowchart maps process steps.
- A project manager is debating whether to invest more in inspections and testing before delivery or to accept higher rework and warranty costs after delivery. Which cost-of-quality concept frames this trade-off?
- Cost of conformance versus cost of nonconformance
- Direct versus indirect costs
- Fixed versus variable costs
- Sunk versus opportunity costs
Correct answer: Cost of conformance versus cost of nonconformance
Cost of quality distinguishes conformance costs (prevention and appraisal, such as testing and inspection) from nonconformance costs (internal and external failure, such as rework and warranty claims). Investing in conformance to avoid larger failure costs is the core quality trade-off.
- During a quality audit, an independent reviewer finds that the team is following all documented procedures correctly, yet defects are still reaching the customer. What is the most likely conclusion the audit supports?
- The processes themselves may be inadequate and should be improved
- The team should be retrained on the existing procedures
- The defects are acceptable because procedures were followed
- Quality control inspections should be reduced
Correct answer: The processes themselves may be inadequate and should be improved
If the team follows procedures correctly but defects still escape, the problem lies in the process design rather than execution, so the processes need improvement. Quality audits are intended to identify such process gaps and drive continuous improvement, not just verify compliance.
- A project manager wants to determine which factors most strongly influence a particular quality defect by changing several input variables in a controlled, structured set of test runs. Which technique is being described?
- Benchmarking
- Design of experiments
- Statistical sampling
- Brainstorming
Correct answer: Design of experiments
Design of experiments is a statistical method that systematically varies multiple factors to identify which have the greatest effect on an outcome, optimizing the process efficiently. Statistical sampling selects a subset to inspect, benchmarking compares to other organizations, and brainstorming generates ideas.
- A team performing schedule risk analysis runs a simulation that samples activity durations thousands of times to produce a probability distribution of possible project completion dates. Which technique is this?
- Monte Carlo simulation
- Critical path method
- Critical chain method
- Resource leveling
Correct answer: Monte Carlo simulation
Monte Carlo simulation repeatedly samples uncertain inputs such as activity durations to produce a probability distribution of outcomes like completion dates. The critical path method computes a single deterministic path, critical chain manages buffers around constraints, and resource leveling adjusts for resource limits.
- After applying resource leveling to resolve an over-allocation, the project manager notices the project end date has moved later than the original critical path indicated. Why does this commonly happen?
- Resource leveling reduces the total amount of work to be performed
- Resource leveling always shortens the schedule by removing slack
- Resource leveling changes the logical dependencies between activities
- Resource leveling can extend the schedule when limited resources delay critical activities
Correct answer: Resource leveling can extend the schedule when limited resources delay critical activities
Resource leveling adjusts start and finish dates based on resource constraints, and when key resources are limited it often pushes activities out, lengthening the schedule and sometimes changing the critical path. It does not reduce total work or alter the underlying logical relationships.
- A project uses cause-and-effect analysis to trace a recurring defect back to its root causes across categories such as people, process, materials, and equipment. Which quality tool supports this analysis?
- A scatter diagram
- A fishbone (Ishikawa) diagram
- A run chart
- A control chart
Correct answer: A fishbone (Ishikawa) diagram
A fishbone or Ishikawa diagram organizes potential causes of a problem into categories to identify root causes. A run chart shows data over time, a scatter diagram tests correlation between two variables, and a control chart monitors process stability against limits.
- The project manager is asked to confirm the schedule is achievable given that one specialized engineer is required for several activities that currently overlap. The end date must not move. Which approach should the project manager use first?
- Resource smoothing within the available float
- Resource leveling regardless of the end date
- Fast tracking the affected activities
- Crashing the affected activities
Correct answer: Resource smoothing within the available float
Resource smoothing adjusts activities only within their available float so resource demand stays under a limit without changing the project end date. Resource leveling can move the end date, while crashing adds cost and fast tracking adds risk; smoothing is the right first choice when the date is fixed.
- A team estimates an activity by comparing it to a similar activity completed on a prior project, using that historical duration and expert judgment because detailed information is not yet available. Which estimating technique is this?
- Bottom-up estimating
- Three-point estimating
- Parametric estimating
- Analogous estimating
Correct answer: Analogous estimating
Analogous estimating uses historical data from a similar past activity or project plus expert judgment, and is used when limited detail is available. Parametric uses a statistical relationship per unit, bottom-up aggregates detailed estimates, and three-point uses optimistic, most likely, and pessimistic values.
- During control quality, the team inspects a sample of finished units and documents which ones meet specifications. The validated deliverables and the inspection results are then routed to the appropriate next steps. Where do the verified deliverables from this process go?
- To validate scope, where the customer formally accepts them
- Back to plan quality management for re-baselining
- Directly to the customer as accepted deliverables
- To close project, bypassing customer acceptance
Correct answer: To validate scope, where the customer formally accepts them
Control quality produces verified deliverables (those that meet quality requirements), which then feed into validate scope where the customer or sponsor formally accepts them. Acceptance is a separate step from verification, so deliverables are not sent directly to the customer as accepted.
- Midway through a six-month software project, the project manager calculates a Cost Performance Index (CPI) of 0.85 and a Schedule Performance Index (SPI) of 1.10. Which statement best describes the project's current health?
- The project is behind schedule and over budget
- The project is ahead of schedule but over budget for the work completed
- The project is behind schedule and under budget
- The project is ahead of schedule and under budget
Correct answer: The project is ahead of schedule but over budget for the work completed
SPI above 1.0 means more work has been completed than planned (ahead of schedule), while CPI below 1.0 means the project is spending more than the value earned (over budget). The combination of SPI 1.10 and CPI 0.85 indicates ahead of schedule but over budget.
- A project has a Budget at Completion (BAC) of $400,000. At a status check, Earned Value (EV) is $200,000 and Actual Cost (AC) is $250,000. Assuming the cost variance experienced so far is typical of future work, what is the Estimate at Completion (EAC)?
- $400,000
- $450,000
- $320,000
- $500,000
Correct answer: $500,000
When current cost performance is expected to continue, EAC = BAC / CPI. CPI = EV/AC = 200,000/250,000 = 0.8. EAC = 400,000/0.8 = $500,000.
- During schedule planning the project manager identifies that Task B cannot begin until two days after Task A finishes, because freshly poured concrete must cure. How should this be represented in the schedule network?
- A start-to-start relationship with a two-day lag
- A finish-to-start relationship with a two-day lead
- A finish-to-finish relationship with a two-day lead
- A finish-to-start relationship with a two-day lag
Correct answer: A finish-to-start relationship with a two-day lag
The cure time is a mandatory delay between the finish of Task A and the start of Task B, which is a finish-to-start dependency with a lag (positive waiting time). A lead would accelerate the successor, the opposite of what is needed.
- A project manager must estimate the cost of a new facility build and has detailed historical data plus statistical relationships between project parameters (such as cost per square foot) from prior similar projects. Which estimating technique provides the most accurate estimate in this situation?
- Expert judgment alone
- Rough order of magnitude
- Parametric estimating
- Analogous estimating
Correct answer: Parametric estimating
Parametric estimating uses a statistical relationship between historical data and other variables (e.g., cost per square foot) to calculate an estimate, producing higher accuracy when reliable scalable data exists. Analogous estimating is less accurate and used when limited detail is available.
- While developing the project schedule, the project manager wants to determine the longest path through the network to calculate the shortest possible project duration. Which technique should be used?
- Critical chain method
- Resource leveling
- Critical path method
- Monte Carlo simulation
Correct answer: Critical path method
The critical path method identifies the longest path of dependent activities through the network, which determines the shortest time to complete the project. Activities on this path have zero float.
- A resource-constrained project has a key engineer who is the only person able to perform three critical activities, causing over-allocation. The project manager adjusts start dates so the engineer works on them sequentially, which extends the project end date. Which technique was applied?
- Resource leveling
- Resource smoothing
- Fast tracking
- Schedule crashing
Correct answer: Resource leveling
Resource leveling adjusts activity start and finish dates based on resource constraints to balance demand against availability, and it can change the critical path and extend the project duration. Resource smoothing, by contrast, does not delay the project completion date.
- The sponsor demands the project finish two weeks earlier without changing scope. The project manager decides to perform two design activities in parallel that were originally planned sequentially. What is the primary risk introduced by this approach?
- Increased rework if the parallel activities require rework due to dependencies
- Reduced quality of the finished deliverables
- Higher direct labor cost from adding resources
- Loss of float on non-critical path activities only
Correct answer: Increased rework if the parallel activities require rework due to dependencies
Performing sequential activities in parallel is fast tracking, which can shorten duration without adding cost but increases the risk of rework because activities that depend on each other are started before predecessors are fully complete. Adding resources (and cost) describes crashing.
- A project manager reviews a status report showing EV = $80,000, PV = $100,000, and AC = $90,000. What is the schedule variance (SV), and what does it indicate?
- +$20,000, meaning the project is ahead of schedule
- -$20,000, meaning the project is behind schedule
- +$10,000, meaning the project is under budget
- -$10,000, meaning the project is over budget
Correct answer: -$20,000, meaning the project is behind schedule
Schedule variance SV = EV - PV = 80,000 - 100,000 = -$20,000. A negative SV indicates less work has been earned than planned, so the project is behind schedule. Cost variance (EV - AC) would address budget status.
- The project's BAC is $600,000, EV is $150,000, and AC is $200,000. Cost performance is expected to continue at the current rate. How much more money is needed to finish the remaining work (Estimate to Complete, ETC)?
- $600,000
- $400,000
- $450,000
- $800,000
Correct answer: $600,000
With typical performance, EAC = BAC/CPI. CPI = 150,000/200,000 = 0.75, so EAC = 600,000/0.75 = $800,000. ETC = EAC - AC = 800,000 - 200,000 = $600,000.
- During estimation, a team provides a most likely cost of $40,000, an optimistic cost of $30,000, and a pessimistic cost of $80,000 for an activity. Using the triangular (simple average) three-point estimate, what is the expected cost?
- $45,000
- $42,500
- $47,500
- $50,000
Correct answer: $50,000
The triangular distribution uses a simple average: (Optimistic + Most Likely + Pessimistic) / 3 = (30,000 + 40,000 + 80,000) / 3 = 150,000/3 = $50,000. The beta (PERT) formula would weight the most likely value by four.
- For the same activity (optimistic $30,000, most likely $40,000, pessimistic $80,000), what is the expected cost using the beta (PERT) distribution?
- $47,500
- $42,500
- $45,000
- $50,000
Correct answer: $45,000
The beta/PERT estimate = (O + 4M + P) / 6 = (30,000 + 4(40,000) + 80,000) / 6 = (30,000 + 160,000 + 80,000)/6 = 270,000/6 = $45,000.
- A project manager establishes the cost baseline. A stakeholder asks what the difference is between the cost baseline and the project budget. Which answer is correct?
- The cost baseline includes management reserves but excludes contingency reserves
- The cost baseline equals the project budget plus contingency reserves
- The project budget equals the cost baseline plus management reserves
- The project budget excludes contingency reserves but includes management reserves
Correct answer: The project budget equals the cost baseline plus management reserves
The cost baseline is the approved, time-phased budget that includes contingency reserves but excludes management reserves. The total project budget = cost baseline + management reserves. Management reserves require management approval to access.
- On a predictive project, the team must reduce the schedule by adding overtime and additional staff to critical path activities while keeping scope unchanged. Which schedule compression technique is being used, and what is its main trade-off?
- Fast tracking, which increases risk
- Resource leveling, which extends duration
- Resource smoothing, which reduces float
- Crashing, which increases cost
Correct answer: Crashing, which increases cost
Crashing shortens the schedule by adding resources (overtime, more people) to critical path activities, with the main trade-off being increased cost. Fast tracking overlaps activities and increases risk rather than directly increasing cost.
- A project manager needs to assign physical resources and team members to scheduled activities and is building a document that shows resource demand over time, highlighting any periods of over-allocation. Which tool is the project manager creating?
- Resource breakdown structure
- Resource histogram
- Milestone chart
- Responsibility assignment matrix (RACI)
Correct answer: Resource histogram
A resource histogram is a bar chart that displays the number of hours a resource is needed over time and visually reveals over-allocation periods. A RACI clarifies roles, and a resource breakdown structure is a hierarchical decomposition of resources by category.
- During an agile project, the team uses story points and historical velocity to forecast how many sprints are needed to complete the remaining backlog. This is the agile equivalent of which traditional planning activity?
- Estimating activity durations and developing the schedule
- Defining and sequencing activities
- Determining the cost baseline
- Performing quantitative risk analysis
Correct answer: Estimating activity durations and developing the schedule
Using velocity (completed story points per sprint) to forecast how many iterations remain is the adaptive way of estimating durations and developing a release schedule. It maps to duration estimation and schedule development rather than cost or risk activities.
- A project's To-Complete Performance Index (TCPI) based on BAC is calculated as 1.25, while the current CPI is 0.90. What does this tell the project manager?
- The schedule must be compressed to meet the deadline
- The team must perform more efficiently than it has been to finish within the original budget
- The project will finish under budget if current performance continues
- The remaining work can be completed at the current efficiency level
Correct answer: The team must perform more efficiently than it has been to finish within the original budget
TCPI represents the cost performance that must be achieved on remaining work to meet a financial goal. A TCPI of 1.25 greater than the current CPI of 0.90 means the team must become significantly more efficient than it has been to complete the project within the original BAC.
- While developing the schedule, the project manager identifies an activity with the following: early start day 5, early finish day 10, late start day 8, late finish day 13. What is the total float of this activity?
Correct answer: 3 days
Total float = Late Start - Early Start = 8 - 5 = 3 days (equivalently Late Finish - Early Finish = 13 - 10 = 3 days). Positive float means the activity can be delayed without delaying the project, so it is not on the critical path.
- A government contract requires the project manager to track the precise time-phased spending plan against which performance will be measured throughout execution. Which output of cost planning serves this purpose?
- The cost baseline (S-curve of cumulative planned value)
- The basis of estimates document
- The cost management plan
- The project funding requirements step function
Correct answer: The cost baseline (S-curve of cumulative planned value)
The cost baseline is the approved time-phased budget, often shown as an S-curve of cumulative planned value (PV), used as the basis for measuring and monitoring cost performance via earned value. The cost management plan defines how costs will be managed, not the spending baseline itself.
- A discretionary dependency (preferred logic) was used to sequence two activities based on the team's best-practice preference. Mid-project, the schedule is at risk. What is the project manager's best option regarding this dependency?
- Remove the dependency entirely without analysis to save time
- Treat it as fixed because all dependencies are mandatory once baselined
- Escalate to the sponsor since changing logic always requires a baseline change
- Consider resequencing the activities, since discretionary dependencies can be modified if needed
Correct answer: Consider resequencing the activities, since discretionary dependencies can be modified if needed
Discretionary dependencies are based on preferred or best practices and are not mandatory, so they can be reviewed and modified (e.g., to enable fast tracking) when schedule pressure arises. Mandatory dependencies (hard logic), by contrast, cannot be changed.
- A project manager is using rolling wave planning on a long-duration project. How does this approach affect cost and schedule estimating for distant work?
- All work is fully estimated in detail at the start to lock the baseline
- Estimates for distant work are fixed and not revised
- Distant work is planned at a higher level and elaborated in detail as it approaches
- Distant work is excluded from the budget until execution begins
Correct answer: Distant work is planned at a higher level and elaborated in detail as it approaches
Rolling wave planning is an iterative technique in which near-term work is planned in detail while future work is planned at a higher level and progressively elaborated as it approaches and more information becomes available.
- The project manager notices the critical path activities are fine, but a near-critical path with only two days of float has experienced a three-day delay. What is the most important consequence the project manager should communicate?
- Total float on the original critical path has increased
- The delay has no impact because it is not on the critical path
- The project budget at completion will automatically increase
- The near-critical path has likely become the new critical path, changing the project finish date
Correct answer: The near-critical path has likely become the new critical path, changing the project finish date
When a delay consumes more float than a near-critical path had (3-day delay on a path with 2 days of float), that path becomes critical and can drive the project completion date. The project manager must reassess the critical path and the finish date.
- A project uses an analogous estimate of $1.2M derived from a similar past project to set the initial budget early in initiation. A stakeholder questions the reliability. What is the most accurate characterization the project manager should give?
- It is a top-down estimate that is faster and cheaper but generally less accurate than bottom-up estimating
- It guarantees the final cost within plus or minus five percent
- It is the most accurate technique available and should not be revised
- It is a bottom-up estimate aggregated from work package details
Correct answer: It is a top-down estimate that is faster and cheaper but generally less accurate than bottom-up estimating
Analogous estimating is a top-down technique that uses values from a previous similar project to estimate the current one. It is less costly and time-consuming but generally less accurate than bottom-up estimating, which aggregates detailed work package estimates.
- Midway through a predictive infrastructure project, a key sponsor verbally asks the project manager to add a new reporting module while the two are in a hallway conversation. The PM agrees it sounds valuable. What should the PM do next to handle this properly?
- Add the module to the next sprint backlog without further analysis
- Document the request as a formal change request and route it through the integrated change control process
- Begin building the reporting module immediately since the sponsor authorized it
- Update the scope statement to include the module and notify the team to proceed
Correct answer: Document the request as a formal change request and route it through the integrated change control process
Even when a sponsor proposes a change, it must be captured as a formal change request and evaluated through Perform Integrated Change Control before any work begins. A verbal hallway agreement is not authorization to alter the baseline.
- A change request to expand project scope has been submitted and analyzed. The change control board reviews the impact analysis and approves it. What must the project manager do to ensure the approval has lasting effect on the project?
- Implement the work but leave the baselines unchanged to preserve the original plan
- Update the affected baselines and the change log, then communicate the change to stakeholders
- File the approval in the project archive and continue with the original plan
- Wait for the sponsor to issue a separate written authorization before acting
Correct answer: Update the affected baselines and the change log, then communicate the change to stakeholders
Once a change is approved, the relevant baselines (scope, schedule, cost) and project documents must be updated, the change log recorded, and stakeholders informed. Failing to update baselines leaves the plan inconsistent with the approved work.
- During execution, a team member implements a fix that alters a product feature without submitting it through any change process. The PM discovers the undocumented modification during a review. What is the BEST way to describe what occurred?
- A configuration item update that the team properly logged
- A defect repair that does not require change control
- An approved corrective action that improves product quality
- Scope creep through an unauthorized change that bypassed integrated change control
Correct answer: Scope creep through an unauthorized change that bypassed integrated change control
An uncontrolled, unsubmitted alteration to the product is unauthorized change (a form of scope creep). All changes to baselined work must pass through integrated change control regardless of how beneficial they appear.
- A project manager wants to ensure that every proposed change to project deliverables is identified, its status tracked, and its versions controlled so the team always knows the current approved configuration. Which discipline directly supports this need?
- Resource leveling
- Earned value management
- Quality assurance auditing
- Configuration management
Correct answer: Configuration management
Configuration management focuses on identifying configuration items, controlling their versions, and recording and reporting their status, ensuring the team always works from the current approved configuration. It works alongside change control but addresses product/deliverable versioning.
- On a hybrid project, the customer requests an enhancement that the PM estimates will add cost and extend the schedule beyond the approved baselines. Before the change control board meets, what should the PM prepare?
- An updated stakeholder register including the requesting customer
- A revised project charter reflecting the requested enhancement
- A lessons-learned entry describing the requested enhancement
- An impact analysis covering effects on scope, schedule, cost, quality, and risk
Correct answer: An impact analysis covering effects on scope, schedule, cost, quality, and risk
Decision-makers need a complete impact analysis showing how the change affects the project constraints and objectives so they can make an informed approve/defer/reject decision. The analysis is the input to the CCB, not a charter revision.
- A change control board rejects a proposed change after reviewing it. What is the appropriate disposition for the project manager?
- Implement a scaled-down version of the change at the PM's discretion
- Hold the request open indefinitely in case the board reconsiders
- Discard the change request entirely so it leaves no trace in project records
- Record the rejected status in the change log and notify the requester of the decision and rationale
Correct answer: Record the rejected status in the change log and notify the requester of the decision and rationale
All change requests—approved, deferred, or rejected—are recorded in the change log with their disposition. The requester should be informed of the outcome and reasoning. Rejected requests are documented, not erased.
- Early in planning a predictive project, the PM must decide whether the organization should build a needed component internally or buy it from an external supplier. Which analysis is MOST appropriate to drive this decision?
- A make-or-buy analysis weighing internal capability, cost, and risk against external sourcing
- A RACI responsibility assignment matrix
- A Monte Carlo simulation of the project schedule
- A stakeholder power/interest grid
Correct answer: A make-or-buy analysis weighing internal capability, cost, and risk against external sourcing
Make-or-buy analysis evaluates whether a product or service is best produced in-house or acquired externally, considering cost, capability, capacity, and risk. It is foundational to developing the procurement management approach.
- A buyer wants to transfer the maximum cost risk to the seller for a clearly defined, well-understood scope of work where requirements are unlikely to change. Which contract type BEST fits this situation?
- Time and materials (T&M)
- Cost plus fixed fee (CPFF)
- Firm fixed price (FFP)
- Cost plus incentive fee (CPIF)
Correct answer: Firm fixed price (FFP)
A firm fixed price contract sets a single price for a well-defined scope, placing cost-overrun risk on the seller. It is most appropriate when the deliverable is clearly specified and stable, minimizing the buyer's financial exposure.
- A project requires specialized work whose total scope cannot be precisely defined up front, and the buyer wants to reimburse the seller's legitimate costs while motivating efficiency through a performance-based bonus. Which contract type aligns with these goals?
- Lump sum contract
- Fixed price with economic price adjustment (FPEPA)
- Firm fixed price (FFP)
- Cost plus incentive fee (CPIF)
Correct answer: Cost plus incentive fee (CPIF)
A cost plus incentive fee contract reimburses allowable costs and adds an incentive fee tied to meeting performance targets, sharing savings or overruns per an agreed formula. It suits uncertain scope while encouraging seller efficiency.
- A buyer engages a contractor for staff augmentation where the exact number of hours of effort is unknown at the outset and the work resembles open-ended consulting. Which agreement type is MOST suitable?
- Time and materials (T&M)
- Fixed price incentive fee (FPIF)
- Firm fixed price (FFP)
- Cost plus award fee (CPAF)
Correct answer: Time and materials (T&M)
Time and materials contracts are hybrid arrangements ideal for staff augmentation, expert acquisition, or work where a precise statement of work cannot yet be written. The buyer pays per hour/unit at agreed rates as effort accumulates.
- During source selection, the project team evaluates several seller proposals against weighted criteria such as technical capability, past performance, and price. What is this technique called?
- A procurement audit
- A weighting system within proposal evaluation
- A bidder conference
- A claims administration review
Correct answer: A weighting system within proposal evaluation
A weighting system assigns numerical weights to evaluation criteria and scores each proposal against them to minimize personal bias and produce a defensible selection. It is a core part of the Conduct Procurements evaluation step.
- A project manager holds a meeting with all prospective sellers before they submit proposals, ensuring every vendor has a clear and common understanding of the procurement requirements. What is this event called?
- A retrospective
- A bidder conference
- A change control board meeting
- A kickoff meeting
Correct answer: A bidder conference
A bidder (or pre-bid/contractor) conference gathers all prospective sellers before proposal submission so each receives the same information and there is no preferential treatment, promoting fair and competitive responses.
- The procurement documents for a competitive bid include a detailed description of the work the seller must perform, derived from the project scope baseline. What is this document called?
- A requirements traceability matrix
- A procurement statement of work (SOW)
- A responsibility assignment matrix
- A risk register
Correct answer: A procurement statement of work (SOW)
The procurement statement of work defines the portion of project scope to be included in the related contract in sufficient detail for sellers to determine whether they can provide the products or services. It is drawn from the scope baseline.
- A buyer wants to solicit price quotations from sellers for a standard, commodity item where price is the primary decision factor. Which procurement document is MOST appropriate to issue?
- A request for information (RFI)
- A request for quotation (RFQ)
- A statement of work (SOW)
- A request for proposal (RFP)
Correct answer: A request for quotation (RFQ)
A request for quotation is used when the buyer expects sellers to compete primarily on price for standard items. An RFP is used for more complex solutions, and an RFI gathers information rather than soliciting a purchase decision.
- After a contract is signed, the seller submits a deliverable. The project manager must confirm the seller's performance meets contractual requirements and authorize payments accordingly. Which process governs this ongoing oversight?
- Plan Procurement Management
- Control Procurements
- Conduct Procurements
- Develop Project Charter
Correct answer: Control Procurements
Control Procurements manages procurement relationships, monitors contract performance, makes changes and corrections, and processes payments. It is the execution-and-monitoring phase that follows awarding the contract in Conduct Procurements.
- A disagreement arises between the buyer and seller over whether certain extra work falls inside the original contract scope, and the parties cannot resolve it through negotiation. What is the BEST term for this matter, and how should it generally be resolved first?
- A risk trigger, which should be logged in the risk register and monitored
- A change request, which the buyer may approve unilaterally
- A claim, which should be resolved through the contract's negotiation or dispute-resolution provisions before escalating to arbitration or litigation
- A defect, which should be repaired by the seller at no cost
Correct answer: A claim, which should be resolved through the contract's negotiation or dispute-resolution provisions before escalating to arbitration or litigation
Contested changes where buyer and seller disagree on compensation or scope are claims (disputes/appeals). They are first addressed through negotiation per the contract's dispute-resolution clauses, with arbitration or litigation as later resorts.
- As a procurement nears completion, the project manager confirms all deliverables were accepted, verifies the contract terms were met, and formally settles open claims and final payments. What is the PM performing?
- Procurement closure, including a procurement audit and formal acceptance
- Quality control inspection of internal deliverables
- Risk reassessment for the remaining project work
- Resource release for the internal project team
Correct answer: Procurement closure, including a procurement audit and formal acceptance
Closing procurements involves verifying deliverables were accepted, resolving open claims, finalizing payments, and conducting a procurement audit to capture lessons. Formal written acceptance and documentation are essential before a contract is closed.
- In an agile environment, the team works with an external vendor whose scope will evolve sprint by sprint. To keep the relationship flexible while still controlling cost, the parties agree to cap total spend and adjust deliverables iteratively. Which contracting approach BEST supports this?
- A lump-sum contract negotiated only at project close
- A cost plus fixed fee contract with no spending limit
- A single firm fixed price contract for the entire anticipated scope
- A master services agreement with smaller, scope-bounded work statements issued per iteration
Correct answer: A master services agreement with smaller, scope-bounded work statements issued per iteration
For evolving agile scope, a master services agreement paired with capped, iteration-level statements of work lets the buyer adjust deliverables each cycle while limiting financial exposure. A single FFP contract conflicts with changing requirements.
- A change is approved that affects a deliverable already produced by an external seller. What must the project manager ensure happens with the contract?
- A formal contract change is processed so the agreement reflects the approved modification
- The seller absorbs the change at no cost as part of normal warranty
- The contract is terminated and re-bid for the modified deliverable
- The change is implemented internally to avoid involving the seller
Correct answer: A formal contract change is processed so the agreement reflects the approved modification
Approved changes affecting contracted work must flow through the contract's change-control provisions so the agreement is formally amended. This keeps the legal document aligned with project baselines and protects both parties.
- A project manager notices that small, individually minor change requests have accumulated to significantly expand the project's scope without any single large approval. What practice would have BEST prevented this drift?
- Deferring all change analysis until the project's final review
- Routing every change—regardless of size—through integrated change control and tracking cumulative impact
- Recording changes only after a phase completes to reduce administrative load
- Allowing the team to approve any change under a set cost threshold on their own
Correct answer: Routing every change—regardless of size—through integrated change control and tracking cumulative impact
Scope creep often accumulates from many small unmanaged changes. Routing all changes through integrated change control and monitoring their cumulative effect against baselines prevents incremental drift, even when each item seems trivial.
- During Control Procurements, the project manager conducts a structured review of the entire procurement process from planning through award to identify successes and failures for use on future procurements. What is this review called?
- A bidder conference
- A procurement audit
- A control chart review
- A make-or-buy analysis
Correct answer: A procurement audit
A procurement audit is a structured review of the procurement process, identifying what worked and what did not, so successes and shortcomings can be carried into future procurements. It supports continuous improvement of the procurement function.
- A seller proposes a change to the way contracted work is performed that the buyer believes is justified, but the parties disagree on the additional compensation owed. The project manager wants to keep work moving while the dispute is settled. What is the MOST appropriate action?
- Remove the seller from the project and complete the work in-house without notice
- Document the contested change as a claim and follow the contract's claims administration and negotiation process while monitoring performance
- Stop all work immediately until a court rules on the disputed amount
- Pay the seller's requested amount in full to avoid delay
Correct answer: Document the contested change as a claim and follow the contract's claims administration and negotiation process while monitoring performance
Contested changes are managed through claims administration: documenting the claim and resolving it via the contract's negotiation/dispute provisions, ideally through negotiation. Work can often continue under monitoring while the compensation dispute is settled.
- Midway through a project, a stakeholder asks the project manager which version of the requirements document was approved before the last change request. The team has been emailing copies back and forth, and several conflicting files now exist. What should the project manager have established to prevent this situation?
- A configuration management system with version control for project artifacts
- A daily standup where requirements are read aloud to the team
- A risk register entry for documentation loss
- A separate communications plan for each stakeholder group
Correct answer: A configuration management system with version control for project artifacts
Managing project artifacts requires configuration management and version control so the team always knows which version of a document is current and approved. Emailing copies creates uncontrolled, conflicting versions. The other options do not address artifact versioning.
- A project manager is setting up the repository where all project documents, including the project charter, plans, and logs, will be stored. Team members in three time zones need consistent, current access. What is the most important characteristic of how these artifacts should be managed?
- A printed binder updated weekly and circulated by mail
- A single source of truth that is continuously kept accurate and accessible to those who need it
- Encrypted copies stored only on the project manager's laptop for security
- Separate, independent copies maintained by each functional team
Correct answer: A single source of truth that is continuously kept accurate and accessible to those who need it
Effective artifact management establishes a single source of truth that is current, accurate, and accessible to authorized stakeholders. Independent or offline copies create version conflicts and stale information, undermining transparency.
- During a project audit, the auditor finds that the same lessons-learned register exists in two locations with different entries. The project manager wants to correct the underlying process. What practice most directly addresses this problem?
- Adding more detail to each lessons-learned entry
- Holding lessons-learned reviews more frequently
- Assigning the lessons-learned register to a junior team member
- Establishing version control so only one authoritative copy of each artifact is maintained
Correct answer: Establishing version control so only one authoritative copy of each artifact is maintained
Two divergent copies signal a lack of version control. The fix is a controlled artifact-management approach with a single authoritative version, not more entries, more meetings, or reassignment.
- A project manager joins a project already in progress and finds documents scattered across personal drives, chat threads, and email. To bring order, what should the project manager prioritize first regarding the artifacts?
- Convert every document into a single combined PDF
- Restrict all artifact access to the sponsor only
- Determine where artifacts will be stored, how they will be versioned, and who can access them
- Immediately delete all duplicate files to reduce clutter
Correct answer: Determine where artifacts will be stored, how they will be versioned, and who can access them
The first step in managing artifacts is defining the management approach: storage location, versioning method, and access permissions. Deleting files without a controlled process risks losing approved information, and restricting access to one person blocks the team.
- A team uses a shared digital workspace where each document automatically retains a history of edits and the ability to revert to prior versions. This capability most directly supports which artifact-management need?
- Maintaining traceability and the ability to recover an earlier approved baseline
- Replacing the project schedule with a document log
- Eliminating the need for a change control process
- Reducing the number of stakeholders on the project
Correct answer: Maintaining traceability and the ability to recover an earlier approved baseline
Edit history and reversion support version control: traceability of changes and recovery of an earlier baseline. It does not remove the need for change control, nor does it substitute for the schedule.
- The project manager must decide who can edit, who can only view, and who can approve changes to the project's key documents. Setting these distinctions is an example of managing what aspect of project artifacts?
- The communications escalation path
- Access and permission controls within the artifact-management approach
- The procurement source selection criteria
- The risk response strategies
Correct answer: Access and permission controls within the artifact-management approach
Defining who can edit, view, or approve artifacts is part of access and permission control, a core element of managing artifacts. The other options address communications, procurement, and risk, not document access.
- A project is closing, and the project manager wants to ensure that future teams can reuse the project's templates, plans, and lessons learned. What artifact-management action best supports this goal?
- Archiving final artifacts in the organization's repository so they become available organizational process assets
- Shredding all documents to protect confidentiality
- Emailing the documents once to the sponsor and deleting the repository
- Keeping the only copies on the departing team's personal devices
Correct answer: Archiving final artifacts in the organization's repository so they become available organizational process assets
At closure, final artifacts should be archived as organizational process assets so future projects can reuse them. Shredding, retaining only personal copies, or deleting the repository destroys reusable knowledge.
- A new regulation requires the team to track the rationale behind every approved requirement change for the project's full duration. Which artifact-management practice best enables compliance?
- Storing only the latest version and discarding all prior versions
- Recording changes verbally in standups without written entries
- Maintaining a change log linked to versioned documents that records what changed, when, and why
- Limiting the project to a single requirement to avoid changes
Correct answer: Maintaining a change log linked to versioned documents that records what changed, when, and why
Traceability of change rationale requires a change log tied to versioned artifacts capturing what, when, and why. Discarding prior versions or relying on verbal records destroys the audit trail needed for compliance.
- A project manager must choose between a predictive, an agile, and a hybrid approach for a new initiative. The requirements are well understood and unlikely to change, and the deliverable must meet strict regulatory documentation at each phase gate. Which approach best fits?
- A team-choice approach with no defined methodology
- A change-driven approach that delays all planning until execution
- A purely adaptive approach with continuous backlog reprioritization
- A predictive (plan-driven) approach with defined phases and phase gates
Correct answer: A predictive (plan-driven) approach with defined phases and phase gates
Stable, well-understood requirements and strict phase-gate documentation favor a predictive approach. Adaptive methods fit high uncertainty and frequent change, which is not the situation described.
- A product's requirements are expected to evolve rapidly based on frequent customer feedback, and the team wants to deliver usable increments every two weeks. Which delivery approach is most appropriate?
- A waterfall approach freezing all requirements up front
- A predictive approach with a single delivery at the end
- A phase-gate approach prohibiting any scope change
- An adaptive (agile) approach using short iterations and incremental delivery
Correct answer: An adaptive (agile) approach using short iterations and incremental delivery
High requirement volatility and a desire for frequent usable increments point to an adaptive approach with short iterations. Predictive and frozen-scope approaches do not accommodate rapid, feedback-driven change.
- A project has a stable infrastructure component that benefits from upfront design, plus a customer-facing feature set that needs frequent iteration. The project manager wants one cohesive approach. What is the most suitable choice?
- Running two completely separate, unrelated projects
- A hybrid approach applying predictive methods to the stable component and adaptive methods to the evolving features
- A fully predictive approach for the entire project
- A fully adaptive approach for the entire project
Correct answer: A hybrid approach applying predictive methods to the stable component and adaptive methods to the evolving features
When parts of the work suit predictive methods and other parts suit adaptive methods, a hybrid approach is most appropriate. Forcing the whole project into one extreme ignores the differing characteristics of each component.
- Before selecting a delivery approach, a project manager evaluates the degree of uncertainty in requirements, the frequency of expected change, and the criticality of early delivery. This evaluation is best described as part of which Process-domain responsibility?
- Determining the appropriate project methodology, methods, and practices
- Procuring external resources
- Closing the project or phase
- Managing stakeholder engagement
Correct answer: Determining the appropriate project methodology, methods, and practices
Assessing requirement uncertainty, change frequency, and delivery needs is how a project manager determines the appropriate methodology and practices. The other options address engagement, closure, and procurement.
- An organization mandates a predictive methodology, but the project manager finds that a specific subprocess would benefit from short feedback loops without violating the mandate's intent. What is the most appropriate action?
- Tailor the approach by incorporating suitable adaptive practices where they add value while honoring organizational requirements
- Escalate to cancel the project due to methodology conflict
- Abandon the beneficial practice because only one methodology may ever be used
- Ignore the organizational mandate entirely and switch to full agile
Correct answer: Tailor the approach by incorporating suitable adaptive practices where they add value while honoring organizational requirements
Tailoring lets the project manager adapt methods to fit the context while still meeting organizational requirements. Ignoring the mandate or refusing any beneficial adjustment are both extremes that tailoring is designed to avoid.
- A project manager is tailoring the project's processes and notes that some standard governance documents add little value for this small, low-risk effort. What is the guiding principle for tailoring these processes?
- Remove all governance to maximize speed
- Adapt the processes to the project's size, complexity, and risk so effort is appropriate to need
- Copy the processes from the largest project in the portfolio
- Always apply every available process regardless of project characteristics
Correct answer: Adapt the processes to the project's size, complexity, and risk so effort is appropriate to need
Tailoring adjusts processes to the project's specific size, complexity, and risk, so effort matches need. Applying every process blindly or removing all governance both ignore the project's actual context.
- During approach selection, a project manager considers how often the team can realistically demonstrate working results to stakeholders. A high feasible demonstration frequency most strongly favors which choice?
- An iterative/incremental approach that delivers and reviews results in short cycles
- A predictive approach delivering only at the final milestone
- A document-only approach with no working deliverables
- Deferring any delivery decision until the closing phase
Correct answer: An iterative/incremental approach that delivers and reviews results in short cycles
The ability to demonstrate working results frequently favors iterative/incremental delivery, where stakeholders review increments in short cycles. A single final delivery does not leverage that capability.
- A project manager must decide which artifacts the team will actually produce and maintain for a lightweight project. Overproducing documents would waste effort, while too few would harm traceability. What approach best resolves this?
- Produce no artifacts and rely on memory
- Produce the maximum possible number of artifacts to be safe
- Use the artifact set from an unrelated industry's template verbatim
- Tailor the set of artifacts to what the project genuinely needs for control and traceability
Correct answer: Tailor the set of artifacts to what the project genuinely needs for control and traceability
Tailoring extends to choosing the appropriate set of artifacts based on the project's real needs for control and traceability. Maximizing or eliminating artifacts both fail to match documentation to need.
- A team is debating whether to use story points and a product backlog or a detailed work breakdown structure with a baseline schedule. This debate is fundamentally about which Process-domain decision?
- Defining the stakeholder communication cadence
- Determining the project's procurement strategy
- Selecting methods and practices consistent with the chosen delivery approach
- Establishing the quality cost of conformance
Correct answer: Selecting methods and practices consistent with the chosen delivery approach
Story points and backlogs versus a WBS and baseline schedule represent method choices aligned to a delivery approach (adaptive versus predictive). The decision is about methodology and methods, not procurement, communications, or quality costs.
- A project manager wants to confirm that the chosen delivery approach remains valid as the project evolves. Which practice best supports this?
- Delegating the approach decision permanently to the sponsor
- Letting each team member choose a different approach each sprint
- Locking the approach at initiation and never revisiting it
- Periodically reassessing the approach and tailoring decisions as conditions change
Correct answer: Periodically reassessing the approach and tailoring decisions as conditions change
Methodology and tailoring decisions should be revisited as project conditions evolve, since context can change. Locking the approach permanently or fragmenting it inconsistently undermines coherent delivery.
- A stakeholder requests access to a confidential project artifact they are not authorized to view. The project manager has defined access rules in the artifact-management approach. What should the project manager do?
- Delete the artifact to avoid the conflict
- Move the artifact to a public folder for everyone
- Apply the defined access controls and decline or escalate the request per the rules
- Grant access immediately because the person asked
Correct answer: Apply the defined access controls and decline or escalate the request per the rules
When access rules exist, the project manager enforces them, declining or escalating requests that fall outside authorization. Granting access on request, deleting, or making artifacts public all violate the controlled approach.
- A project manager notices that team members cannot tell whether a plan they are reading is the current approved baseline or an old draft. What artifact-management improvement directly fixes this confusion?
- Increasing the font size of all documents
- Clear version labeling and status indicators (e.g., draft vs. approved) on every artifact
- Reducing the number of project meetings
- Adding more stakeholders to the distribution list
Correct answer: Clear version labeling and status indicators (e.g., draft vs. approved) on every artifact
Confusion between draft and approved content is resolved by clear version labeling and status indicators on each artifact. Formatting changes, fewer meetings, or wider distribution do not clarify version status.
- When determining the appropriate methodology, a project manager weighs the organization's culture, the level of regulatory oversight, team experience with agile, and how mature the requirements are. Why are these factors evaluated together?
- Because methodology must be identical across all company projects
- Because the best-fit approach depends on the combined project and organizational context, not a single factor
- Because regulatory oversight is the only factor that ever matters
- Because team experience must always force a predictive approach
Correct answer: Because the best-fit approach depends on the combined project and organizational context, not a single factor
Methodology selection considers the combined context: culture, regulation, team capability, and requirement maturity together. No single factor dictates the choice, and approaches are tailored per project rather than forced to be identical.
- A project manager establishes that whenever an artifact is updated, the system records who made the change and timestamps it, and prior versions remain retrievable. During a dispute over a deleted requirement, this setup allows the team to do what?
- Prevent any future changes to the requirement permanently
- Eliminate the need for stakeholder sign-off on changes
- Trace exactly when and by whom the requirement was changed and restore the earlier version if needed
- Automatically resolve the dispute without any human review
Correct answer: Trace exactly when and by whom the requirement was changed and restore the earlier version if needed
Authorship tracking, timestamps, and retrievable prior versions provide traceability and recovery, letting the team see who changed what and restore an earlier version. It does not remove the need for sign-off or human judgment in resolving disputes.
- A project team is split across three vendor organizations and disagreements about who can approve scope changes keep stalling work. The project manager wants to fix this systematically. Which action most directly establishes the governance the project lacks?
- Add a clause to each vendor contract requiring faster responses
- Escalate every disputed change to the project sponsor for a final ruling
- Hold a daily standup so all three vendors share status updates
- Define a decision-making framework that documents which roles hold authority over which categories of decisions
Correct answer: Define a decision-making framework that documents which roles hold authority over which categories of decisions
Governance is fundamentally about defining decision rights and authority. Documenting which roles can decide what (a decision-making framework) resolves the root cause: unclear authority. Escalating everything overloads the sponsor, contract clauses address speed not authority, and standups improve communication but not who decides.
- During project initiation, the sponsor asks the project manager to clarify how project-level decisions will connect to the organization's portfolio review board. What is the project manager primarily being asked to define?
- The escalation paths and reporting lines linking project governance to enterprise governance
- The risk register thresholds for individual risks
- The communications management plan for daily team updates
- The detailed work breakdown structure for the first phase
Correct answer: The escalation paths and reporting lines linking project governance to enterprise governance
Linking project decisions to a higher portfolio board concerns governance alignment, specifically escalation paths and reporting lines that connect project, program, and organizational governance. A WBS, communications plan, and risk thresholds are valuable but do not define how project governance ties into enterprise governance.
- A project uses a hybrid approach. The PM notices that the same minor technical disputes are repeatedly escalated to the steering committee, slowing decisions. What governance adjustment best addresses this?
- Forward all disputes to the PMO for arbitration
- Define decision thresholds so lower-impact decisions are resolved at the team level and only higher-impact ones escalate
- Require the team to vote on every technical dispute
- Disband the steering committee and let the sponsor decide everything
Correct answer: Define decision thresholds so lower-impact decisions are resolved at the team level and only higher-impact ones escalate
Effective governance assigns decisions to the appropriate level. Setting decision thresholds empowers the team to resolve minor matters while reserving the steering committee for high-impact issues. Disbanding the committee, mandatory voting, and routing all to the PMO either remove needed oversight or add bottlenecks.
- A newly assigned project manager finds there is no clear definition of who is accountable versus merely consulted for each major deliverable. Which tool best establishes this part of the governance structure?
- A stakeholder power/interest grid
- A burndown chart tracking remaining work
- A Gantt chart showing deliverable due dates
- A RACI (responsibility assignment) matrix that clarifies who is accountable, responsible, consulted, and informed
Correct answer: A RACI (responsibility assignment) matrix that clarifies who is accountable, responsible, consulted, and informed
A RACI matrix explicitly defines roles and accountability for deliverables, a core component of governance. A Gantt chart shows timing, a burndown shows remaining work, and a power/interest grid classifies stakeholders by influence, none of which clarify accountability for specific deliverables.
- Midway through execution, an unexpected technical defect is discovered that blocks a deliverable. It is not a risk that was identified earlier. What should the project manager do first to handle this as an issue?
- Close it out as accepted scope and move on
- Add it to the risk register as a new threat to monitor
- Submit a change request to baseline the schedule slip
- Log it in the issue log with an owner and target resolution date
Correct answer: Log it in the issue log with an owner and target resolution date
An issue is a present problem requiring action, distinct from a risk (a future uncertainty). The first step is to record it in the issue log with an assigned owner and target date so it can be tracked to resolution. Logging it as a risk misclassifies a current problem, a change request is premature, and ignoring it abandons the problem.
- A project manager is reviewing the issue log and sees several issues marked open with no owner and no due date, lingering for weeks. What is the most effective corrective action?
- Assign each open issue a single accountable owner and a target resolution date, then review progress regularly
- Escalate every open issue directly to the sponsor
- Delete the stale issues to keep the log clean
- Convert all open issues into risks for the risk register
Correct answer: Assign each open issue a single accountable owner and a target resolution date, then review progress regularly
Issues require a named owner and resolution date to drive accountability and closure. Reviewing progress regularly keeps them moving. Deleting them hides problems, converting to risks mislabels active problems, and escalating all of them to the sponsor is excessive for issues the team can resolve.
- What is the key conceptual difference a project manager applies when deciding whether to place an item in the risk register versus the issue log?
- Risks are uncertain future events; issues are problems happening now that need resolution
- Risks belong to the sponsor; issues belong to the team
- Risks are always negative; issues are always positive
- Risks are tracked in agile projects only; issues in predictive only
Correct answer: Risks are uncertain future events; issues are problems happening now that need resolution
The defining distinction is timing and certainty: a risk is an uncertain future event that may occur, while an issue is a current problem that has already materialized and requires action. Risks can be opportunities, ownership varies, and both logs are used across methodologies.
- A steering committee was set up at project start, but team members are unsure when to bring matters to it. To strengthen governance, what should the project manager clarify with the committee?
- The personal development goals of each committee member
- The detailed estimates for every remaining work package
- The vendor payment schedule for the procurement contracts
- Its mandate, meeting cadence, and the types of decisions and escalations it owns
Correct answer: Its mandate, meeting cadence, and the types of decisions and escalations it owns
A governance body functions well only when its mandate, cadence, and decision scope are explicit. Clarifying what the steering committee owns and when it convenes removes confusion. Work estimates, member development goals, and payment schedules are unrelated to defining the committee's governance role.
- An issue logged two weeks ago has grown beyond the project team's authority to resolve because it requires additional funding. According to sound governance, what should the project manager do?
- Resolve it by quietly reallocating budget from another work package
- Wait to see if the issue resolves itself before acting
- Escalate the issue through the defined escalation path to the role authorized to approve additional funding
- Close the issue and document that it could not be solved
Correct answer: Escalate the issue through the defined escalation path to the role authorized to approve additional funding
When an issue exceeds the PM's or team's authority, governance dictates escalation along the defined path to the authority who can act, here someone who can approve funding. Reallocating budget without approval violates governance, closing it abandons the problem, and waiting risks worsening impact.
- A project manager wants the issue log to be genuinely useful rather than a passive list. Which set of attributes should each entry contain to support active management?
- Description, owner, priority, status, and target resolution date
- A copy of the full project charter for context
- The sponsor's name and the project budget
- Only a brief description and the date it was raised
Correct answer: Description, owner, priority, status, and target resolution date
An actionable issue log entry needs enough structure to be managed: a clear description, an owner, a priority, a current status, and a target resolution date. A bare description with a date cannot be tracked to closure, and the other options add irrelevant or duplicated information.
- During a phase-gate review, the governance board must decide whether the project continues, is paused, or is terminated. What is this type of governance decision point called?
- A change control board approving scope changes
- A stage gate (phase gate) where go/no-go decisions are made
- A daily standup to synchronize the team
- A retrospective to capture lessons learned
Correct answer: A stage gate (phase gate) where go/no-go decisions are made
A stage or phase gate is a governance checkpoint at which leadership makes a go/no-go (continue, hold, or kill) decision based on criteria. A standup synchronizes daily work, a retrospective reflects on process, and a change control board evaluates change requests, none of which are phase-gate continuation decisions.
- A conflict has arisen because two functional managers each believe they have final say over a shared resource's assignments. The project manager realizes the governance structure did not define this. What is the best long-term fix?
- Document the resource-decision authority in the governance structure so the conflict cannot recur
- Remove the shared resource from the project entirely
- Always defer to whichever manager is more senior
- Ask the two managers to resolve it between themselves each time it happens
Correct answer: Document the resource-decision authority in the governance structure so the conflict cannot recur
The recurring conflict stems from undefined decision authority, a governance gap. Documenting who decides resource assignments prevents recurrence. Letting them work it out each time is reactive, deferring to seniority ignores project needs, and removing the resource may harm delivery unnecessarily.
- An issue is resolved, but the project manager notices the issue log still shows it as open. What should the project manager ensure happens to maintain an accurate governance artifact?
- Delete the entry now that it is resolved
- Move it to the risk register as a residual risk
- Update the issue status to closed and record the resolution and date
- Leave it open in case the problem returns later
Correct answer: Update the issue status to closed and record the resolution and date
Keeping the issue log accurate requires marking resolved issues closed and documenting how and when they were resolved, preserving traceability. Leaving it open misrepresents status, deleting it loses the record and lessons, and moving a closed issue to the risk register confuses the artifacts.
- At project startup, the sponsor and PM agree on a charter that names the sponsor as the authority for budget changes above a set amount. This agreement is an example of establishing which element?
- A communications plan listing meeting frequencies
- A procurement strategy for selecting vendors
- A quality management plan defining acceptance criteria
- Governance: defining authority levels and decision rights for the project
Correct answer: Governance: defining authority levels and decision rights for the project
Naming who holds authority over certain budget decisions and at what threshold defines decision rights, which is the essence of governance. A communications plan addresses information flow, a quality plan addresses standards, and a procurement strategy addresses sourcing, none of which set decision authority.
- A project manager observes that issues raised by team members are being handled informally in hallway conversations, with no record of decisions. What governance-related risk does this create, and what is the best response?
- Lost traceability and accountability; route all issues through the issue log with documented decisions
- It only matters if the sponsor complains, so wait for that
- Replace the issue log with verbal updates to save time
- No risk; informal resolution is faster and should be encouraged
Correct answer: Lost traceability and accountability; route all issues through the issue log with documented decisions
Handling issues informally without records destroys traceability and accountability and can hide patterns or unresolved problems. Routing issues through the log with documented decisions restores governance discipline. Encouraging informality, waiting for complaints, or eliminating the log all worsen the gap.
- A program contains several projects, and the program manager asks each project manager to align their project governance with the program's governance framework. What does aligning to program governance primarily require of the project manager?
- Eliminating the project's own steering committee
- Adopting the program manager's personal leadership style
- Copying the program's detailed schedule into the project plan
- Ensuring project escalation paths, reporting, and decision thresholds are consistent with the program's framework
Correct answer: Ensuring project escalation paths, reporting, and decision thresholds are consistent with the program's framework
Aligning project governance with program governance means making escalation, reporting, and decision authority consistent so the layers fit together. Copying a schedule, mimicking a leadership style, or removing a needed governance body are not what alignment of governance frameworks entails.
- An issue has been escalated to the steering committee, which makes a decision. To preserve governance integrity, what should the project manager do with that decision?
- Forward it to all stakeholders as a binding contract amendment
- Record the decision, its rationale, and the responsible party in the appropriate project artifact
- Override the decision if the team disagrees with it
- Implement it verbally without recording it to save time
Correct answer: Record the decision, its rationale, and the responsible party in the appropriate project artifact
Governance decisions must be documented, including rationale and ownership, so they are traceable and enforceable. Acting verbally loses the record, overriding a legitimate governance decision undermines the structure, and treating it as a contract amendment misapplies the decision.
- While reviewing project artifacts, an auditor asks the project manager to show how decision authority was assigned and how exceptions are escalated. Which artifact best demonstrates this?
- The lessons learned register from the prior phase
- The governance plan documenting roles, authority levels, and escalation procedures
- The detailed cost estimate spreadsheet
- The team's vacation calendar
Correct answer: The governance plan documenting roles, authority levels, and escalation procedures
A governance plan (or equivalent section of the project management plan) documents roles, authority levels, and escalation procedures, exactly what the auditor requested. A lessons learned register, cost estimate, and calendar do not describe decision authority or escalation.
- A team member raises an issue but is unsure how urgent it is relative to other open issues. To manage issues effectively, what should the project manager do?
- Treat every issue as equally urgent and address them in the order received
- Assign a priority based on impact and urgency so resolution effort is focused appropriately
- Ask the team member to decide the priority alone
- Defer all issues until the next phase gate
Correct answer: Assign a priority based on impact and urgency so resolution effort is focused appropriately
Prioritizing issues by impact and urgency lets the team focus limited effort where it matters most. Treating all issues equally wastes effort, deferring everything to a gate lets problems fester, and leaving priority to a single member lacks the broader context the PM provides.
- A project manager is setting up governance for a project in a heavily regulated industry. Beyond internal decision rights, what additional governance consideration is especially important here?
- Reducing the number of approvals to move faster than regulators expect
- Excluding auditors from any decision visibility
- Treating regulatory rules as optional guidance
- Incorporating compliance and regulatory oversight requirements into the governance structure
Correct answer: Incorporating compliance and regulatory oversight requirements into the governance structure
In regulated environments, governance must embed compliance and regulatory oversight so the project meets legal obligations and audit expectations. Cutting approvals below regulatory minimums, hiding decisions from auditors, or treating rules as optional all expose the project to serious compliance failures.
- The issue log shows an issue that has been open well past its target resolution date with no progress. What is the most appropriate governance response by the project manager?
- Reassign it repeatedly among team members until someone fixes it
- Review why it stalled and, if it exceeds the owner's authority or capacity, escalate it per the defined path
- Remove the target date so the issue no longer appears overdue
- Extend the target date indefinitely without investigating
Correct answer: Review why it stalled and, if it exceeds the owner's authority or capacity, escalate it per the defined path
An overdue issue signals a blockage; the PM should investigate the cause and, where it exceeds the owner's authority or capacity, escalate through the defined path. Extending dates blindly, churning ownership, or deleting the date all mask the problem rather than resolving it.
- A project manager wants to confirm that the governance structure is actually functioning during execution, not just on paper. Which observation best indicates healthy project governance in practice?
- No decisions are ever escalated under any circumstances
- Decisions are being made at the appropriate authority levels and escalations follow the defined path without bottlenecks
- All decisions are routed to the sponsor regardless of size
- Team members make every decision by unanimous consensus
Correct answer: Decisions are being made at the appropriate authority levels and escalations follow the defined path without bottlenecks
Healthy governance shows decisions occurring at the right level and escalations flowing smoothly along defined paths. Routing everything to the sponsor signals over-centralization, never escalating may mean issues are stuck or hidden, and forcing unanimous consensus on everything is impractical and slow.
- A project manager is wrapping up a six-month software delivery. Before the team disbands, she wants to ensure the technical decisions and workarounds the developers discovered are not lost when they move to other projects. What is the most effective action to preserve this knowledge for the organization?
- Ask each developer to email her a private summary of their work that she keeps in her own files
- Schedule the knowledge capture for after the team has been released to their next assignments
- Facilitate a lessons learned session and store the captured insights in the organization's lessons learned repository
- Wait until the final project report is written and reference the issues there only if asked
Correct answer: Facilitate a lessons learned session and store the captured insights in the organization's lessons learned repository
Knowledge transfer for project continuity requires capturing both explicit and tacit knowledge while the team is still engaged, then storing it in a shared lessons learned repository so future projects can access it. Private files, deferring to the final report, or waiting until the team disperses all risk losing the knowledge.
- During a project, the team holds short retrospective sessions at the end of each iteration rather than waiting until the very end of the project. What is the primary benefit of capturing lessons learned throughout the project instead of only at closure?
- It guarantees that no further issues will arise in later phases of the project
- The team can apply improvements immediately to the remaining work of the same project
- It transfers all knowledge automatically to the organizational process assets
- It eliminates the need to hold a final lessons learned session at project closure
Correct answer: The team can apply improvements immediately to the remaining work of the same project
Capturing lessons learned continuously (e.g., in iteration retrospectives) lets the team apply improvements to its own ongoing work, rather than only benefiting future projects. It does not remove the need for a final review, automate asset updates, or guarantee no future issues.
- A project has reached its planned end. The customer has formally accepted all deliverables. As part of administrative closure, which document records the formal acknowledgment that the project's objectives have been met and the project is complete?
- The final report or formal acceptance documentation signed by the sponsor or customer
- The risk register with all risks marked as closed
- The stakeholder engagement assessment matrix
- The detailed work breakdown structure used during planning
Correct answer: The final report or formal acceptance documentation signed by the sponsor or customer
Closing a project requires formal sign-off—typically a final report and formal acceptance from the sponsor or customer—confirming objectives were met. The risk register, WBS, and stakeholder matrix are planning/monitoring artifacts, not the formal closure acknowledgment.
- A vendor has completed all contracted deliverables for a project. The project manager wants to formally close the agreement. What should the project manager do first to properly close the procurement?
- Release the project team and reassign them to new work
- Begin negotiating a new contract with the same vendor for unrelated work
- Verify that all contractual terms and deliverables have been satisfied before issuing formal contract closure
- Immediately destroy all procurement records to free up storage
Correct answer: Verify that all contractual terms and deliverables have been satisfied before issuing formal contract closure
Closing a procurement requires confirming that all terms, conditions, and deliverables of the contract have been met before the buyer issues formal closure. Releasing the team, destroying records (which must be archived), or starting unrelated negotiations are not the correct closure step.
- A multi-phase project is ending its design phase and preparing to begin the construction phase, which will be staffed by a different team. To support continuity, what is the most important closure activity for the design phase?
- Conduct a phase-end review and hand off documented deliverables and lessons learned to the construction team
- Close all financial accounts so the construction phase starts with a clean budget
- Cancel all remaining contracts and re-bid every supplier from scratch
- Delete the design artifacts since the construction team will create their own
Correct answer: Conduct a phase-end review and hand off documented deliverables and lessons learned to the construction team
Phase closure (a phase gate or transition) involves reviewing the phase, validating deliverables, and transferring documentation and lessons learned to the next phase's team to ensure continuity. Closing budgets entirely, re-bidding all suppliers, or deleting artifacts would undermine continuity.
- A project is being terminated early because the business case is no longer valid after a market shift. What should the project manager do regarding closure activities for this cancelled project?
- Reassign the team without recording why the project ended
- Skip all closure activities because the project did not finish its deliverables
- Perform formal closure activities, documenting the reason for termination and capturing lessons learned
- Continue spending the remaining budget so the funds are not wasted
Correct answer: Perform formal closure activities, documenting the reason for termination and capturing lessons learned
Even when a project is cancelled or terminated early, the project manager should still perform formal closure—documenting why it ended, the status of deliverables, and lessons learned—so the organization retains the knowledge. Skipping closure or wasting remaining budget is inappropriate.
- At closure, a project manager is releasing resources, archiving documents, and finalizing reports. Which of these is also a key administrative closure activity that ensures organizational assets are updated?
- Updating organizational process assets with final project records, lessons learned, and historical data
- Re-running the qualitative risk analysis on closed risks
- Re-baselining the schedule for the next reporting period
- Issuing new change requests for scope that was never approved
Correct answer: Updating organizational process assets with final project records, lessons learned, and historical data
Administrative closure includes updating organizational process assets (OPAs)—archiving final records, lessons learned, and historical information for future use. Re-baselining, issuing change requests for unapproved scope, or re-analyzing closed risks are not closure activities.
- A project's final deliverable—a new payroll system—is ready to be turned over to the operations and support team. What should the project manager ensure happens during this transition to operations?
- The project team retains ownership and continues to operate the system indefinitely
- All knowledge stays with the project manager in case questions arise later
- The receiving team is trained and the necessary documentation and support information are formally handed over
- The deliverable is released to operations without any documentation to save time
Correct answer: The receiving team is trained and the necessary documentation and support information are formally handed over
Transitioning a deliverable to operations requires a planned handover: training the receiving team and transferring documentation, support procedures, and warranties. Keeping ownership with the project team, omitting documentation, or hoarding knowledge would compromise sustained operation.
- During project execution, an experienced engineer who holds critical undocumented technical knowledge announces she is leaving the company in two weeks. What is the project manager's best immediate action to protect project continuity?
- Assume the remaining team can reverse-engineer the knowledge after she leaves
- Wait until the project closes to capture the knowledge in the lessons learned report
- Restrict her from sharing knowledge to avoid disrupting current work
- Arrange knowledge transfer sessions to capture her tacit knowledge and document it before she departs
Correct answer: Arrange knowledge transfer sessions to capture her tacit knowledge and document it before she departs
Tacit knowledge held by a departing expert is at risk of being lost. The project manager should proactively arrange knowledge-transfer sessions to capture and document it before she leaves. Waiting until closure, relying on reverse-engineering, or restricting sharing all threaten continuity.
- A project manager wants to make sure that lessons learned captured during the project are actually used by future project teams, not just filed away. What is the most effective approach?
- Email the lessons once to the current team and then delete the file
- Share the lessons only verbally during the project's final meeting
- Store lessons learned in an accessible, searchable knowledge repository and integrate review of it into future project planning
- Keep the lessons learned in a printed binder in the project manager's desk drawer
Correct answer: Store lessons learned in an accessible, searchable knowledge repository and integrate review of it into future project planning
For lessons learned to provide ongoing value, they must be stored in an accessible, searchable knowledge base and their review built into future planning processes. A printed binder, a one-time verbal share, or a deleted email all prevent reuse.
- A project is closing and the project manager is confirming that all deliverables have been completed and formally accepted by the customer. This validation of deliverable acceptance is most closely associated with which knowledge area's closing process?
- Project Cost Management, through earned value analysis
- Project Communications Management, through stakeholder analysis
- Project Integration Management, through the Close Project or Phase process
- Project Risk Management, through risk response planning
Correct answer: Project Integration Management, through the Close Project or Phase process
Confirming completion and formal acceptance of deliverables and finalizing all activities is part of Close Project or Phase, which sits within Project Integration Management. Risk planning, earned value, and stakeholder analysis are not the closing integration process.
- After a long project, the project manager schedules a final lessons learned workshop. To get the most value, who should ideally participate?
- Only the newest team members who joined at the end
- Only senior executives who funded the project
- Only the project manager, who knows the project best
- Key team members and relevant stakeholders who were involved across the project's work
Correct answer: Key team members and relevant stakeholders who were involved across the project's work
A productive lessons learned session draws on the diverse perspectives of team members and relevant stakeholders who participated in the work, surfacing what went well and what could improve. Limiting it to one person, only executives, or only late joiners loses critical insight.
- A predictive project has finished delivering, but several minor punch-list items remain outstanding with a subcontractor. The customer is pressing to close the contract. What is the project manager's most appropriate action?
- Refuse to discuss closure until the subcontractor finishes years later
- Document the outstanding items, obtain agreement on how they will be resolved, and update closure records accordingly
- Pay the subcontractor in full and assume the items are no longer relevant
- Close the contract immediately and ignore the outstanding punch-list items
Correct answer: Document the outstanding items, obtain agreement on how they will be resolved, and update closure records accordingly
Procurement closure requires resolving or formally documenting outstanding items and reaching agreement on their disposition before finalizing the contract and updating records. Ignoring open items, indefinitely refusing closure, or paying without resolving the work are all improper.
- In an organization that values knowledge sharing, the project manager establishes communities of practice and regular knowledge-sharing forums across project teams. What is the main purpose of these knowledge management practices?
- To replace the need for a project management plan
- To eliminate the requirement for any project documentation
- To enable individuals to share and reuse both explicit and tacit knowledge across the organization
- To formally close out individual project contracts
Correct answer: To enable individuals to share and reuse both explicit and tacit knowledge across the organization
Project knowledge management aims to share and reuse existing knowledge (explicit and tacit) and create new knowledge to achieve objectives. Communities of practice support this. It is unrelated to contract closure, replacing the PM plan, or removing documentation.
- A project manager is finalizing closure and discovers that no formal acceptance was ever obtained for two early deliverables, though the customer used them. What should the project manager do before declaring the project complete?
- Issue a change request to add the deliverables back into scope
- Declare the project complete since the customer is already using the deliverables
- Remove those deliverables from the scope statement retroactively
- Obtain formal acceptance for those deliverables to ensure all are validated before closure
Correct answer: Obtain formal acceptance for those deliverables to ensure all are validated before closure
Project closure requires that all deliverables be formally accepted. The PM should secure formal acceptance for the missing items before declaring completion. Assuming acceptance, retroactively altering scope, or adding already-delivered items via change request are incorrect.
- As part of closing a phase, a project manager compiles a transition plan describing how the phase's outputs will be carried forward. What information is most important to include in this transition plan?
- The personal performance ratings of each team member
- The deliverables being transferred, their status, and the responsibilities of the receiving party
- The vendor's internal pricing strategy for future bids
- A detailed list of every email sent during the phase
Correct answer: The deliverables being transferred, their status, and the responsibilities of the receiving party
A transition (or handover) plan should clearly specify what is being transferred, its current status, and who is responsible for receiving and continuing the work. Email logs, individual performance ratings, and a vendor's pricing strategy are not appropriate transition-plan content.
- A project manager notices the team repeatedly solving problems that a prior project already solved, wasting effort. To address this at the start of future projects, what should be incorporated into project planning?
- A review of historical information and lessons learned from previous similar projects
- An assumption that no prior project is ever comparable
- A rule that each new project must start with no reference to prior work
- A prohibition on consulting any past project documentation
Correct answer: A review of historical information and lessons learned from previous similar projects
Reusing organizational knowledge—reviewing historical information and lessons learned from similar past projects during planning—prevents teams from repeating mistakes and re-solving solved problems. Ignoring or prohibiting prior work defeats the purpose of knowledge management.
- During closure of an agile-delivered product, the team conducts a final retrospective. Beyond capturing lessons, what additional closure-related action ensures the increment delivers ongoing value?
- Reassign accountability for benefits back to the now-disbanded team
- Cancel all monitoring of the product so the team can move on completely
- Confirm the released product is transitioned to the group responsible for ongoing support and benefit realization
- Delete the product backlog so it cannot be referenced again
Correct answer: Confirm the released product is transitioned to the group responsible for ongoing support and benefit realization
Even in agile delivery, closure includes transitioning the released product to the team responsible for ongoing support and benefit realization. Cancelling monitoring, deleting the backlog, or assigning benefits to a disbanded team would jeopardize sustained value.
- A project manager is archiving project records at closure. Which records should be archived to support future audits and provide historical reference?
- Nothing, since records are no longer needed once a project ends
- Only personal notes the project manager wants to keep
- Project documents, the project management plan, deliverable acceptance records, and lessons learned
- Only the final invoice from the largest vendor
Correct answer: Project documents, the project management plan, deliverable acceptance records, and lessons learned
At closure, the project's complete records—plans, project documents, acceptance records, and lessons learned—are archived as organizational process assets for audits and historical reference. Keeping only one invoice, only personal notes, or nothing fails this requirement.
- A project manager is determining how knowledge will be managed across a complex, multi-team program. Which combination of tools best supports both explicit and tacit knowledge sharing?
- Only informal hallway conversations with no documentation
- Only a single shared spreadsheet with no discussion forums
- Only a locked archive accessible to the project manager alone
- Knowledge management tools such as a document repository plus interactive methods like workshops and storytelling
Correct answer: Knowledge management tools such as a document repository plus interactive methods like workshops and storytelling
Effective knowledge management blends information management tools (repositories for explicit knowledge) with interaction-based techniques (workshops, storytelling, communities of practice) that surface tacit knowledge. A lone spreadsheet, only informal chats, or a locked archive each cover only part of the need.
- At the formal close of a project, the sponsor asks the project manager to confirm that the project met its objectives. Where should the project manager primarily look to make this assessment?
- The personal opinions of the newest team members
- The project's success criteria and acceptance criteria defined in the project charter and scope baseline
- The competitor's recent product announcements
- The marketing department's promotional materials
Correct answer: The project's success criteria and acceptance criteria defined in the project charter and scope baseline
To confirm objectives were met, the PM compares results against the documented success and acceptance criteria established in the charter and scope baseline. New members' opinions, marketing materials, and competitor announcements are not the basis for measuring project success.
- A project manager realizes that valuable knowledge generated during the project is held informally and could be lost. To convert this tacit knowledge into a reusable organizational asset, what should the project manager do?
- Restrict access so only the original holders can ever use it
- Assume it will naturally pass to others without any effort
- Leave the knowledge undocumented since it lives in people's heads
- Facilitate discussion and capture the knowledge in documented form for the knowledge base
Correct answer: Facilitate discussion and capture the knowledge in documented form for the knowledge base
Converting tacit knowledge into explicit, reusable form requires facilitated discussion and documentation so it can be stored in the organization's knowledge base. Leaving it undocumented, restricting it, or assuming automatic transfer all risk permanent loss of the knowledge.
- A project to launch a healthcare data platform must meet HIPAA privacy rules, OSHA workplace safety standards for the on-site install team, and an internal corporate coding standard. As the project manager begins planning compliance, what is the MOST useful first step?
- Ask the team to self-certify that they will follow all applicable rules
- Add a single 'compliance' line item to the risk register and assign it to the sponsor
- Schedule the final compliance audit so the date is locked before work begins
- Classify each requirement into its compliance category and determine its source and consequences of non-compliance
Correct answer: Classify each requirement into its compliance category and determine its source and consequences of non-compliance
Planning project compliance starts with identifying and classifying compliance requirements by category (legal/regulatory, safety, internal standards), their source, and the consequences of non-compliance. Only after classification can you analyze threats and build appropriate methods. The other options skip the foundational classification step.
- Midway through a predictive construction project, a new regional building code takes effect that the current design does not satisfy. What should the project manager do FIRST?
- Immediately stop all work until the new code is fully understood by the legal department
- Analyze the gap between the current deliverables and the new requirement and assess the impact on scope, cost, and schedule
- Continue as planned because the design was approved before the code changed
- Remove the affected scope so the project can finish on its original baseline
Correct answer: Analyze the gap between the current deliverables and the new requirement and assess the impact on scope, cost, and schedule
When a compliance requirement changes, the PM must first measure the extent to which the project already complies and analyze the impact of the gap. This drives an informed change request. Ignoring the code, deleting scope, or halting everything without analysis are reactive and not grounded in impact assessment.
- A project manager is building a compliance management approach for a project subject to environmental regulations. Which activity BEST represents proactively managing potential threats to compliance rather than reacting to violations?
- Assuming the contractor's standard process already covers all environmental rules
- Identifying compliance threats, prioritizing them by likelihood and impact, and defining preventive controls before work begins
- Waiting for the regulator's inspection report and correcting only the items it flags
- Documenting violations after they occur so they can be reported in the lessons learned
Correct answer: Identifying compliance threats, prioritizing them by likelihood and impact, and defining preventive controls before work begins
Proactive compliance management means analyzing potential threats to compliance, prioritizing them, and putting preventive measures in place before issues arise. Reacting to inspections, logging violations after the fact, or assuming a vendor has it covered are reactive and leave the project exposed to non-compliance penalties.
- During execution, a quality test reveals that a shipped batch of a regulated medical device does not meet a mandatory safety standard. Which response BEST reflects appropriate handling of a compliance non-conformance?
- Reassign the testing task to a different team member and retest later
- Record the defect quietly so it does not alarm the customer or delay the next milestone
- Negotiate with the regulator to waive the standard for this one batch
- Determine the necessary corrective and preventive actions, communicate the issue to stakeholders, and verify the fix restores compliance
Correct answer: Determine the necessary corrective and preventive actions, communicate the issue to stakeholders, and verify the fix restores compliance
A confirmed compliance non-conformance on a regulated product requires identifying and executing corrective/preventive actions, transparent stakeholder communication, and verification that compliance is restored. Hiding the defect, seeking informal waivers, or merely reassigning the task fail to address the safety and regulatory obligation.
- A sponsor asks the project manager to confirm that a software release is compliant before go-live. What provides the STRONGEST evidence that compliance requirements have actually been met?
- Documented compliance verification results, such as audit findings and test records mapped to each requirement
- A verbal assurance from the development lead that everything was followed
- The original compliance plan showing what the team intended to do
- The fact that no compliance complaints have been received from customers yet
Correct answer: Documented compliance verification results, such as audit findings and test records mapped to each requirement
Demonstrating compliance requires objective evidence: verification and validation results, audit findings, and test records traceable to each requirement. A plan states intent, verbal assurance is not evidence, and the absence of complaints does not prove compliance was achieved.
- A project must comply with both a national data-protection law and a stricter company-internal data policy that conflict in one area. How should the project manager handle the conflicting requirements?
- Average the two requirements to create a middle-ground rule for the project
- Always follow the internal policy because it is owned by the organization
- Always follow the national law because external rules outrank internal ones
- Apply the more stringent requirement where they conflict and escalate to governance to confirm the approach
Correct answer: Apply the more stringent requirement where they conflict and escalate to governance to confirm the approach
When compliance requirements conflict, the prudent approach is generally to meet the more stringent requirement so both are satisfied, while escalating to governance for confirmation and documentation. Blindly favoring one source or 'averaging' rules can leave the project in violation of the stricter obligation.
- Before approving project funding, leadership wants to know whether the expected returns justify the investment. Which document is designed to capture this justification and link the project to business need?
- The project schedule, which sequences the activities and milestones
- The communications management plan, which defines stakeholder reporting
- The responsibility assignment matrix, which maps work to people
- The business case, which documents the need, expected benefits, costs, and financial justification
Correct answer: The business case, which documents the need, expected benefits, costs, and financial justification
The business case captures the business need, options analysis, expected benefits, costs, and financial justification (such as ROI) used to decide whether to fund a project. The schedule, communications plan, and RACI matrix support execution but do not justify the investment.
- Two candidate projects are competing for the same budget. Project A has an NPV of $250,000 and Project B has an NPV of -$40,000, both over the same horizon. Using net present value as the decision criterion, which project should be selected and why?
- Project B, because a smaller absolute number is easier to deliver
- Either project, because NPV does not influence project selection
- Project A, because a positive NPV indicates the project is expected to create value above its cost of capital
- Project A, because it has the larger team and therefore more capacity
Correct answer: Project A, because a positive NPV indicates the project is expected to create value above its cost of capital
Net present value reflects value created above the required rate of return; a positive NPV indicates expected value creation, while a negative NPV indicates value destruction. Project A's positive NPV makes it the value-adding choice. Team size is irrelevant, and NPV is a core selection metric.
- A project manager wants to track whether the organization is actually realizing the benefits promised in the business case after deliverables are handed over. Which tool is specifically intended for this purpose?
- A change log that records approved and rejected change requests
- A benefits management plan that defines target benefits, metrics, owners, and the timeframe for realization
- A procurement statement of work that defines vendor deliverables
- A daily stand-up agenda that lists the team's tasks for the day
Correct answer: A benefits management plan that defines target benefits, metrics, owners, and the timeframe for realization
The benefits management plan documents the target benefits, how and when they will be measured, the metrics, and the owners responsible for realization, often extending beyond project closure. Stand-ups, change logs, and SOWs serve other purposes and do not track benefits realization.
- During an agile delivery, a product owner must decide the order in which features are built. Which approach BEST ensures the project delivers business value as early as possible?
- Prioritize and sequence the backlog so the highest-value features are delivered in the earliest iterations
- Defer all releases until every planned feature is complete
- Build the easiest features first regardless of their value to the customer
- Order the backlog alphabetically to keep the list easy to maintain
Correct answer: Prioritize and sequence the backlog so the highest-value features are delivered in the earliest iterations
Maximizing early value delivery means ordering the backlog so the highest-value items are produced first, allowing incremental benefit realization and early feedback. Sequencing by ease, alphabetics, or withholding value until full completion delays or undermines value delivery.
- A long-running program's strategic context shifts when the company pivots to a new market. What should the project manager do to keep the project aligned with business value?
- Add more features to the project to make it appear more valuable
- Reassess the project's benefits and value against the new strategy and recommend continuing, adjusting, or terminating it
- Wait for the steering committee to issue a stop order before reviewing anything
- Continue executing the original scope because the charter was already approved
Correct answer: Reassess the project's benefits and value against the new strategy and recommend continuing, adjusting, or terminating it
Delivering value requires continually evaluating whether the project still supports organizational strategy. When strategy changes, the PM should reassess benefits and value and recommend continuing, adjusting, or terminating the project. Blindly continuing or padding scope ignores the alignment obligation.
- Leadership asks how soon the project's cumulative cash inflows will recover the initial investment. Which financial measure directly answers this question?
- Return on investment, which expresses net gain as a percentage of cost
- Benefit-cost ratio, which compares total benefits to total costs
- Internal rate of return, which is the discount rate that sets NPV to zero
- Payback period, which is the time required for cumulative benefits to equal the initial cost
Correct answer: Payback period, which is the time required for cumulative benefits to equal the initial cost
The payback period measures how long it takes for cumulative inflows to recover the initial investment, directly answering 'how soon.' IRR, BCR, and ROI are valid value metrics but express rate, ratio, and percentage gain respectively, not the time to recoup the investment.
- A project's deliverables are technically complete, but the expected operational savings have not yet appeared in the business. What is the project manager's MOST appropriate action regarding value?
- Reopen the project scope and add work until the savings materialize
- Declare full value achieved because all scope was delivered on time
- Remove the savings target from the business case so the project looks successful
- Confirm that ownership for tracking and realizing the remaining benefits is transferred to the operational owner with defined metrics
Correct answer: Confirm that ownership for tracking and realizing the remaining benefits is transferred to the operational owner with defined metrics
Many benefits are realized after deliverables are handed over, so the PM should ensure benefit ownership, metrics, and tracking transition to the operational owner. Equating delivered scope with realized value, padding scope, or editing the business case to hide a gap all misrepresent value delivery.
- A project manager is asked to evaluate a proposed initiative using a benefit-cost ratio. The expected benefits total $1.2 million and the expected costs total $800,000. What does the resulting ratio indicate about the initiative's value?
- The ratio is 1.5, meaning expected benefits exceed costs, which supports proceeding on value grounds
- The ratio is 1.0, meaning the initiative exactly breaks even
- The ratio cannot be computed without the discount rate
- The ratio is 0.67, meaning costs exceed benefits, so it should be rejected
Correct answer: The ratio is 1.5, meaning expected benefits exceed costs, which supports proceeding on value grounds
Benefit-cost ratio equals benefits divided by costs: $1.2M / $0.8M = 1.5. A BCR greater than 1 indicates benefits outweigh costs, supporting the value case. The reciprocal (0.67) inverts the formula, 1.0 would require equal amounts, and a simple BCR does not require a discount rate.
- While planning, a project manager discovers that a required regulatory permit will take twelve weeks to obtain and the work that depends on it is scheduled in week four. What is the BEST way to integrate this compliance requirement into the plan?
- Treat the permit as a low-priority task to be handled near project closure
- Add the permit acquisition as an explicit predecessor activity in the schedule and start it early enough to avoid delaying dependent work
- Begin the dependent work on schedule and apply for the permit in parallel afterward
- Assume the regulator will expedite the permit if the deadline approaches
Correct answer: Add the permit acquisition as an explicit predecessor activity in the schedule and start it early enough to avoid delaying dependent work
Compliance obligations such as permits must be built into the schedule as real activities with their own lead time and dependencies. Adding the permit as a predecessor and starting it early protects the schedule. Starting dependent work first risks non-compliance, and deferring or assuming expedited handling is a planning failure.
- A steering committee wants a single ongoing indicator that shows whether a project remains worth funding as it progresses. Which practice BEST supports this value-based oversight throughout the project?
- Measuring solely the percentage of tasks completed against the schedule
- Counting the number of change requests submitted each month
- Reviewing only the final benefits report after the project closes
- Periodically revisiting the business case and benefits metrics at phase gates to confirm continued justification
Correct answer: Periodically revisiting the business case and benefits metrics at phase gates to confirm continued justification
Continued justification is maintained by revisiting the business case and benefits metrics at phase gates or regular reviews, allowing leadership to continue, adjust, or stop the project. Waiting until closure is too late, and task completion or change-request counts measure activity, not ongoing business value.
- Midway through an 18-month project, the national legislature passes a new data-residency law requiring that all customer records be stored on servers physically located within the country. The project's architecture currently relies on a foreign-hosted cloud region. What should the project manager do FIRST?
- Immediately rearchitect the solution to use a domestic data center to ensure the team stays compliant
- Add a new risk to the risk register and continue executing the original plan until the next phase gate
- Assess how the new regulation impacts the project scope and backlog, then bring recommended options to the change control process
- Escalate to the sponsor and pause all work until legal counsel confirms the law applies
Correct answer: Assess how the new regulation impacts the project scope and backlog, then bring recommended options to the change control process
The PM should survey external changes and then assess and prioritize their impact on scope/backlog before recommending options. Evaluating the impact and routing options through change control is the correct first step. Rearchitecting immediately skips analysis and bypasses governance; merely logging a risk ignores a change that has already occurred; and pausing all work overreacts before the impact is even understood.
- A project manager wants a structured way to continually scan the external environment for shifts in political, economic, social, technological, legal, and environmental factors that could affect the project's scope. Which tool is BEST suited to this purpose?
- Make-or-buy analysis
- Earned value analysis
- PESTLE analysis
- Critical path method
Correct answer: PESTLE analysis
PESTLE (Political, Economic, Social, Technological, Legal, Environmental) is the framework used to systematically survey external business environment changes. Make-or-buy analysis supports procurement decisions, earned value analysis measures cost and schedule performance, and the critical path method analyzes the schedule network, none of which scans the external environment.
- During execution, a competitor releases a product that makes one of the project's planned features obsolete, while regulators simultaneously mandate a new accessibility feature. The product owner asks the PM how to respond. What is the MOST appropriate recommendation?
- Defer all backlog decisions until the project's final iteration to gather more market data
- Cancel the obsolete feature unilaterally because the market has moved on
- Keep delivering the backlog in its original priority order to honor the baseline commitment
- Reprioritize the backlog to deprioritize the obsolete feature and elevate the mandated accessibility work, then validate the trade-offs with stakeholders
Correct answer: Reprioritize the backlog to deprioritize the obsolete feature and elevate the mandated accessibility work, then validate the trade-offs with stakeholders
Assess the impact of external changes on the backlog and recommend options such as reprioritization, then confirm trade-offs with stakeholders. Holding the original order ignores a clear external shift; acting unilaterally bypasses the product owner and stakeholders; and deferring until the final iteration wastes the opportunity to deliver value sooner and meet the mandate on time.
- A new technology emerges that could deliver the same project outcome at lower cost, but adopting it would require significant rework. What should the project manager do when evaluating this external change?
- Analyze the impact on scope, schedule, and cost, then present recommended options and their trade-offs for a decision
- Adopt the new technology right away because lower cost always benefits the business case
- Document it as a lesson learned for the next project and take no action now
- Reject the new technology because changing approach mid-project is too disruptive
Correct answer: Analyze the impact on scope, schedule, and cost, then present recommended options and their trade-offs for a decision
Assess the impact of a technology change on scope, schedule, and cost and recommend options for the appropriate decision-makers. Adopting immediately ignores rework cost and trade-offs; rejecting outright dismisses a potentially valuable opportunity without analysis; and shelving it as a lesson learned defers value the current project could capture.
- A geopolitical conflict disrupts the supply of a critical hardware component sourced from one region. The project manager has surveyed the situation. What should happen NEXT?
- Wait until the component is actually unavailable before changing anything in the plan
- Remove the affected deliverables from scope to protect the schedule baseline
- Assess and prioritize the impact on the project's scope and backlog, then recommend options such as alternative suppliers or schedule adjustments
- Transfer the entire issue to the procurement department and resume normal work
Correct answer: Assess and prioritize the impact on the project's scope and backlog, then recommend options such as alternative suppliers or schedule adjustments
After surveying an external change, the PM assesses and prioritizes its impact on scope/backlog and recommends options. Waiting for the disruption to fully materialize forfeits proactive response; removing deliverables unilaterally is a scope decision that needs analysis and stakeholder input; and handing off the issue entirely ignores the PM's responsibility to evaluate scope impact.
- A project manager establishes a recurring agenda item to review regulatory, market, and technology trends at every iteration review for the life of the project. Which Business Environment responsibility does this practice BEST demonstrate?
- Continually reviewing the external business environment for impacts on scope and backlog
- Assessing organizational culture to support change adoption
- Planning and managing project compliance with internal policies
- Delivering project benefits to the benefits owner
Correct answer: Continually reviewing the external business environment for impacts on scope and backlog
Continually reviewing the external environment for impacts on scope/backlog is the responsibility being operationalized by a recurring review cadence. Managing compliance, delivering benefits, and assessing organizational culture are separate Business Environment tasks.
- A project will significantly change how an operations team performs its daily work. Before designing a rollout, the project manager wants to understand how receptive the organization is likely to be and what norms and behaviors might help or hinder adoption. What should the PM do?
- Assess the organizational culture to determine how it will affect the change and what actions are required
- Build a detailed training schedule immediately so the team is ready on go-live day
- Add a contingency reserve to the budget to absorb the cost of resistance
- Escalate to the sponsor to mandate the change so resistance is not an option
Correct answer: Assess the organizational culture to determine how it will affect the change and what actions are required
Assessing organizational culture is the foundation for planning an effective change approach. Jumping to a training schedule skips the readiness and culture assessment that shapes the plan; mandating the change ignores genuine adoption and resistance; and adding reserve treats resistance as a cost item rather than something to be actively managed.
- After assessing the organization, a project manager determines that a major change is needed for the new system to be adopted, but several departments are not yet ready. What is the MOST appropriate next action?
- Reassign responsibility for adoption entirely to the functional managers
- Delay go-live indefinitely until every department voluntarily reaches full readiness
- Deliver the system as planned and let each department adapt on its own
- Recommend, plan, and facilitate change activities such as communication, training, and readiness support
Correct answer: Recommend, plan, and facilitate change activities such as communication, training, and readiness support
Recommending, planning, and facilitating the changes needed for adoption encompasses communication, training, and readiness activities. Delaying indefinitely is not a plan and may forfeit value; delivering and leaving departments to cope alone abandons the PM's role in supporting change; and fully offloading adoption ignores the PM's facilitation responsibility.
- A project manager is preparing a change adoption plan and wants a model that gauges whether individuals are aware of, want, are able to perform, and will sustain a change. Which model is the project manager applying?
Correct answer: ADKAR
ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement) is a change management model used to assess individual readiness and sustainment. RACI clarifies roles and responsibilities, SWOT analyzes strengths/weaknesses/opportunities/threats, and MoSCoW prioritizes requirements, none of which measure individual change adoption.
- An enterprise reorganization shifts the project's sponsoring department under a new executive with different priorities partway through delivery. What should the project manager do?
- Treat the reorganization as outside the project's concern and ignore it
- Evaluate the impact of the organizational change on the project and determine the required actions
- Continue executing exactly as before, since the deliverables have not changed
- Immediately cancel the project because its original sponsor is gone
Correct answer: Evaluate the impact of the organizational change on the project and determine the required actions
Evaluating the impact of organizational change on the project and determining required actions is exactly what a sponsorship shift demands. Continuing unchanged ignores potential changes to priorities, funding, and alignment; treating it as irrelevant overlooks a direct governance change; and cancelling outright is a premature reaction before any impact assessment.
- As a project nears completion, the project manager realizes that going live will substantially alter how three other business units operate and could affect the company's broader strategy. What should the PM do?
- Delay the project's strategic alignment review until after the warranty period ends
- Evaluate the impact of the project on the organization and determine the actions required to support the transition
- Limit communication to the project team to avoid alarming the other units prematurely
- Hand over the deliverables and consider the project complete once acceptance is signed
Correct answer: Evaluate the impact of the project on the organization and determine the actions required to support the transition
Evaluating the impact of the project on the organization and determining required actions means the PM should proactively plan to support the affected units' transition. Restricting communication undermines readiness; treating sign-off as the end ignores adoption and benefit realization; and postponing the alignment review leaves the broader organizational impact unmanaged when it matters most.
- A team using an adaptive (agile) approach learns that a new market entrant has shifted customer expectations. The product owner wants to keep the project aligned with external realities. How should external environment changes BEST be handled in this context?
- Open a formal change request for every backlog re-ordering decision before reprioritizing
- Escalate each market signal to the change control board for individual approval
- Reflect the change by re-ordering and refining the product backlog during regular grooming and review events
- Freeze the backlog until the current release is fully delivered to preserve stability
Correct answer: Reflect the change by re-ordering and refining the product backlog during regular grooming and review events
In adaptive environments, responding to external changes is handled by continually refining and re-prioritizing the product backlog. Freezing the backlog defeats agility and ignores the market shift; routing each re-ordering through formal change requests or the CCB imposes predictive governance that does not fit backlog management and slows responsiveness.
- During the project, the PM identifies several external factors that could affect scope but with widely varying likelihood and severity. What should the project manager do before recommending any scope or backlog changes?
- Wait for the steering committee to tell the team which factors matter
- Assess and prioritize the impacts so that the most significant changes are addressed first
- Recommend changes for every identified factor to be thorough
- Address only the factors that are easiest and least costly to act on
Correct answer: Assess and prioritize the impacts so that the most significant changes are addressed first
Assess and prioritize the impact of external changes on scope/backlog before recommending options. Acting on every factor wastes effort and dilutes focus; choosing the easiest factors ignores severity and value; and waiting passively for the steering committee abdicates the PM's analytical responsibility to inform that decision.
- A change manager argues that adoption will fail because employees do not understand why the new process is being introduced. Using the ADKAR model, which element is currently lacking?
- Knowledge of how to perform the new process
- Reinforcement to sustain the change
- Ability to implement the required skills
- Awareness of the need for the change
Correct answer: Awareness of the need for the change
In ADKAR, Awareness is about understanding the reason and need for the change; if employees do not understand why, Awareness is the gap. Ability concerns demonstrating the new skills, Reinforcement concerns sustaining the change over time, and Knowledge concerns knowing how to perform the change, none of which address the missing understanding of why.
- A new industry standard becomes effective during a project. The PM evaluates it and concludes the project's deliverables already exceed the standard, so no rework is required. What should the project manager do?
- Stop monitoring industry standards because this one has been resolved
- Add rework to the plan anyway to be safe, since the standard is now mandatory
- Remove the related scope items since the standard makes them redundant
- Document the assessment and its conclusion, then continue monitoring the external environment for further changes
Correct answer: Document the assessment and its conclusion, then continue monitoring the external environment for further changes
Assess external changes and continually review the environment; when no action is needed, the right step is to document the conclusion and keep monitoring. Adding unnecessary rework wastes resources for a standard already met; stopping monitoring abandons the continual-review responsibility; and removing scope items misreads compliance as making deliverables redundant.
- To strengthen organizational change support, a project manager builds a rollout plan that defines knowledge transfer, training, and readiness activities timed to the deployment. Which Business Environment objective does this BEST serve?
- Documenting an agreement on ownership for ongoing benefit realization
- Facilitating the changes so the organization is prepared to adopt and sustain the project's outcomes
- Surveying the external business environment for regulatory and market changes
- Classifying and analyzing categories of compliance requirements
Correct answer: Facilitating the changes so the organization is prepared to adopt and sustain the project's outcomes
A rollout plan covering knowledge transfer, training, and readiness facilitates the changes needed for adoption and sustainment. Surveying the external environment, documenting benefit ownership, and classifying compliance categories are distinct Business Environment tasks.