PMI Exam Practice Questions - Page 20

PMI Practice Questions, Discussions & Exam Topics by our Authors

A newly assigned project manager is reviewing the project management plan and realizes that the project is running behind schedule. What ...

When a newly assigned project manager realizes that the project is running behind schedule, the appropriate course of action should focus on understanding the reasons behind the delay and ensuring that the project management plan is revised and aligned with the current reality, while maintaining proper governance. Analysis of options: - Option A: Negotiate with the project sponsor immediately and establish a new project charter. - The project charter is created at the start of the project and serves as the foundational document outlining the project's objectives, stakeholders, and constraints. It is not typically adjusted in response to delays or schedule changes unless the scope or fundamental direction of the project changes significantly. Changing the charter may not address the immediate need to get the project back on track, especially if the core objectives haven't shifted. This option is not ideal in this context. - Option B: Modify the project management plan and get approval from relevant stakeholders. - This is a reasonable option. The project management plan includes the schedule and various other components like scope, budget, and risk management. If the project is behind schedule, modifying the plan to reflect new realities (e.g., adjusted timelines, revised milestones) and seeking stakeholder approval ensures that all parties are aligned with the new approach. This is a structured and appropriate response to addressing delays, and it ensures that changes are documented and authorized. - Opti...

Author: Madison · Last updated May 4, 2026

A key business stakeholder sent emails to the developers with complaints based on the last few sprints. The developers forwarded the emails to the project manager but have not yet responde...

In this situation, the project manager needs to address the issue raised by the key business stakeholder and ensure clear and effective communication. The developers have already forwarded the complaints but have not responded yet, which means there is a communication gap that needs to be resolved quickly. Analysis of options: - Option A: Analyze and perform a root cause analysis (RCA). - While performing a root cause analysis (RCA) could be useful for understanding underlying problems, it may not be the most immediate and effective action. The stakeholder's complaint needs to be addressed promptly with a response, and a root cause analysis is a more in-depth process that could take time. In this case, the immediate need is to address the stakeholder's concern and initiate a response, rather than diving into an RCA. - Option B: Add the situation to the issue log. - Adding the situation to the issue log might be helpful for tracking the problem, but this does not directly resolve the communication gap. The issue log can be useful for documentation and future reference, but it does not solve the problem of not responding to the stakeholder. The project manager should take action beyond logging the issue to ensure prompt reso...

Author: Isabella1 · Last updated May 4, 2026

A project manager is made aware that there are defects in the parts provided by a supplier, which are causing delays in the testing phase. The supplier claims that all parts have been delivered as per the contract. If the defects are not fixed ...

In this situation, the project manager must focus on resolving the issue without causing unnecessary escalation or taking overly aggressive actions, as it may affect the long-term supplier relationship or introduce delays. Here's an analysis of the options: A) Request a cancellation of the procurement contract with the supplier and impose a penalty. - Rejected: This option is extreme, especially at this stage, and could jeopardize the working relationship with the supplier. It would also introduce delays in finding an alternative supplier. Since the issue seems to be related to defects rather than a total failure of the supplier to meet their obligations, a more collaborative approach is preferable. Additionally, penalties and cancellation could lead to further delays, exacerbating the problem. B) Review the procurement contract and ask the supplier to negotiate a solution. - Selected: This is the most reasonable option. Reviewing the contract allows the project manager to confirm whether the supplier has met their obligations or if there's flexibility for negotiation. The supplier could be given a chance to rectify the defects within the specified timeline. Negotiation enables the project manager to align both parties on a solution, potentially avoiding legal or financial disputes and preventing further delays in the project. It fosters a cooperative approach, maintaining the business relationship and ensu...

Author: Siddharth · Last updated May 4, 2026

A project manager is leading the development of a mobile banking application using a hybrid approach. The team has been holding daily standup meetings each workday morning. Due to an unexpected issue, 50% of the team has to work from home. The bank's management directed the team not to have in-person daily standups. Various te...

In this scenario, the project manager must address the communication issues arising from the shift to remote work while also maintaining the momentum and coordination of the team. Here's an analysis of the options: A) Delegate authority to the team members and ask them to submit weekly status reports instead. - Rejected: While delegating authority can be beneficial in some situations, asking team members to submit weekly status reports instead of holding daily standups would likely lead to a loss of real-time communication and quick issue resolution. Daily standups are important for maintaining team synchronization and addressing issues promptly. Weekly reports would be too infrequent to replace the daily information sharing and might not resolve problems in time to keep the project on track. B) Postpone the daily standups and ask the team members to update the project manager daily via messaging. - Rejected: Relying on messaging updates instead of structured standups may create confusion, as there's no guarantee that all team members will provide consistent or comprehensive information. It also risks breaking down communication clarity and flow. The real-time, interactive nature of standups is crucial for understanding daily challenges and promoting team cohesion. This option would reduce the effectiveness of communication and transparency. C) Hold virtual daily standups each workday morning and use collaboration tools to manage project updates. - Selected: This is the most appropriate option. The ...

Author: SolarFalcon11 · Last updated May 4, 2026

A project manager finds that there are knowledge gaps in the project team relating to the core competencies required to deliver the desired results. W...

In this scenario, the project manager faces knowledge gaps within the team that are critical for achieving the desired results. The primary goal should be to address these gaps effectively and efficiently while minimizing disruption to the project. Here's an analysis of the options: A) Plan to hire more experienced team members and lay off a few of the existing team members. - Rejected: Hiring new team members and laying off existing ones is a drastic and costly solution. It may also cause delays due to the time required for recruitment, onboarding, and training. This approach could negatively impact team morale and stability, and is not a practical way to address knowledge gaps in the short term. It's more efficient to invest in upskilling the current team rather than making significant personnel changes. B) Communicate the situation to the customer and inform them about potential delays in delivery. - Rejected: While transparency is important, immediately informing the customer about delays due to internal team knowledge gaps might be premature. Before reaching out to the customer, the project manager should first attempt to resolve the issue internally by providing training or support. Prematurely communicating potential delays may create unnecessary concern and damage client relationships, especially when a solution is likely achievable through internal efforts. ...

Author: Carlos Garcia · Last updated May 4, 2026

DRAG DROP -A project manager is leading a project in which key performance indicators (KPIs) are measured through earned value management (EVM).Match ea...

n...

Author: Manish · Last updated May 4, 2026

A team is testing a product on multiple radio frequencies. The project manager is informed that a new government policy, expected in 2 weeks, will mandate companies to obtain approval and licensing for frequency testing. The team has completed 80% of the testing and needs 4 weeks to c...

In this scenario, the project manager must take proactive steps to handle the impending regulatory change while ensuring that the testing process is not unduly delayed. Here's an analysis of the options: A) Hire a vendor with the required expertise and infrastructure to complete the testing. - Rejected: Hiring a vendor might take time, and it could introduce additional complexity, especially if the vendor needs to be onboarded or has their own set of approval processes. Additionally, it may not be possible to complete the remaining 20% of testing within the 2-week timeframe required to meet the new policy deadline. This option is more appropriate when the existing team cannot meet the timeline, but it is not the most efficient solution in this case. B) Stop testing immediately and escalate the issue to senior management for a decision. - Rejected: Stopping testing immediately could cause unnecessary delays. Escalating the issue to senior management should be reserved for when there is a critical blockage that cannot be resolved at the project level. Since the team has already completed 80% of the testing and only needs 4 weeks to finish, stopping work without a clear reason might unnecessarily hinder the project's progress and waste resources already invested. C) Allow testing to continue for the complete duration as the policy may not apply to ongoing projects. - Rejected: Assuming that the policy will not apply to the current project could result in legal or regulatory risks, especially if the policy changes and requires compliance. It is not advisable to continue testing without considering the po...

Author: Sophia · Last updated May 4, 2026

A project manager is appointed to manage an infrastructure project that spans across several countries, including different time zones within a subregion. It is likely that most of the project team members will never meet, but they will have to collaborate to ensure deliver...

To ensure good collaboration between the remote project team members, the project manager must prioritize effective communication, team cohesion, and clear expectations while accommodating various time zones and the virtual nature of the work environment. Let's evaluate each option: Option A: Discuss the concerns with the project sponsor and modify the project charter to include more budget for interactions. - While it's important to address resource needs, adding budget for interactions may not be the most immediate or effective way to ensure collaboration. The project charter's main focus should be on the project's objectives, scope, and high-level strategy, and the budget might not necessarily solve issues around team interaction or virtual collaboration. This approach might be better for resolving broader resource issues, but it does not directly tackle the immediate need for facilitating collaboration. Option B: Create a social media group platform for the team to create a supportive environment. - A social media platform can foster a supportive environment, but it may not be the best tool for professional collaboration, especially when discussing technical or project-related matters. While informal platforms like social media can be useful for team bonding, they might dilute focus and professionalism, and might not provide the structure needed for effective collaboration. Option C: Set the ground rules and identify a contingency plan in the risk register. - Setting ground rules is essential, but this option primar...

Author: Isabella · Last updated May 4, 2026

A team is assembled for a new project that will be using a predictive approach through requirements gathering and an agile approach for development and testing. Not everyone on the team has experience working in agile. The schedule has started slipping due to the unc...

In this scenario, the project manager is working with a hybrid approach, blending predictive and agile methodologies. The fact that the team is struggling due to unclear agile processes suggests the need for better guidance on how to implement agile practices, as well as clearer communication and structure for the development process. Let's evaluate the options: Option A: Set up weekly status meetings to review team progress, prepared weekly status reports to track progress, and regularly escalated delays. - While weekly status meetings and reports are useful for tracking overall progress in a traditional project management approach, they are less effective in an agile environment where flexibility and daily communication are critical. Weekly reports may miss small issues that could be addressed daily, and waiting a week to escalate delays may be too late in an agile context. This approach doesn't foster the continuous, iterative feedback loop essential to agile practices. Option B: Established daily standup meetings to track and report on team progress and escalated delays to stakeholders as they occurred. - Daily standup meetings are a core agile practice, designed to facilitate daily communication and allow the team to quickly identify obstacles and challenges. This option encourages transparency, quick adjustments, and early identification of potential delays, which aligns with the agile approach. It ensures that the project manager and team are regularly aligned, allowing for more proactive problem-solving, which could have prevented the schedule slippage. However, escalations may still be necessary, though they would ideally happen after identifying recurring issues rather ...

Author: Benjamin · Last updated May 4, 2026

A project team working on a hybrid project is struggling to achieve customer satisfaction. The team states that the customer keeps changing their priorities. Meanwhile, the customer argues that ...

In this scenario, both the project team and the customer are experiencing communication challenges and misalignment regarding priorities and needs. The project manager's role is to bridge this gap and ensure a shared understanding, fostering collaboration between the team and the customer to prevent further issues. Let's evaluate each option: Option A: Meet with the customer and the project team to understand the problem. - This option involves direct engagement with both the customer and the project team to understand each side's perspective. It allows the project manager to gather insights from both parties, clarify misunderstandings, and ensure that both the team's and the customer's concerns are addressed. It encourages open communication, which is essential for resolving issues in hybrid projects where both predictive and agile elements are at play. This proactive approach helps create alignment between the customer and the team, making it the most effective course of action to resolve the communication breakdown. Option B: Hire an external organization to audit the project and deliverables. - Hiring an external organization to audit the project might help identify process flaws or performance issues, but it is not the best initial step for resolving communication and prioritization issues. An external audit may take time and resources, and it doesn't directly address the underlying communication problems between the project team and the customer. The issue seems more related to understanding and managing expectations, which can be addressed more effectively through direct communication. Option C: Ask the product owner to explain the customer needs to the project team. - ...

Author: Krishna · Last updated May 4, 2026

An agile project manager is evaluating the method that will be used to display the value of the work performed to date. Which metho...

n...

Author: Aditya · Last updated May 4, 2026

An organization is transitioning to an agile approach. At the project=E2=80=99s first sprint review, the product owner did not accept the result of the...

In this situation, the best approach is to focus on collaboration and improvement rather than escalation or conflict. Let's break down the options: A) Ask the project team to address the product owner's issues since the product owner is responsible for the scope in agile. - While the product owner is responsible for the scope and prioritization, the product owner's concerns are valid and should be addressed in a collaborative way. Simply asking the team to resolve the issues may not lead to productive discussions or improvements. The team needs to understand why the product owner is concerned and work together to resolve any misunderstandings or misalignments. B) Create a record in the issue register and escalate the issue to the project steering committee. - Escalating an issue to the steering committee during the first sprint review is premature. Agile emphasizes quick resolution through team collaboration and feedback loops. Escalation should be reserved for more serious or systemic issues that cannot be resolved within the team. This option bypasses the opportunity for the team and product owner to align and learn from the situation. C) Ask the product owner to accept the outcome sin...

Author: Aarav · Last updated May 4, 2026

A project manager receives a serious complaint from a functional manager about a team member. What s...

In this situation, the project manager should prioritize communication, understanding, and conflict resolution. Let's break down the options: A) Support the team member and provide documentation to the functional manager proving their performance. - While supporting the team member is important, simply providing documentation may come across as defensive or dismissive of the functional manager's concerns. This response may not resolve the underlying issue or help the team member improve. It also risks escalating tension between the project manager and the functional manager, potentially creating a rift in collaboration. B) Replace the team member immediately to maintain a good relationship with the functional manager. - Replacing the team member immediately may not be the best approach, especially without understanding the root cause of the complaint. This could set a precedent of reacting hastily without due process. Additionally, it could demoralize the team and potentially harm the team member's professional development. A better approach would involve understanding the situation before making any drastic decisions. C) ...

Author: Evelyn · Last updated May 4, 2026

A project involves exporting 150 packages to the customer. However, only 30 packages have been cleared by the customer for shipment. The logistics manager provided details to the customer 2 weeks ago and set up a weekly conference call to effectively communicate with ...

In this scenario, the project manager should focus on understanding the customer's lack of engagement and addressing the root cause of the issue. Let's break down the options: A) Request a change in the contract to include the shipment in the project management plan. - While modifying the contract might seem like a formal solution, it does not address the core issue: the customer's lack of communication and participation. A change in the contract is unnecessary at this point without understanding the reasons for the delay. The focus should be on improving the customer's engagement and clarifying any obstacles that might be preventing the shipment from moving forward. B) Find the root cause of the issue and discuss the customer's current engagement. - This is the most constructive approach. By finding the root cause of the issue, the project manager can identify if there are any misunderstandings, delays, or other factors preventing the customer's engagement. This will help the project manager address the issue directly, communicate more effectively, and ensure that the customer is fully aligned with the proj...

Author: Elijah · Last updated May 4, 2026

A project team is working on a product that is planned for multiple iterations. They are delivering increment...

In an iterative, incremental approach, demonstrating value should align with the principles of delivering early and often to gather feedback and adapt accordingly. Let's break down the options: A) After full development is completed. - This option contradicts the principles of iterative development. In Agile and other incremental approaches, waiting until the full development is completed to demonstrate value risks late-stage surprises, misalignment with customer expectations, and delays in receiving feedback. It's far better to demonstrate value regularly throughout the process. B) When the sponsor approves the increment. - While sponsor approval is important, relying on this alone is not ideal for demonstrating value. It places an unnecessary step before the demonstration and could cause delays in showing progress. In an Agile context, demonstrating value should be more frequent than waiting for approval, ensuring transparenc...

Author: Michael · Last updated May 4, 2026

Toward the end of a project, the project manager did not receive approval from a key stakeholder because the necessary deliverables were not fun...

In this situation, the project manager needs to address the issue of the deliverables not functioning as expected. The next step should focus on understanding whether the root cause lies in the requirements, quality standards, or stakeholder expectations. Let's evaluate the options: A) Review the stakeholder engagement plan. - While important for ensuring the right level of communication and engagement, the stakeholder engagement plan focuses more on managing relationships, communication strategies, and expectations. It won't directly help identify why the deliverables are not functioning as expected. Reviewing the engagement plan would not address the immediate issue with the product quality or performance. B) Review the requirements traceability matrix. - This is a strong option. The requirements traceability matrix (RTM) is a tool that links project requirements to their corresponding deliverables. If the deliverables are not functioning as expected, the RTM can help the project manager confirm whether all the requirements were properly captured, implemented, and tested. This review could uncover gaps in underst...

Author: IceDragon2023 · Last updated May 4, 2026

A project manager identifies a risk that has a high probability of occurring. How should the project...

When managing a risk with a high probability of occurring, the project manager needs to proactively address the situation rather than just monitor it or delay action. Let's review each option and evaluate its suitability: Option A: Assign a qualified team member to be the risk manager for the project. - Pros: Assigning a qualified risk manager can help ensure the risk is closely monitored, managed, and mitigated. A dedicated team member can focus on identifying, assessing, and addressing risks as they arise. - Cons: While assigning a risk manager is helpful, it doesn't directly address the risk itself. The risk needs a more specific action to mitigate or reduce its probability or impact. - Scenario: This option could be valuable in a broader project risk management strategy but doesn't directly solve a high-probability risk in the short term. Option B: Remove the user stories associated with that risk and avoid the impact to the project deliverables. - Pros: Removing the user stories could effectively eliminate the risk's impact by ensuring that the specific tasks related to the risk are not part of the final deliverable. - Cons: This may lead to a significant reduction in scope, which could be detrimental to the project and lead to deliverables not meeting stakeholder expectations. It might be an extreme measure unless the risk is unavoidable and essential parts of the scope are at risk. - Scenario: This would be appropriate if the risk directly compromises critical aspects of the project that cannot be mitigated through other means. Option C: Submit a change request to transfer the risk to a third party in case it becomes an issue. - Pros: Transferring the risk to a third party ...

Author: ShadowWolf101 · Last updated May 4, 2026

Due to a company merger and acquisition process, the main stakeholder of a critical project has been changed. This new stakeholder complains that they were unaware of a delay on the project of which the rest of the stakeholders were aware. All the communications about...

When a new stakeholder becomes involved in a critical project and is unaware of key updates, the project manager must address the issue to ensure transparency, communication clarity, and alignment moving forward. Let's evaluate each option: Option A: Discuss project requirements with the new stakeholder, and update the communications management plan. - Pros: This option addresses both the communication gap and the stakeholder's needs. Discussing the project requirements ensures the new stakeholder understands the project's current status and expectations. Updating the communication management plan could also help align all stakeholders' needs and ensure that future communication is more effective and tailored. - Cons: While updating the plan and discussing requirements is useful, it may not immediately address the issue of the stakeholder's lack of awareness of the current delay. However, this step would help prevent similar issues in the future. - Scenario: This approach is valuable when the new stakeholder's requirements or preferences for communication have not been fully aligned with the existing plan. Option B: Send evidence to the new stakeholder that the project's status was sent according to the schedule. - Pros: Providing evidence that communication was sent on schedule might clarify the situation and show that the information was not overlooked. - Cons: While this is factually accurate, this option might not resolve the root cause of the problem. It may create a defensive tone, making the stakeholder feel like the project manager is justifying the delay rather than addressing the communication failure. The focus should be on ensuring that the new stakeholder receives the required information moving forward. - Scenario: This could be useful if the new stakeholder is questioning the reliability of the communication process and needs proof of the status updates. However, it doesn't address the broader communication alignment issue. Option C: Sugg...

Author: Deepak · Last updated May 4, 2026

A client comes to the company asking to copy a project that was executed 2 years ago in the same city, with the expectation that the new project will have the same cost and duration. While finalizing the project management plan, the project manager realizes that th...

In this scenario, the project manager needs to understand why the new project has a significantly higher baseline cost than the original project, especially when the client expects the costs and duration to be the same. Let's evaluate each option and its suitability: Option A: Assigned the same project resources to this project. - Pros: Using the same project resources (e.g., personnel, equipment, etc.) could provide consistency and potentially lower costs if the same team has experience with the project type. - Cons: This option doesn't address why the costs are higher in the new project. The project's cost might be influenced by factors beyond just the resources, such as inflation, changes in the market, or different supplier pricing. The resources alone may not be the cause of the increased costs. - Scenario: This option could be useful in ensuring that experienced team members are available, but it doesn't tackle the underlying budget discrepancies. Option B: Determined a budget reserve for this project. - Pros: Budget reserves are typically set aside to address known or unknown risks that could affect costs. This would allow the project manager to account for any unforeseen costs or changes in scope. - Cons: While budget reserves help manage risks, they don't directly explain why the baseline costs are higher than expected. This approach doesn't address the misalignment between the current project and the previous one in terms of scope or cost drivers. - Scenario: This option is helpful for risk management, but it's not the best approach to avoid the discrepancy in baseline costs from the start. Option C: Verified applicable budget inputs related to this project. - Pros: This is a critical step. By verifying the budget input...

Author: Leah · Last updated May 4, 2026

A team needs to follow defined cybersecurity compliance that is mandatory for a customer project. What should the proj...

When managing a project that requires compliance with cybersecurity standards, the project manager must ensure that the team follows the defined compliance guidelines. Let's evaluate each option in terms of its effectiveness for monitoring compliance: Option A: Confer with team members. - Pros: Confering with team members can help the project manager gauge their understanding of the cybersecurity compliance requirements and address any issues early on. This ensures that team members are aligned with the project's needs. - Cons: While it's useful to communicate with the team, this option is more about gathering information or clarifying concerns, rather than actively monitoring and enforcing compliance. It may not be sufficient to ensure that the project adheres to all the required cybersecurity standards. - Scenario: This could be useful for checking in with the team about their understanding but would not guarantee compliance on its own. Option B: Discuss with the customer. - Pros: Discussing with the customer ensures that the project manager is clear on the customer's specific cybersecurity requirements and expectations. It can provide insights into any nuances or updates to the compliance requirements. - Cons: While useful for clarifying customer expectations, this option doesn't directly help the project manager monitor compliance. It's more about setting expectations than ensuring compliance during the project's execution. - Scenario: This is important during the initial stages of the project to confirm compliance requirements but does not help in the ongoing monitoring process. Option C: Review with security experts. - Pros: Collaborating with security experts is one of the most effect...

Author: Ahmed97 · Last updated May 4, 2026

One team member is complaining about an agreement made during the last meeting. That team member was present at the meeting and participated in the decisions regi...

In this situation, a team member is expressing dissatisfaction with an agreement made during the last meeting, despite having participated in and agreed to the decisions. The project manager needs to address this complaint effectively, ensuring that team dynamics remain strong and that future collaboration is based on mutual respect and understanding. Let's evaluate each option: Option A: Schedule a new meeting to evaluate the agreement and negotiate a new one. - Pros: This approach opens up the possibility of revisiting the decision and potentially revising it if there are valid concerns or misunderstandings. It gives the team an opportunity to reassess the situation. - Cons: This could set a precedent for revisiting every decision made during meetings when a team member has a complaint, which could lead to inefficiencies and confusion. If the agreement was already documented and clear, reopening negotiations could undermine the authority of the meeting minutes. - Scenario: This option is useful if there is a significant misunderstanding or new information that justifies revisiting the agreement. However, it may not be the best option if the team member's complaint is about a personal preference rather than a substantial issue with the decision itself. Option B: Meet with the team member and search for the root cause of their behavior. - Pros: This allows the project manager to understand why the team member is dissatisfied and gives them the chance to address any underlying concerns, which might not be directly related to the decision made in the meeting. - Cons: While understanding the root cause is important, this option doesn't immediately resolve the issue at hand. If the complaint is about something that was clearly agreed upon in the meeting, focusing solely on the root cause might detract from the need for respecting team agreements. - Scenario: This option is useful when there's a deeper interpersonal or motivational issue, but it may not address the current situation effectively, where the team member simply needs to acknowledge and respect the decision made. O...

Author: Kai99 · Last updated May 4, 2026

Just as a team reaches a mutual consensus on a preferred design, a stakeholder submits a request to add new features that enhance the company...

In this scenario, the project manager must balance the interests of the stakeholders with the project's scope, timeline, resources, and quality. Let's break down the options: A) Start the process to include the new features of the product on the next iteration. - Reasoning: This option allows for the new features to be considered in the next iteration without disrupting the current progress. It follows the standard process of evaluating changes through the project's change control process. Starting this process ensures that the team assesses the impact on scope, timeline, and resources, while also maintaining alignment with the project's objectives and goals. - When to use it: This is an ideal choice when the new features are valuable but require further assessment before implementation. The team can incorporate these changes without disrupting the current work. - Conclusion: This option is prudent as it strikes a balance between stakeholder requests and maintaining project integrity. B) Allow all requested changes and bypass the company's change control process. - Reasoning: This approach is risky because it circumvents the formal change control process, which is designed to ensure that all changes are evaluated for their impact on the project's objectives. Bypassing this process could lead to scope creep, misalignment with project goals, and issues with resource allocation, timelines, or budget. - When to use it: This might be considered if the changes are minor and urgently needed, but generally, bypassing the change control process should be avoided due to the potential negative impact on project management practices. - Conclusion: Not recommended as it could jeopardize the project's success. C) Reject all requested changes and bypass the company's...

Author: Alexander · Last updated May 4, 2026

A project sponsor asks the project team to add an enhancement to the project. How should the project...

When a project sponsor asks the project team to add an enhancement, the project manager needs to ensure that any changes are properly assessed to understand their impact on the project's scope, timeline, budget, and resources. Let's review each option: A) Accept the request because it came from the project sponsor. - Reasoning: While the project sponsor's input is important, accepting the request automatically without evaluating its impact is risky. Simply accepting the request could lead to scope creep, unexpected costs, and delays. The project manager must not blindly accept changes without a thorough analysis. - When to use it: This could be considered if the enhancement was pre-discussed and agreed upon in the project's scope, but even then, it should still be assessed for feasibility. - Conclusion: Not the best approach, as it doesn't involve the necessary evaluation of the impact of the change. B) Refuse the project sponsor's request because it is out of scope. - Reasoning: Refusing the sponsor's request without a proper evaluation is dismissive and could harm the relationship between the project team and the sponsor. It's important to first assess whether the enhancement is truly out of scope or if it can be incorporated into the project. - When to use it: This could be applicable if the enhancement is indeed out of scope and no adjustments to the project's objectives, schedule, or budget can accommodate the request. - Conclusion: This approach could be too rigid unless the enhancement is clearly outside of the project's agreed-upon scope. ...

Author: Mia · Last updated May 4, 2026

A project manager is assigned to an organizational transformation project. The company typically defines individual performance plans at the beginning of the year, and functional managers conduct feedback reviews at the end of the year. The transformation project team members are concerned that the work they are doing fo...

When managing a project, especially an organizational transformation, the project manager must address concerns from team members about how their contributions will be evaluated and aligned with their individual performance plans. Let's evaluate the options: A) Meet with the functional managers to align the expected frequency and results reporting for the team members. - Reasoning: This option is proactive and ensures alignment between the project work and performance evaluations. By collaborating with functional managers, the project manager can clarify how project work is considered within performance reviews, ensuring that team members' contributions to the transformation are accurately reflected in their performance plans. This would provide transparency and alignment across the organization. - When to use it: This is the ideal option when there is a disconnect between individual performance expectations and project work. It creates a direct line of communication between the project manager and functional managers to align goals, expectations, and feedback. - Conclusion: This is the best approach, as it ensures alignment and maintains clear communication with functional managers, benefiting the team and the project's success. B) Provide performance feedback to the team members' functional managers at the end of the year. - Reasoning: While providing feedback at the end of the year is part of the process, waiting until the end of the year may not address team members' concerns in real time. This option doesn't immediately address their concerns about alignment between the project and their performance plans. Delaying feedback may lead to dissatisfaction or a sense of disconnection between project work and individual goals. - When to use it: This could be applicable if feedback is required for formal reviews, but it doesn't proactively address the alignment issues that the team members are concerned about. - Conclusion: Not the best option for addressing immediate concerns; it's more reactive than proactive. ...

Author: NebulaEagle11 · Last updated May 4, 2026

During a meeting with project stakeholders, a stakeholder who is known for causing problems, questions the project manager=E2=80=99s authority to implement new p...

In this situation, the project manager is dealing with a stakeholder who questions their authority to implement changes, which can cause tension and disrupt the project's progress. The project manager needs to respond in a way that maintains authority and clarifies the process while addressing the stakeholder's concerns professionally. Let's analyze the options: A) Refer to the change management plan and review the documented process changes. - Reasoning: Referring to the change management plan would provide a formal framework for how changes are handled within the project. However, in this specific situation, the stakeholder is questioning the project manager's authority rather than challenging specific changes. While reviewing the change management plan is useful for resolving disputes about specific changes, it does not directly address the stakeholder's challenge to the project manager's authority. - When to use it: This could be relevant when a stakeholder disputes specific changes, but it does not directly address concerns about authority or decision-making. - Conclusion: Not the best approach, as it doesn't directly address the underlying issue of authority. B) Meet with the stakeholder individually. - Reasoning: Meeting individually with the stakeholder can be an effective way to resolve conflicts, particularly if the stakeholder has a history of causing problems. A private conversation can help the project manager understand the root cause of the stakeholder's concerns and work toward a resolution. However, the issue of authority needs to be addressed publicly, especially if the stakeholder's challenge is impacting team dynamics or stakeholder relations. While private meetings can be useful, the project manager must also assert authority in front of the group to maintain leadership credibility. - When to use it: This approach can be used to understand the stakeholder's concerns in more detail, but it should be supplemented by a public clarification of authority in the meeting. - Conclusion: Not the most effective choice ...

Author: Olivia Johnson · Last updated May 4, 2026

A project manager working in a matrix organization manages an internal software development project that is intended to reduce conflicts in the company's internal tracking system. Developers placed the software application in production, and it is currently achievin...

In this scenario, the project manager is working in a matrix organization and has a project that has delivered a software application. However, the full benefits are not yet realized, and the project manager needs to decide the best course of action to ensure continued success and benefit realization. Let's examine the options: A) Continue to manage the project until all project benefits are realized. - Reasoning: This approach is reactive and does not acknowledge the fact that the project may already have transitioned to the operational phase where benefits are tracked over time. The project manager's role generally ends once the project is completed and transitioned. Continuing to manage the project indefinitely could lead to confusion over the distinction between project and operational responsibilities. - When to use it: This could be relevant if there were substantial ongoing project work to complete, but in this case, the project has already been deployed, and it's about realizing benefits, not ongoing project management. - Conclusion: Not the best option, as it can blur the lines between project and operational activities and prolong the project unnecessarily. B) Coordinate with the project's functional leads to validate its readiness for transition. - Reasoning: This option makes sense, as it emphasizes confirming that the project has been successfully transitioned to the operations team. The software is in production, and the next step is to ensure the operational teams are ready to take over responsibility for ongoing monitoring, support, and benefit realization. Coordination with functional leads will help validate that the system is stable and that operational processes are in place to monitor and track benefits over time. - When to use it: This is the appropriate course of action when the project is near completion but benefits are to be realized over a longer period. It ensures that the project's transition to operations is smooth and that everyone involved understands their roles in monitoring and reporting outcomes. - Conclusion: This is the most suitable choice...

Author: Emma · Last updated May 4, 2026

A bridge construction project has been paused due to a political change in the local government. After almost 5 years, the new government would like to resume the project, ...

When resuming a bridge construction project after a prolonged pause due to a political change, the project manager must first understand the project's current status and the expectations of all involved parties. Let's break down the options: A) Prepare an estimate of the time and cost to complete this project: This is an important step, but it should not be the first action. Preparing a time and cost estimate requires understanding the scope and expectations, which might have changed since the project was paused. This can only be accurately done after reviewing the project's current context, including any political, financial, or stakeholder changes. B) Study the project's lessons learned to understand why it was paused: While studying lessons learned from the past can be insightful, it's more of a secondary action. The primary concern should be to understand the project's current status and future direction rather than focusing solely on past reasons for the pause. This option is useful for long-term improvement and risk management but doesn't directly inform the immediate next steps for resumption. C) Meet the new stakeholders and understand their expectations: This is a critical action. The new government and other key stakeholders may have different prior...

Author: GlowingTiger · Last updated May 4, 2026

The stakeholders in an agile project are upset because some of the final products do not meet their expectations. When the project manager asks the team about the stakeholders' expectations, the team only mentions the project's objective.In addition to reminding the team about the importanc...

When dealing with a situation where stakeholders are upset because the product doesn't meet their expectations, it's essential to understand why this gap occurred. The project manager needs to bridge the gap between the team's understanding and the stakeholders' expectations. Let's analyze each option: A) Motivate the team to create and use an agile project charter: The agile project charter is a useful tool for setting the project's initial direction and defining high-level goals, but it's not the immediate solution to the issue at hand. The main issue here is the team's misunderstanding or lack of awareness of the stakeholders' expectations, and while the charter might help clarify scope and objectives, it won't directly improve the team's understanding of those expectations. A project charter is useful at the start of the project, but in this case, the problem has already emerged after execution. B) Encourage the team to use an information radiator to analyze expectations: An information radiator, such as a visible board with project information, can indeed improve communication and transparency. However, using it to "analyze expectations" might be a bit indirect. While it helps make key metrics and progress visible, it doesn't directly solve the problem of the team misinterpreting or not being fully aware of stakeholder expectations. The problem seems more about communication with stakeholders rather than the team's visibility into the project's status. C) Teach the team how to use the user persona technique: User personas he...

Author: Evelyn · Last updated May 4, 2026

During the execution phase of a project, a new project manager is assigned to replace the previous project manager. As the project manager starts managing the project, they discover that team performance is significantly decreasing, which is impacting the project=E2=80=99s key performance indicators (KPIs). This...

When a new project manager discovers a drop in team performance that is negatively affecting key performance indicators (KPIs), the primary concern should be to understand the underlying cause of the issue before jumping into any solutions. Let's assess each option: A) Review the resource management plan and organizational assets: While reviewing the resource management plan and organizational assets can provide valuable context on resource allocation and availability, it doesn't directly address the immediate issue at hand, which is declining team performance. This step is typically more relevant if the performance decline is due to resource shortages or misallocation. It's an important long-term measure, but it's not the first step when trying to diagnose a sudden drop in team performance. B) Estimate the baseline impacts and submit a change request: Estimating baseline impacts and submitting a change request might be necessary later if the project scope or timelines need to be adjusted. However, this is a reactive measure. The first action should be to identify the reasons for the team's performance issues before deciding if a change request is required. If the performance decline is due to miscommunication, unclear goals, or team dynamics, jumping straight into change requests could be premature. C) Implement compression te...

Author: Ryan · Last updated May 4, 2026

A project manager is facilitating a project steering committee meeting where the prioritization of work items in the backlog is being discussed. The engineering executive wants to prioritize features based on level of effort, completing the smallest items first. The quality executive wants to complete the most complex tasks first to have adequate time to ensure a quality product is delivered. ...

When dealing with conflicting priorities for work items in the backlog from different stakeholders (engineering, quality, and compliance), the project manager must make a decision that balances these competing interests while aligning with the project's overall goals. Let's examine each option: A) Ensure that the project value is within the quality guidelines by prioritizing and completing intricate tasks earlier in the project: While ensuring quality is important, prioritizing complex tasks early in the project can lead to delays and inefficiencies, especially if simpler tasks are skipped. Focusing on intricate tasks without addressing smaller, potentially higher-value tasks could delay the delivery of business value and miss out on opportunities to show incremental progress. This approach is more suitable when quality must be ensured upfront in specialized projects, but it's not the best in this case where multiple factors must be balanced. B) Complete tasks associated with regulatory components as the team cannot deliver business value that does not adhere to compliance regulations: Compliance is a critical factor in many projects, especially when dealing with regulatory constraints. However, prioritizing regulatory tasks first could cause delays in delivering business value, as it may not always align with other objectives like customer needs or immediate business outcomes. While regulatory components are essential, this approach could hinder progress on more urgent or impactful work. It works best when compliance directly impacts the delivery and the project cannot proceed without meeting these requirements, but it is not the best solution for balancing stakehold...

Author: Mia · Last updated May 4, 2026

One of the team members is consistently absent in team meetings, but always completes their assigned tasks on time. Other team members think this memb...

In this situation, the project manager needs to address the team member's absence from meetings while maintaining positive team dynamics and productivity. Let's evaluate each option: A) Review and update the project ground rules to make meeting attendance mandatory: While establishing clear ground rules for team meetings is important, making attendance mandatory without first understanding the reasons for the team member's absence could lead to unnecessary tension. It's essential to address the root cause of the absenteeism before imposing strict rules, especially since the team member is still completing their tasks on time. This approach could be seen as too rigid and punitive without understanding the context. B) Assign this member to facilitate the next meeting to ensure project team collaboration: Assigning the absent team member to facilitate the next meeting might seem like a good way to increase engagement, but it could backfire if the member has been absent due to a lack of interest, time, or other reasons. It could also create unnecessary pressure or discomfort if they don't feel ready to take on such a responsibility. This approach assumes that facilitating the meeting will solve the problem without addressing the underlying reasons for absenteeism. C) Understand the reason for the team member's absence and encourage them to attend future meetings: This is the most balance...

Author: Julian · Last updated May 4, 2026

A project manager is working on a product development project. When the product is delivered, there are major issues that require rework and delay new feature development.W...

To resolve the quality issues and prevent further delays, the project manager should focus on ensuring that the quality issues are addressed in a structured and thorough manner. Let's evaluate each option in detail: A) Discuss adding business scenario tests with the customer: - This option focuses on validating the product from the customer's business perspective. However, this might be too reactive at this stage, as it involves waiting for the customer's input and may not directly address the root cause of the quality issues. While customer feedback is important, it may delay the solution without directly resolving the current quality issues. B) Discuss adding additional test cases with the product owner: - This is a good option because discussing additional test cases with the product owner ensures that the product's functionality is thoroughly tested. However, this might not immediately resolve the quality issues that have already been identified. Adding more tests after defects have been found can be useful, but the current focus should be on resolving the issues and preventing them from occurring in the first place. C) Add more test scenarios based on the issues found: - This is a strong option because it directly addresses the specific quality problems identified. By adding test scenarios based on the issues that were found, the team can focus on mitigating those issues through targeted testing. This approach helps identify and prevent simila...

Author: MysticJaguar44 · Last updated May 4, 2026

A project sponsor asks the project manager to explore a hybrid approach for a new project. The product manager for this project has already prepared a detailed specification for the produc...

When exploring a hybrid approach for a new project, the project manager needs to align the project's structure with both the stable and evolving aspects of the product, while also considering how best to deliver value incrementally. Let's break down the options: A) Recommend to the project sponsor that a predictive approach is appropriate for the project due to the stable product requirements: - This option focuses on a predictive (waterfall) approach, which might be suitable for a project with well-defined and stable requirements. However, since the sponsor asked for a hybrid approach, recommending a purely predictive method would not align with the directive. A hybrid approach typically incorporates both predictive and agile elements, allowing flexibility where necessary. This option overlooks the need for adaptability in a hybrid framework. B) Explore with the product manager to determine if there are viable opportunities to deliver value incrementally and increase business value: - This option aligns well with the concept of a hybrid approach. The product manager's detailed specification could serve as a foundation, but there could still be opportunities to deliver parts of the product incrementally, allowing flexibility, faster feedback, and greater alignment with business value. Exploring opportunities for incremental delivery fits with the hybrid model of combining both predictive and agile methods. This option allows for a more balanced approach to deliver value, adjusting where needed. C) Ask the product manager whether they are prepared to act as product owner for the project in order to participate in iterative planning and reviews: - While this option is valid for agile frameworks like Scrum, it might not necessarily be needed in a hybrid approach. In a hybrid scenario, the product manager may already have a strong role in guiding the project, and it m...

Author: Rohan · Last updated May 4, 2026

A global company is executing a strategic project to upgrade a legacy enterprise system. The company uses a hybrid approach to project management and has just completed the first sprint. A team member provided ideas to improve ...

The next step for the project manager should focus on incorporating the feedback from the sprint retrospective and ensuring that improvements to the testing process are implemented effectively for the next sprint. Let's break down each option: A) Document the lessons learned and implement improvements in the next sprint: - This is the most appropriate next step. The retrospective is designed to identify lessons learned and areas for improvement. Documenting the lessons and planning for implementation in the next sprint ensures that the feedback is addressed in a timely and actionable manner. Since the team has provided ideas to improve the testing process, documenting and implementing them is a key step toward continuous improvement. B) Request that all team members think of ideas to improve processes: - While encouraging team members to think of improvements is valuable, this step has already been done during the sprint retrospective. Asking for more ideas without implementing the existing feedback could lead to an overwhelming amount of suggestions without actionable outcomes. At this stage, the priority should be to implement the current improvements rather than generate new ideas. C) Facilitate a daily standup with the team to track the implementation of changes: - Daily standups are typically used for tracking progress on ongoing tasks and resolving immediate issues. While this option might seem beneficial for tracking improvements, the retrospective feedback and the resulting improvements are better suited to...

Author: RadiantPhoenixX · Last updated May 4, 2026

DRAG DROP -A project manager has been assigned to a software development project that will undergo several iterations until the customer is satisfied. Match the tool or technique on the left that the project mana...

n...

Author: VenomousSerpent42 · Last updated May 4, 2026

A project manager brings in a new team member from an agile environment to work in a predictive environment. The project manager expects to leverage the new team member's agile experience with the existing tea...

To integrate the new team member from an agile environment into a predictive environment effectively, the project manager needs to ensure clarity of roles and expectations, provide necessary training, and foster collaboration between the new team member and the existing team. Let's evaluate each option: A) Set expectations with the new team member and explain what is needed: - This is a crucial step in helping the new team member understand the work culture, the environment, and the specific expectations within the predictive framework. The new team member's agile background could be valuable, but they need to understand how to operate within the predictive context. Setting clear expectations would ensure that they can effectively contribute to the team while adjusting to the new environment. This is a proactive and necessary action. B) Acknowledge that hiring this new employee is a risk to the existing team: - While it's important to be aware of potential challenges, this approach takes a negative perspective. Acknowledging "risk" before the integration even begins might foster unnecessary concern among the existing team members and create tension. Instead, the project manager should focus on how to leverage the new team member's skills and foster collaboration, rather than framing the situation as a risk. C) Train the new team member in the predictive project management approach: - This is a practical and necessary action if the new team member is unfamiliar with the predictive environment. However, training should be part of a...

Author: Layla · Last updated May 4, 2026

Upon analyzing the report requirements to create a functional design, the project team finds that the information source is not correct a...

In this situation, the project team has identified that the information source is incorrect and needs adjustment. The project manager must take appropriate action to address this issue efficiently and ensure the project continues to move forward. Here's an analysis of each option: A) Initiate a change request procedure. - Reasoning: A change request procedure is typically used when there is a need to formally modify the scope, schedule, cost, or other key aspects of the project. While adjusting incorrect information might involve changes later on, it is too early to initiate this procedure if the issue is more about clarifying or validating the source of information. - Rejection: The issue here is about correcting or verifying information, not necessarily a formal change to the project scope. This option is premature and might cause unnecessary overhead. B) Build a prototype to verify the information. - Reasoning: Building a prototype could help clarify the information if there are uncertainties about the solution or product, but it is not the first step in validating information sources. The team should first ensure the data or information they are working with is accurate and appropriate, which might not require prototyping. - Rejection: This option is more relevant in situations where the project is more tangible and iterative (like product design or software development) and the focus is on confirming usability or functionality. In this case, it might be too complex or unnecessary at the stage of verif...

Author: Grace · Last updated May 4, 2026

The project sponsor requested technical specifications for a project-related component. The project sponsor does not have the authorization to see the specifications, but insist...

In this scenario, the project sponsor has requested access to technical specifications that they are not authorized to see. The project manager must address this issue while balancing project confidentiality and the sponsor's requests. Here's an analysis of each option: A) Provide the specifications to the project sponsor with some information removed. - Reasoning: Providing partial specifications, even with redacted or removed information, could lead to misunderstandings or potential leaks of sensitive data. This could violate confidentiality agreements or create issues around unauthorized access. - Rejection: This option could jeopardize project security and doesn't address the core issue, which is the sponsor's lack of authorization to see these specifications in the first place. B) Update the issue log to make the project team aware and to develop a strategy. - Reasoning: While logging the issue may be useful for tracking and documentation, the situation requires an immediate response to the sponsor's request. It does not provide a direct solution to the problem, nor does it address the need for immediate discussion with the sponsor. - Rejection: This option is more suitable for tracking ongoing issues rather than responding to urgent requests from the sponsor. It's not the best choice for addressing the current situation directly. C) Create a stakeholder engagement plan to help the team formulate a response. - Reasoning: While stakeholder engagement planning is crucial in managing relationships and ensu...

Author: Nia · Last updated May 4, 2026

A key stakeholder who is frustrated by the lack of transparency of IT projects declines an invitation to participate in the new project meetings. What should t...

In this situation, a key stakeholder is frustrated by the lack of transparency in IT projects and has declined the invitation to participate in project meetings. The agile project manager must find a way to re-engage this stakeholder, rebuild trust, and address their concerns. Here's an analysis of each option: A) Introduce the stakeholder to the project team and invite them to the next iteration review meeting with the IT team. - Reasoning: While involving the stakeholder in iteration reviews can be a useful way to demonstrate transparency and showcase progress, this option may not be the most effective approach if the stakeholder is already frustrated with the lack of transparency. The frustration might be tied to a broader communication issue, and simply inviting them to a meeting may not be sufficient to rebuild trust. - Rejection: This approach could be seen as too transactional and may not address the root cause of the stakeholder's frustration. The stakeholder might not feel engaged or understood just by being added to a meeting. B) Use stakeholder mapping to document the level of influence and interest for the next iteration planning meeting. - Reasoning: Stakeholder mapping is a valuable tool for understanding the position of various stakeholders in relation to the project, but it is more of an analytical step rather than a direct action to re-engage the frustrated stakeholder. This option is more about assessing the situation than actively addressing the current problem. - Rejection: While useful for strategic planning, stakeholder mapping does not directly engage the frustrated stakeholder or help to resolve the issue of their disengagement. C) Present the project management pl...

Author: Elizabeth · Last updated May 4, 2026

A project manager is assigned to lead a hybrid innovation project. During a meeting with the sponsor and major stakeholders, the project manager realizes that the requi...

In this scenario, the project manager is faced with unclear requirements during a meeting with the sponsor and major stakeholders. The project manager must take action to address the ambiguity and ensure the project can move forward effectively. Here's an analysis of each option: A) Request that the sponsor meet with the product owner to address the issue. - Reasoning: While collaboration between the sponsor and product owner is important, the responsibility for clarifying requirements should not solely fall on the sponsor and product owner. The project manager plays a key role in facilitating communication and ensuring clarity at the outset of the project. Just passing the responsibility off to the product owner or sponsor without addressing the root cause might not lead to a timely resolution. - Rejection: This option assumes that the sponsor and product owner can solve the problem independently. However, it's the project manager's responsibility to facilitate discussions and bring stakeholders together to clarify the requirements effectively. B) Help the sponsor and major stakeholders to craft the product vision. - Reasoning: Crafting a clear product vision is essential for setting a shared understanding of the project's goals and requirements. This is a proactive and collaborative approach where the project manager can work closely with the sponsor and stakeholders to clarify objectives and ensure alignment on the project's direction. - Selection: This option directly addresses the unclear requirements by helping the sponsor and stakeholders develop a clearer vision. It allows the project manager to lead the discussion, clarify goals, and align all parties on the project's objectives and scope. This is especially ...

Author: FlamePhoenix2025 · Last updated May 4, 2026

During the last two iterations of a project, one of the team members had low performance. The project manager conducted two feedback sessions with the team member and escalated the issue to the resource manager and...

In this scenario, the project manager has already conducted feedback sessions with the underperforming team member, escalated the issue to both the resource manager and project sponsor, but has seen no improvement in performance. Now, the project manager needs to decide on the best course of action. Let's review the options: A) Request a new resource to execute the activities. - Reasoning: Requesting a new resource is a significant step, as it may disrupt the team's dynamic, cause delays, and create additional overhead in terms of onboarding and ramping up the new team member. Before taking such a drastic measure, it's important to ensure that all avenues for addressing the issue with the current team member have been explored. - Rejection: This option may be premature, especially if the team member could still improve with the right support. It's also not the most constructive way to handle performance issues, as it avoids addressing the root cause. B) Review this obstacle during the daily standup meeting. - Reasoning: The daily standup is typically a forum for discussing ongoing work, blockers, and coordination between team members, not for addressing ongoing performance issues with individual members. While the project manager can use standups to bring up challenges, the daily meeting isn't the appropriate setting for addressing persistent performance problems. - Rejection: While it's important to keep the team aware of potential obstacles, discussing a low-performance issue during the standup is not ideal because it might embarrass the team member, and the daily meeting isn't intended for such in-depth discussions. C) Escalate the situation again to the project sponsor. - Rea...

Author: VioletCheetah55 · Last updated May 4, 2026

A project manager was recently assigned to a project that is in the execution phase and is experiencing roadblocks. During a review of the processes and procedures, the project manager notices similarities to a previous project that experienced similar roadblocks. The project manager reviews the task schedule and finds that certain tasks are well behind expect...

In this scenario, the project manager is observing roadblocks that are similar to those encountered in a previous project. The task schedule is behind expectations, and the team is following the processes as directed, which suggests that the processes themselves may be a contributing factor to the delays rather than issues related to resources or unexpected changes. Let's analyze the options in detail: - A) Review and amend the processes to ensure only value-adding activities are present. This is a strong option because the issue seems to stem from the processes that are being followed. If the processes are causing delays without adding significant value, then revising them to streamline and focus on value-adding activities can help. This approach ensures that unnecessary steps are eliminated, improving efficiency and potentially resolving the roadblocks. - B) Review the resources allocated to the project and change accordingly. While resource allocation could be a potential factor in delays, the problem as described points more to the processes rather than the resources themselves. The team is following the processes, so the root cause appears to be inefficiency in the execution of those processes rather than a lack of resources. Changing resources without addressing the processes may not effectively resolve ...

Author: Aria · Last updated May 4, 2026

A new project manager is initiating a project and realizes the team members are all very rigid, unwilling to change, and constantly state that they have been running projects successfully for years. The project manager realizes that the p...

In this scenario, the project manager faces a team that is resistant to adopting an agile approach, which is essential for the success of the project. The team members are experienced but rigid, sticking to their traditional ways of running projects. The project manager needs to address this issue to ensure the project succeeds in the evolving environment that requires agility. Let's analyze the options: - A) Realize the team is in the forming stage and that, as the team moves toward the performing stage, it will become agile. While it is true that teams develop over time, this option assumes that the team will naturally become agile on its own as they mature, which may not be the case. Since the team is specifically resistant to change and following a traditional approach, it's unlikely that they will automatically become agile just because they progress to the performing stage. This assumption does not actively address the issue or the risk to the project. - B) Schedule a meeting with the project sponsor to request that management support the team's adoption of agile. While gaining support from the project sponsor and management is critical, this option may not immediately address the core issue. The resistance is at the team level, and without first engaging the team, simply escalating the issue to management might not result in the necessary behavioral change. It's important to first involve the team in the process and help them understand the benefits of agile. ...

Author: Aarav · Last updated May 4, 2026

The customer wants to show their stakeholders a tangible outcome faster. This requires advancing a milestone.Which two ...

In this scenario, the customer wants to advance a milestone to provide a tangible outcome sooner. The project manager needs to balance the customer's expectations with the reality of project constraints, such as scope, resources, and timelines. Let's review the options: - A) Review the customer's priorities regarding the desired requirements for the milestones. This is a strong option because understanding the customer's priorities is crucial for determining which aspects of the project are most important to them. By reviewing the priorities, the project manager can identify which elements of the milestone are most critical and possibly find ways to focus on delivering high-priority requirements first, which might allow advancing the milestone without compromising quality. - B) Convince the customer to keep the requirements as is and not move the milestone. This option would reject the customer's request and could create friction. The customer is clearly seeking a tangible outcome sooner, so denying this request without exploring alternatives could damage the relationship or leave the customer dissatisfied. It may also prevent the project from adapting to evolving needs, which is not ideal. - C) Discuss which requirements can be delivered faster with the project team. This is also a strong option because collaborating with the project team to identify which deliverables can be expedited is essential for meeting the customer's request. The project manager and team can assess whether some requirements can be re-prioritized, streamlined, or delivered more q...

Author: Leah Davis · Last updated May 4, 2026

An agile team recently started working on a project for a financial institution. The project sponsor is concerned that an agile approach will not provide enough support for the organization's compliance standa...

In this scenario, the project manager is addressing concerns from the project sponsor regarding the agility of the process and its potential impact on compliance with the organization's standards. It's important to ensure that the agile methodology accommodates the compliance needs of the financial institution without compromising the benefits of flexibility and speed that agile offers. Let's analyze the options: - A) Ensure that the peer review process also covers compliance requirements, creating a second layer of security for the project. This is a helpful action, but it may not be sufficient on its own to fully address compliance concerns. While a peer review can certainly catch issues, it might not be comprehensive enough to ensure that all compliance requirements are met, especially in a regulated industry like financial services. Compliance should be embedded into the team's processes and understood from the outset, rather than as an afterthought during reviews. - B) Meet with the compliance team and make sure that their requirements are covered in the definition of done (DoD) for each story. This is a very strong option. The definition of done (DoD) is a key part of agile methodologies, and ensuring that compliance requirements are explicitly included in the DoD for each user story ensures that compliance is built into the work from the very beginning. This approach integrates compliance seamlessly into the agile process and provides clear, measurable criteria for meeting those standards. - C) Liaison with the compliance group, making them responsible f...

Author: ShadowWolf101 · Last updated May 4, 2026

The project manager is reviewing the program risks and issues with key stakeholders. One of the stakeholders wants to understand when the risk may potentially become an i...

In this scenario, the stakeholder wants to understand when a risk might potentially become an issue. The project manager needs to provide an artifact that not only identifies risks but also outlines how and when they might escalate into actual issues. Let's break down the options: - A) Project management plan The project management plan is a broad document that includes various plans related to scope, schedule, and resources, among others. While it could mention risk management in passing, it is not the most detailed artifact specifically focused on risks or issues, making it less suitable for answering the stakeholder's specific question about when a risk might become an issue. - B) Issue log The issue log tracks issues that have already occurred and are being managed. It does not deal with potential risks and does not provide information on when a risk could escalate into an issue. This is not the appropriate document for understanding the timing of risk escalation. - C) Risk management plan The risk ...

Author: ElectricLionX · Last updated May 4, 2026

A company that is introducing a new product into the market by the end of the year requires a storage and distribution facility to be built. During the monthly stakeholder meeting, it is discovered that the locat...

In this scenario, the project manager needs to assess the impact of the discovered issue that the location for the storage and distribution facility is a government-owned area. This discovery could bring about potential legal, regulatory, and logistical challenges that need to be addressed as part of the project. Let's evaluate the options: A) Update the risk register: This option would involve adding the discovery of a government-owned location to the risk register. The project manager may identify risks such as delays due to permit processes, legal hurdles, or issues with zoning or land use. However, this is only a preventive measure and doesn't resolve the immediate issue or lead to any concrete action toward finding a solution. It's more of a tracking action. B) Update the issue log: An issue log is used to track problems that need to be addressed in real time, but the discovery of the government-owned area might not yet be an issue that has materialized. It's still a potential barrier that requires further investigation. If the site is nonviable, then it becomes an issue, but updating the issue log alone might be premature. C) Identify an alternative site: This option is the most proactive. If ...

Author: Michael · Last updated May 4, 2026

A project manager has been assigned to a new digital product line, which the company hopes will boost their revenue. The product is complex and requires customer feedback to continually refine the product. The project is being handled by...

In this scenario, the project manager is overseeing a complex digital product line within an agile environment, where customer feedback is critical to the continuous refinement of the product. The goal is to ensure that value is delivered quickly, especially since the product is aimed at boosting revenue. Let's evaluate the options: A) Ask the project sponsor to provide additional resources to fast track the project: While adding resources can sometimes help, in an agile environment, more resources don't always equate to faster delivery, especially if the team is already cross-functional and well-balanced. Agile frameworks emphasize collaboration, and simply adding more people can lead to coordination overhead and inefficiencies. The focus should be on optimizing current processes rather than just increasing the workforce. B) Plan the project to deliver value incrementally with regular releases: This is the core principle of agile methodology. Delivering value incrementally with regular releases ensures that customer feedback is continuously integrated and that parts of the product can go to market quickly. By adopting this approach, the project manager ensures that the team is focused on delivering tangible value early and often, allowing for continuous refinement based on user feedback. This is the most effective way to ensure value is del...

Author: Aditya · Last updated May 4, 2026

A project is designed to provide local community members with health facilities that will support improved sanitation practices. What should the project manager ...

In a project focused on providing health facilities for a local community, communication with the community members is key to ensuring they are informed and engaged throughout the process. The project manager must select the most effective communication approach to keep community members up to date on the project's progress. Let's evaluate the options: A) Share the annual reports virtually and in the local newspapers: While sharing reports through newspapers or virtually might be helpful for informing the public in general, it may not be the most immediate or personal method for keeping community members directly involved and informed about the project's progress. Annual reports are often too infrequent and formal, and may not convey timely or detailed updates in a manner that actively engages the community. B) Share project updates when requested by the stakeholders: Waiting for stakeholders to request updates could result in delays in communication. Proactive communication is typically more effective than reactive, especially in projects that directly affect the community. By waiting for requests, the project manager risks missing opportunities to engage stakeholders in a timely manner. C) Share project ...

Author: Leah Davis · Last updated May 4, 2026

A project manager is assigned to a major system integration project that is currently in the execution phase. The project relies heavily on the presence and availability of certain products and services, which are provided at various periods throughout the project phases ...

In this scenario, the project manager is working on a system integration project that heavily relies on third-party vendors to supply products and services at various points during the execution phase. The project's success depends on the timely delivery and availability of these third-party products and services. Let's evaluate the options: A) Oversee the selection process for the vendor to procure the needed products and services: While overseeing the vendor selection process might be important in earlier phases of the project, the project is already in the execution phase. At this point, the vendors should already be selected, and the focus should be on managing their performance and ensuring they deliver as agreed. This option is not the best choice since it pertains more to the planning and procurement phase rather than the execution phase. B) Ask the procurement department to select the vendor using established processes: The procurement department may have established processes for vendor selection, but this approach would be appropriate only if the vendors haven't been selected yet, which contradicts the scenario that the project is already in the execution phase. The project manager's role at this point should be more focused on managing and ensuring vendor performance rather than selecting them. C) Activate the mitigation plan for the procurement risks: Mitigation plans for procuremen...

Author: Victoria · Last updated May 4, 2026

What Our Friends Say

What Our Friends Say

PMI Practice Questions, Discussions & Exam Topics by our Authors

A newly assigned project manager is reviewing the project management plan and realizes that the project is running behind schedule. What ...

A key business stakeholder sent emails to the developers with complaints based on the last few sprints. The developers forwarded the emails to the project manager but have not yet responde...

A project manager is made aware that there are defects in the parts provided by a supplier, which are causing delays in the testing phase. The supplier claims that all parts have been delivered as per the contract. If the defects are not fixed ...

A project manager finds that there are knowledge gaps in the project team relating to the core competencies required to deliver the desired results. W...

DRAG DROP -A project manager is leading a project in which key performance indicators (KPIs) are measured through earned value management (EVM).Match ea...

A team is testing a product on multiple radio frequencies. The project manager is informed that a new government policy, expected in 2 weeks, will mandate companies to obtain approval and licensing for frequency testing. The team has completed 80% of the testing and needs 4 weeks to c...

A project manager is appointed to manage an infrastructure project that spans across several countries, including different time zones within a subregion. It is likely that most of the project team members will never meet, but they will have to collaborate to ensure deliver...

A team is assembled for a new project that will be using a predictive approach through requirements gathering and an agile approach for development and testing. Not everyone on the team has experience working in agile. The schedule has started slipping due to the unc...

A project team working on a hybrid project is struggling to achieve customer satisfaction. The team states that the customer keeps changing their priorities. Meanwhile, the customer argues that ...

An agile project manager is evaluating the method that will be used to display the value of the work performed to date. Which metho...

An organization is transitioning to an agile approach. At the project=E2=80=99s first sprint review, the product owner did not accept the result of the...

A project manager receives a serious complaint from a functional manager about a team member. What s...

A project involves exporting 150 packages to the customer. However, only 30 packages have been cleared by the customer for shipment. The logistics manager provided details to the customer 2 weeks ago and set up a weekly conference call to effectively communicate with ...

A project team is working on a product that is planned for multiple iterations. They are delivering increment...

Toward the end of a project, the project manager did not receive approval from a key stakeholder because the necessary deliverables were not fun...

A project manager identifies a risk that has a high probability of occurring. How should the project...

Due to a company merger and acquisition process, the main stakeholder of a critical project has been changed. This new stakeholder complains that they were unaware of a delay on the project of which the rest of the stakeholders were aware. All the communications about...

A client comes to the company asking to copy a project that was executed 2 years ago in the same city, with the expectation that the new project will have the same cost and duration. While finalizing the project management plan, the project manager realizes that th...

A team needs to follow defined cybersecurity compliance that is mandatory for a customer project. What should the proj...

One team member is complaining about an agreement made during the last meeting. That team member was present at the meeting and participated in the decisions regi...

Just as a team reaches a mutual consensus on a preferred design, a stakeholder submits a request to add new features that enhance the company...

A project sponsor asks the project team to add an enhancement to the project. How should the project...

During a meeting with project stakeholders, a stakeholder who is known for causing problems, questions the project manager=E2=80=99s authority to implement new p...

A project manager working in a matrix organization manages an internal software development project that is intended to reduce conflicts in the company's internal tracking system. Developers placed the software application in production, and it is currently achievin...

A bridge construction project has been paused due to a political change in the local government. After almost 5 years, the new government would like to resume the project, ...

The stakeholders in an agile project are upset because some of the final products do not meet their expectations. When the project manager asks the team about the stakeholders' expectations, the team only mentions the project's objective.In addition to reminding the team about the importanc...

One of the team members is consistently absent in team meetings, but always completes their assigned tasks on time. Other team members think this memb...

A project manager is working on a product development project. When the product is delivered, there are major issues that require rework and delay new feature development.W...

A project sponsor asks the project manager to explore a hybrid approach for a new project. The product manager for this project has already prepared a detailed specification for the produc...

A global company is executing a strategic project to upgrade a legacy enterprise system. The company uses a hybrid approach to project management and has just completed the first sprint. A team member provided ideas to improve ...

DRAG DROP -A project manager has been assigned to a software development project that will undergo several iterations until the customer is satisfied. Match the tool or technique on the left that the project mana...

A project manager brings in a new team member from an agile environment to work in a predictive environment. The project manager expects to leverage the new team member's agile experience with the existing tea...

Upon analyzing the report requirements to create a functional design, the project team finds that the information source is not correct a...

The project sponsor requested technical specifications for a project-related component. The project sponsor does not have the authorization to see the specifications, but insist...

A key stakeholder who is frustrated by the lack of transparency of IT projects declines an invitation to participate in the new project meetings. What should t...

A project manager is assigned to lead a hybrid innovation project. During a meeting with the sponsor and major stakeholders, the project manager realizes that the requi...

During the last two iterations of a project, one of the team members had low performance. The project manager conducted two feedback sessions with the team member and escalated the issue to the resource manager and...

A new project manager is initiating a project and realizes the team members are all very rigid, unwilling to change, and constantly state that they have been running projects successfully for years. The project manager realizes that the p...

The customer wants to show their stakeholders a tangible outcome faster. This requires advancing a milestone.Which two ...

An agile team recently started working on a project for a financial institution. The project sponsor is concerned that an agile approach will not provide enough support for the organization's compliance standa...

The project manager is reviewing the program risks and issues with key stakeholders. One of the stakeholders wants to understand when the risk may potentially become an i...

A company that is introducing a new product into the market by the end of the year requires a storage and distribution facility to be built. During the monthly stakeholder meeting, it is discovered that the locat...

A project manager has been assigned to a new digital product line, which the company hopes will boost their revenue. The product is complex and requires customer feedback to continually refine the product. The project is being handled by...

A project is designed to provide local community members with health facilities that will support improved sanitation practices. What should the project manager ...

A project manager is assigned to a major system integration project that is currently in the execution phase. The project relies heavily on the presence and availability of certain products and services, which are provided at various periods throughout the project phases ...