PMP PMI Project Management Professional (PMBOK 7th Version) Free Practice Exam Questions (2026 Updated)

In the planning phase of a project, it’s common for team members to have different views on how to approach certain tasks. In this case, where there is a disagreement on how to approach end-user training, the project manager should consider the view of each team member about the issue in order to reach consensus. This approach promotes a collaborative environment and ensures that all perspectives are considered, which can lead to a more effective and comprehensive solution. References: PMBOK® Guide – Sixth Edition, Project Management Institute, Inc., 2017, p. 314. Available at: PMI

 In Agile project management, retrospectives are conducted to reflect on the previous sprint or phase of work. The Agile principle of self-organization emphasizes that teams are best positioned to determine how to accomplish their work, which includes task allocation. The project manager should support this principle by informing the functional manager that the team is responsible for self-organizing, which includes task allocation. This approach empowers the team and supports Agile methodologies’ emphasis on team autonomy and accountability.

= While I cannot provide direct references from the Professional in Business Analysis Reference Materials, this answer aligns with the general principles found in Agile and Scrum frameworks, as described in the Scrum Guide and Agile Manifesto.

Implementing a requirements traceability matrix (RTM) is the most effective way for the project manager to ensure that each requirement is linked to business and project objectives. An RTM is a tool that maps out the relationship between requirements and project work, ensuring that predetermined project requirements are met and providing a record of any testing, issues, and completed items. This approach helps in keeping the project aligned with its objectives and facilitates the tracking of requirements throughout the project lifecycle123.

= Information on RTMs from Project-Management.com1, PMI.org2, and ProjectManager.com3. Additionally, techniques for linking business analysis plans to organizational strategy as found in the BABOK® Guide4.

In a global project using a follow-the-sun approach, it is crucial to have effective communication to ensure a smooth handover of tasks and issues between teams in different time zones. Moving working windows to increase overlap allows for real-time communication and collaboration, which can help in addressing and resolving issues more efficiently. This approach aligns with the PMBOK guide’s emphasis on effective communication management in projects1.

 The Project Management Professional (PMP) emphasizes the importance of supporting team performance by assessing team member performance, supporting team development, giving feedback, and verifying improvements. It highlights the significance of creating a cooperative and motivated team environment. Building a culture of empathy falls under these guidelines as it helps in dealing with emotions and supports team development. This approach not only aids the affected team member but also enhances the overall team’s performance by fostering a supportive and understanding work environment. References: = PMI’s “A Guide to the Project Management Body of Knowledge (PMBOK® Guide)” and “Business Analysis for Practitioners: A Practice Guide” provide insights into team dynamics and the importance of emotional intelligence in project management. These resources support the approach of building a culture of empathy to manage team performance effectively12.

Integrating a new team member into an iterative project requires a supportive approach that ensures they understand the processes and can contribute effectively. Allocating time within the iterations for mentoring allows the new member to learn the necessary skills and processes in a structured manner. This aligns with the PMBOK® Guide’s principles of project team management and development, which emphasize the importance of continuous learning and improvement within the team. Mentoring provides a practical way to facilitate this learning, helping the new member to integrate into the team’s workflow without negatively impacting the schedule1.

Mentoring - Key Competency for Program and Project Professionals - PMI1.

 To avoid the problem of inaccurate cost estimation, as indicated by a CPI of 0.65, bottom-up estimating should have been used. This method involves estimating the cost of individual tasks in detail and then aggregating them to arrive at a total project cost. It is more accurate than analogous estimating because it considers the specific details of the current project rather than relying on the cost data of past projects, which may not be directly applicable. Bottom-up estimating allows for a more granular and accurate assessment of the project’s financial requirements.

 The project manager should analyze the team members’ influence levels and schedule a training on the importance of daily standups and the time-bound feature of the meetings (Option A). This approach is based on the principle that understanding the influence levels of team members can help in effectively managing their participation in meetings1. Additionally, training on the importance of daily standups can help team members understand the value of these meetings and encourage their participation2.

Requiring all team members to attend the daily review meetings as they are requested by the project sponsor (Option B) may not be effective if the team members do not see the value in these meetings2. Informing the functional manager and replacing team members who cannot join the daily progress meetings (Option C) may not be practical or beneficial for the project2. Reviewing the influence of each team member, calling the team members with the highest influence to a meeting, and convincing them to join the daily standups (Option D) may not ensure the participation of all team members1.

In Agile projects, it is essential to involve stakeholders and keep them informed about the project’s progress. The sprint review meetings are designed for this purpose, as they provide a platform for the team to demonstrate the work completed during the sprint and gather feedback. Inviting stakeholders to these meetings every 2 weeks aligns with Agile best practices of maintaining regular feedback loops and ensuring stakeholder engagement1. This approach allows stakeholders to see firsthand the project’s progress and contribute their insights, which can be invaluable for the project’s success.

 To enhance collaboration among virtual teams, especially when one team feels isolated due to time zone differences, the project manager should consider implementing strategies that promote inclusive communication and regular engagement.

Option A, scheduling weekly progress meetings with all three teams, ensures that each team has the opportunity to be heard and to participate actively in the project’s progress. This approach fosters a sense of unity and allows for synchronous communication, where immediate feedback can be provided and all teams are updated simultaneously12.

Option C, updating the communications management plan, is crucial for addressing the current issues faced by Team A. By encouraging all teams to review the communications plan promptly and proactively, the project manager can ensure that information dissemination is timely and no team is left out of the loop. This step also allows for the identification of any gaps in the current communication strategy and the implementation of improvements to facilitate better collaboration12.

While the other options may have their merits, they are not as immediately impactful as A and C for addressing the current challenges of feeling left out and information delays experienced by Team A.

 The best course of action in this scenario is to ensure that the content of the project report is clearly understood by all stakeholders and to actively seek their feedback. This approach aligns with the principles of transparency and communication found in both the PMBOK® Guide and the Professional in Business Analysis Reference Materials. By clarifying the report’s content and engaging stakeholders in providing feedback, the project manager can address any concerns or misunderstandings regarding the project’s progress and the iterative nature of the releases. This proactive communication helps to set accurate expectations and fosters a collaborative environment where stakeholders are informed and involved in the project’s development process. References: PMBOK® Guide, Professional in Business Analysis Reference Materials12.

 In the context of PMP, when a project encounters technical impediments that could potentially delay deliverables, it is crucial to document and track these issues formally. Updating the issue log is a standard practice in project management, as it ensures that all stakeholders are aware of the impediments and the actions being taken to resolve them. This approach aligns with the principles of communication and transparency in project management, as outlined in the PMBOK® Guide and other PMP reference materials. It allows for a structured method to prioritize and address the issues, facilitating better decision-making and resource allocation to resolve the impediments1.

In the context of project management, particularly within the PMBOK® Guide’s framework, it is crucial for a project manager to address conflicts by identifying and addressing the root causes. This approach aligns with the conflict resolution techniques outlined in the PMBOK, which include problem-solving and collaboration as effective methods for resolving disputes. By engaging stakeholders to understand their perspectives and reach a consensus, the project manager can facilitate a collaborative environment that fosters mutual understanding and agreement on how to move forward.

(PMBOK® Guide - Sixth Edition, Chapter 13: Project Stakeholder Management)

 When a project manager joins a project midway and identifies issues with dependencies and communication, the first step should be to consult the communications management plan. This plan outlines how project communications will be planned, structured, implemented, and monitored for effectiveness1. It includes key points such as defining the audience, requirements, and communications schedule, which are essential for ensuring that all team members are adequately informed of impacting changes1. By consulting this plan, the project manager can address the communication issues systematically and align with the established project management practices.

The closing phase of project management is the final phase of the project lifecycle. This is the stage where all deliverables are finalized and formally transferred, and all documentation is signed off, approved, and archived1. The most important step of the project closing phase is getting formal sign-off and acceptance of the customer2. Because projects are initiated based on a business need and customer request. Therefore, if the customer does not accept the final outputs and product, a project cannot be closed2. References: 7 Steps to Nail the Project Management Closure Process, Project Closing Phase: Do You Know the 8 Steps for Closing a Project?

 When faced with a delay in a critical path activity, it is prudent for the project manager to thoroughly evaluate the proposed fallback plan, considering its impact on the project’s scope, time, cost, and quality. If the fallback plan is viable and justifies the additional cost, the project manager should proceed with submitting a change request. This process involves documenting the proposed changes, assessing the benefits and risks, and seeking approval from the project sponsor or change control board. The change request should detail the reasons for the deviation from the original plan, the expected outcomes, and the justification for the additional expenditure. This approach ensures that any alterations to the project are well-considered, transparent, and formally approved, maintaining the integrity of the project management process123.

In an Agile environment, the project manager’s role is to empower the teams and make them self-organizing12. This involves helping the teams establish their own ground rules and ensuring adherence to these rules3. It’s important to revisit these rules at regular intervals for continuous improvement2. This approach promotes collaboration, understanding, and strong leadership within the team1. It’s also crucial for the project manager to have excellent communication skills, the ability to identify and analyze potential risks, and the ability to motivate and mentor individuals and teams3. References:

https://apmg-international.com/article/what-does-agile-project-manager-do

https://businessmap.io/blog/agile-project-manager

According to the Project Management Body of Knowledge (PMBOK) guide, the project manager should ensure that the project meets the agreed acceptance criteria by performing tests and routinely tracking results as per the quality management plan. This approach allows the project manager to monitor the project’s progress and make necessary adjustments to ensure that the project meets the acceptance criteria. References: PMBOK Guide, 6th Edition, Section 8: Quality Management

The introduction of new requirements during the implementation phase can lead to scope creep, which may adversely affect the project’s cost and schedule baselines. To manage this, establishing a proper governance structure is essential. This structure would include a change control board or similar entity to evaluate the impact of new requirements and make decisions on their inclusion in the project. This ensures that all changes are assessed for their implications on the project’s objectives and resources before being approved1.

= The need for a governance structure to manage changes and its role in maintaining project baselines is supported by best practices in project management as outlined in the PMBOK® Guide2. Additionally, the Professional in Business Analysis (PMI-PBA) materials emphasize the importance of governance in change management and the role of business analysts in assessing the impact of changes34.

 Effective communication is a cornerstone of project management, particularly when dealing with changes that may affect team morale. The project manager should openly communicate the project’s impact and involve the team in the planning process. This approach not only helps in managing the change effectively but also in addressing the concerns of the team members, thereby fostering a collaborative project team environment. Engaging the team throughout the project helps in building a common understanding and ensures that everyone is aligned with the project’s objectives12. References:

Create a collaborative project team environment :: PMBOK® Guide1.

PMBOK 7 principles :: PMBOK® Guide2.

The project manager should evaluate the project’s specific needs, resources, timelines, and risk tolerance to determine the most suitable project management approach. While the PMO is implementing adaptive tools, and the functional manager prefers predictive tools, the project manager’s responsibility is to assess the situation and decide on the approach that aligns best with the project’s goals and context. This decision should be based on a thorough understanding of both adaptive and predictive methodologies and their applicability to the project at hand. The project manager should consider the unique aspects of the project, such as its complexity, stakeholder expectations, and the degree of uncertainty, to make an informed decision.

The information provided is synthesized from the general principles found within the PMI’s guide and standards for project management and business analysis, which advocate for tailoring the project management approach to the specific needs of the project123. It is also aligned with the PMI’s stance on the importance of using the right tools and techniques to support the project’s objectives45.

When faced with internal team conflicts, especially between a team lead and an experienced engineer, it is important to address the issue collectively. Organizing a meeting with the project team allows for open communication and collaborative problem-solving. This aligns with the PMBOK® Guide’s principles of conflict resolution, which include promoting a team environment where issues can be discussed and resolved in a manner that respects all parties’ perspectives1. It also adheres to the Professional in Business Analysis (PMI-PBA) guidelines, which emphasize the importance of addressing conflicts directly and seeking a resolution that supports project delivery2.

Conducting feasibility studies is a critical part of project management to ensure that a project is viable and can proceed successfully. According to best practices, it is advisable to obtain approval to conduct the feasibility study in parallel with the prefeasibility study. This ensures that the project timelines are maintained without delay. The feasibility study is an essential step that should not be skipped or merged with the prefeasibility study, as it provides a deeper level of analysis regarding the project’s viability12. References: “Using Feasibility Studies in Project Management [2024]” by Asana1; “What Is a Feasibility Study? How to Conduct One for Your Project” by Jennifer Bridges2.

In an agile project, transparency and communication are key. When a team member anticipates a delay, it is important to discuss the issue openly with the team as soon as possible. This allows the team to understand the potential impact on the project and to collaborate on finding a solution. The agile methodology encourages daily meetings for this purpose, making it the ideal setting to address such concerns. This approach is supported by the PMBOK® Guide, which emphasizes the importance of communication and stakeholder engagement in project management. Additionally, the Professional in Business Analysis (PBA) reference materials highlight the value of addressing issues promptly and collaboratively in an agile environment.

PMBOK® Guide – Sixth Edition; Professional in Business Analysis (PBA) Reference Materials.

 When a project deliverable is not fulfilling the business case requirement, it is important for the project manager to understand why this is happening. Analyzing the business benefits criteria and assumptions (Option C) can help identify if there were any discrepancies or misunderstandings in the initial planning stages. This could include reassessing the expected benefits, costs, risks, and strategic alignment of the project.

Additionally, scheduling a project review meeting to analyze the root cause (Option E) can provide valuable insights into what went wrong. This could involve discussions with the project team, stakeholders, and possibly the operations team who are now handling the deliverable. The goal of this meeting would be to understand the root cause of the issue and to identify potential solutions or improvements for future projects.

= Project Management Institute’s Guide to the Project Management Body of Knowledge (PMBOK® Guide), 6th Edition1; Unito’s guide on Project Deliverables2.

The PMBOK® Guide emphasizes the importance of team dynamics and project performance. In this scenario, the project manager should assess the impact of the team member’s enrollment in a master’s program on the project’s performance. This involves understanding the team member’s commitment to both the master’s program and the project, and determining how their coursework might affect their project responsibilities. The goal is to ensure that the project’s last phase can be completed successfully without compromising the team member’s educational goals123.

The project manager should take the following actions to ensure proper stakeholder involvement:

Prioritize stakeholders based on the project phase and need (Option A): Not all stakeholders need to be involved at all stages of the project. The project manager should identify and prioritize stakeholders based on the current phase of the project and the need for their involvement1.

Develop a stakeholder impact influence matrix to determine the level of engagement (Option B): This matrix helps in understanding the level of influence and interest each stakeholder has in the project. It assists in determining the level of communication and engagement required for each stakeholder1.

Perform a stakeholder assessment to align with the project objectives (Option C): A stakeholder assessment helps in understanding the stakeholders’ interests, expectations, and influence. It ensures that the stakeholders’ needs and expectations are aligned with the project objectives2.

Including all stakeholders in the stakeholder engagement plan and providing the same level of communication (Option D) may not be feasible or efficient as different stakeholders have different levels of interest and influence in the project1. Classifying and ranking stakeholders based on their positions in the organization (Option E) may not always reflect their actual influence or interest in the project1.

According to the Project Management Body of Knowledge (PMBOK) guide, effective stakeholder engagement is crucial for the success of a project. The project manager should schedule regular meetings with the key stakeholder to provide updates and receive feedback. This will ensure that the stakeholder is kept informed about the progress of the project and can provide valuable input. Additionally, promoting an adaptive and transparent environment where the team can easily communicate with the stakeholders will help in building trust and improving the relationship with the stakeholder. References: PMBOK Guide, 6th Edition, Section 13: Stakeholder Management

To ensure that the project acceptance criteria are met for all project deliverables, the project manager should include the expectations and needs of project stakeholders in the creation of the project acceptance criteria. This aligns with the best practices in project management, which emphasize the importance of understanding and incorporating stakeholder requirements to achieve project success. By doing so, the project manager can ensure that the deliverables will meet the agreed-upon standards and satisfy stakeholder needs, which is crucial for the acceptance of the project outcomes.

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

Project Management Institute. (2024). Project Management Professional (PMP)® Certification Handbook.

KnowledgeHut. (2024). Project Management Acceptance Criteria with Examples.

ProjectManagers.Org. (2024). Project Acceptance Criteria • The Definitive Guide.

The project manager should work with the PMO manager to generate an onboarding plan for the new product owner. This is because the product owner’s role is crucial in understanding the product and conveying its requirements to the team. An onboarding plan would help the new product owner to understand the product, the project, and their role better. It would also help in establishing the product owner’s credibility with the team.

While options A, B, and D might be part of the subsequent actions, the first step should be to work on an onboarding plan. Assuming the role of the product owner (option A) might create confusion about roles and responsibilities. Scheduling time to share insights (option B) is important, but it should be part of a structured onboarding plan. Organizing a team-building activity (option D) might help in building respect, but it does not address the root cause of the problem, which is the product owner’s lack of knowledge.

Project Management Body of Knowledge (PMBOK) Guide, 6th Edition, Section 9.1: Plan Resource Management.

In a hybrid project management approach, which combines elements of both predictive and adaptive methodologies, it is crucial to address changes in project scope or direction promptly and formally. The PMBOK Guide emphasizes the importance of managing stakeholder engagement and ensuring that project objectives align with business needs. When a client expresses dissatisfaction and a desire to change the project’s course, the project manager should first seek to understand the new requirements and then formalize these changes through a contract amendment. This ensures that all parties have a clear understanding of the new expectations and agree to the revised terms before proceeding1.

 In an agile environment, accountability is achieved through transparency, collaboration, and shared understanding of the project’s goals and objectives. The agile model emphasizes the importance of open communication and collective responsibility among team members. By fostering an environment where the marketing vice president and other stakeholders can openly discuss issues and agree on objectives, the project manager ensures that everyone is aligned and accountable for the project’s success. This approach aligns with the principles of both Agile and Business Analysis, which advocate for stakeholder engagement and collaborative decision-making to deliver value and meet business needs. References: (Agile Methodology in Project Management as a Licensed PMP1, Accountability is a Quality of Agile2, Professional in Business Analysis Certification | PMI3, What is Personal accountability? – The Functional BA4)

The success of virtual teams largely depends on regular communication and the establishment of a strong sense of community among team members. Planning regular virtual meetings is a best practice for managing virtual project teams, as it helps to motivate and support the team, fosters collaboration, and keeps team members engaged1. This approach aligns with the principles of both Project Management and Business Analysis, which emphasize the importance of stakeholder engagement and team dynamics for project success2. References:

Best practices for managing and developing virtual project teams1.

Managing Virtual Teams for High Performance2.

When a stakeholder requests changes that could impact the project scope, the project manager should first review and validate the scope management plan. This plan outlines how scope changes are managed and controlled. If the new ideas are not covered within the existing project scope, they may require a formal change request and impact analysis before proceeding. This ensures that any changes align with project objectives and do not adversely affect project constraints such as time, cost, and quality.

The presence of references to unrelated products in project documentation indicates a need for improved quality control measures. Developing a standard for document quality control is a proactive approach that aligns with PMI’s emphasis on quality management and the use of standardized processes to ensure project deliverables meet the required standards and are free from errors. This action will help prevent similar issues in the future by establishing clear guidelines and checks for documentation quality, which is a fundamental aspect of project management as per PMI standards12.

 In the context of Agile methodologies, such as Scrum, which is often used in conjunction with PMP practices, the daily standup meeting serves as a platform for team members to communicate progress and identify impediments to the sprint goal. When a delay is reported, especially one that involves an external vendor, it is crucial for the project manager to facilitate a resolution that does not disrupt the team’s workflow. The project manager should gather all necessary details from the team member to understand the issue fully and then work directly with the vendor to resolve it. This approach aligns with the principles of effective communication and vendor management, ensuring that the project manager has the information needed to address the problem without overburdening the team member with responsibilities that fall outside their scope.

The answer is supported by best practices in vendor management and communication as outlined in the PMBOK® Guide and Agile methodologies, which emphasize the importance of the project manager’s role in addressing issues with external vendors and maintaining the flow of the sprint. Additionally, the approach of engaging with the vendor directly is consistent with the guidance provided in the Professional in Business Analysis (PMI-PBA) reference materials, which advocate for clear communication and negotiation to resolve vendor-related issues and conflicts.

In an agile project, the Definition of Done (DoD) is a shared understanding among the team about what it means for work to be complete. This includes the completion of all user stories and meeting all acceptance criteria. If the sprint goals were not met, but there were no defects for the new user stories and no new requirements were discussed, it indicates a possible misalignment between the team’s understanding of the DoD and the product owner’s expectations. To avoid such situations in the future, the project manager should review the DoD with the product owner to ensure that everyone has the same understanding of what it means for work to be complete1.

Agile project management focuses on continuous improvement, scope flexibility, team input, and delivering essential quality products2. Agile project management approaches include scrum as a framework, extreme programming (XP) for building in quality upfront, and lean thinking to eliminate waste1. These and many other agile methodologies have in common flexible scope, frequent interaction, and delivering working, tested software2.

 When a project encounters a risk that was not fully anticipated, and the project manager has developed a new response that deviates from the original plan, it is essential to obtain management approval before proceeding. This ensures that the new approach is aligned with the project’s objectives and that management is aware of the changes being made to the risk response plan. The PMBOK Guide highlights the importance of involving project stakeholders, particularly management, when significant changes are proposed1. This is also supported by best practices in business analysis, which advocate for stakeholder engagement and approval in the decision-making process to address risks effectively2.

In the context of iteration planning and task selection, the project lead plays a crucial role in empowering team members to take on challenging tasks. Coaching is a key aspect of this support, as it involves guiding the team member through the process of understanding the tasks, assessing their own skills, and encouraging them to take ownership of the tasks they are interested in. This approach not only helps in personal development but also ensures that the team member is fully committed and has the confidence to tackle the challenges ahead.

The answer is supported by best practices in Agile methodologies, where coaching and empowerment are essential for team development and performance12. The project lead’s role in facilitating iteration planning meetings and helping the team in task estimation and selection is well-documented in the PMI’s resources on Agile practices3.

The best course of action when team members are unfamiliar with a system is to provide training. This ensures that all team members have the necessary knowledge to perform their tasks effectively. According to the PMBOK® Guide, project managers should develop the team through training, team-building activities, and creating an environment conducive to teamwork. Training enhances team members’ technical and interpersonal skills, which is essential for project success. Furthermore, the PMI-PBA® Reference Materials emphasize the importance of ensuring that stakeholders (in this case, team members) understand the requirements, which includes the rules and criteria for applicant approval in the public housing project.

= Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition and Agile Practice Guide. Newtown Square, PA: Author. Project Management Institute. (2015). Business Analysis for Practitioners: A Practice Guide. Newtown Square, PA: Author.

In Agile project management, it is crucial to address issues as they arise, particularly when an iteration is nearing completion and the team is struggling with user stories. The first step should be to meet with the project team to understand the challenges they are facing and collaboratively develop a resolution. This approach is supported by the principles of Agile, which emphasize team collaboration, regular communication, and adaptive planning to overcome obstacles1. By engaging the team directly, the project manager can facilitate problem-solving and ensure that the team’s insights and suggestions are incorporated into the solution.

For a project with a long timeline and complex scope, where the client requires both a high-level, long-term plan and the ability to add features incrementally, a hybrid approach is suitable. Starting with a predictive approach allows the project manager to establish a clear structure and plan using a work breakdown structure (WBS). This sets the foundation for the project’s scope, deliverables, and milestones. Transitioning to an agile approach for execution enables the project to adapt to changes and deliver value incrementally, which meets the client’s need for immediate functionality and continuous improvement. This hybrid method leverages the strengths of both approaches: the clarity and predictability of a predictive approach and the flexibility and responsiveness of an agile approach12.

In the Scrum framework, the traditional project schedule is replaced by a combination of the sprint plan and the product roadmap. The sprint plan outlines the work to be performed during the sprint, which typically lasts 2-4 weeks, and includes the sprint goal, the set of product backlog items selected for the sprint, plus the plan for delivering the product increment and realizing the sprint goal. The product roadmap provides a longer-term view of where the product is headed and the milestones along the way. It is a strategic document that outlines the vision, direction, priorities, and progress of the product over time.

The information is aligned with the Scrum Guide and the principles outlined in the Project Management Institute’s (PMI) Agile Practice Guide, which complements the PMBOK® Guide and other PMI standards.

When a project undergoes an executive-level reorganization resulting in a new sponsor who is not keen on continuing the project, the project manager should engage with the new sponsor to align their understanding and commitment to the project’s vision and outcomes. This approach is supported by PMI’s guidelines which emphasize the importance of the project sponsor’s role in championing the project, endorsing it as a valued investment, and maintaining a good working relationship with key stakeholders, including the project manager12. The project manager should utilize the opportunity to communicate the strategic significance of the project and how it serves the organization’s objectives, thereby fostering support from the new sponsor1.

In projects with high levels of uncertainty, especially those that are innovative in nature, it is beneficial to increase the number of iterations. This allows for more frequent reassessments and adjustments, which can help in managing change requests more effectively. By breaking down the project into smaller parts and reassessing at the end of each iteration, the project manager can incorporate necessary changes in a controlled manner, thus reducing the overall number of change requests.

The PMBOK Guide outlines the iterative approach as a means to manage and control projects with high uncertainty1. It suggests that iterative cycles allow for continuous improvement and adaptation, which is crucial for innovation projects2. The Professional in Business Analysis materials also support this approach, emphasizing the importance of iterative review and adaptation in response to change34.

 In an agile project environment, when faced with customer complaints regarding project stability and other critical issues, it is essential to engage the team in a collaborative problem-solving process. A brainstorming session is an effective way to gather collective insights and identify the root causes of the issues raised by the customer. This approach aligns with the agile principles of valuing individuals and interactions over processes and tools, and responding to change over following a plan. By involving the team in identifying problems and generating solutions, the project manager can ensure that the project’s direction is realigned with customer expectations and project goals1.

 In an agile project, daily standup meetings are crucial for maintaining open communication among team members. These meetings serve as a platform for team members to report on their progress, discuss any challenges they are facing, and understand the work being done by their peers. When these meetings are not consistently attended, it can lead to a lack of understanding of each other’s work, creating silos within the team. Regular attendance and active participation in daily standups are essential for fostering collaboration and ensuring that all team members are aligned and informed about the project’s progress.

= Agile communication best practices - PM-Training1.

Managing interdependencies in a cross-organizational project, especially one that affects multiple business units and shares resources with other projects, requires a coordinated approach. The PMBOK Guide highlights the importance of identifying and engaging stakeholders who can influence the project’s outcomes1. In this scenario, program managers are typically responsible for overseeing the program’s overall direction and managing dependencies across projects within the program2. Consulting with program managers first can provide a comprehensive view of the program’s objectives, resources, and constraints, which is crucial for effectively managing interdependencies. References: Stakeholder Management - Project Management Institute; Project Stakeholder Management According to the PMBOK12.

On day four of a 15-day sprint, the team should continue with the sprint work as planned and keep monitoring the burndown chart. The burndown chart is a visual representation of the work left versus the time remaining in the sprint. If the “Actual” line closely follows the “Planned” line, it indicates that the team is on track. Making adjustments or changing the sprint scope at this stage is premature unless there are significant deviations or impediments1. The team should maintain their current pace and monitor progress, making adjustments only if necessary as the sprint progresses2. References: “Burndown Chart: What it is, How to Use it, Example [2024]” by Asana; “Scrum Sprint Burndown Chart [Everything you Need to Know]” by KnowledgeHut12.

According to the PMBOK Guide, 7th edition, an agile project is one that follows an adaptive development approach, where requirements and solutions evolve through collaborative efforts of self-organizing and cross-functional teams and their customers. In an agile project, the product owner is the person who represents the voice of the customer and defines the product vision and value. The product owner also prioritizes the product backlog, which is a list of features and requirements that need to be delivered by the project team. The product owner’s interest in having features released during product development over having the product completed in one year indicates a preference for delivering value early and frequently, rather than waiting for a final product. This is consistent with the agile principle of satisfying the customer through early and continuous delivery of valuable software. Therefore, the project manager should facilitate sprint planning sessions with a focus on defining the minimum viable product (MVP), which is the version of the product that has enough features to satisfy the customer’s needs and provide feedback for future development. By doing so, the project manager can help the product owner and the project team to align their expectations, scope, and schedule, and to deliver value incrementally and iteratively. References:

PMBOK Guide, 7th edition, page 19, section 1.2.2, Adaptive Development Approach

PMBOK Guide, 7th edition, page 20, section 1.2.3, Agile Project Environment

PMBOK Guide, 7th edition, page 21, section 1.2.4, Agile Principles

PMBOK Guide, 7th edition, page 23, section 1.2.5, Agile Team Roles

PMBOK Guide, 7th edition, page 25, section 1.2.6, Agile Practices

According to the PMBOK Guide, stakeholder engagement is the process of communicating and working with stakeholders to meet their needs and expectations, address issues, and foster appropriate stakeholder involvement. The project manager should engage with the town’s authorities to understand the root cause of their resistance, address their concerns, and negotiate a mutually acceptable solution that aligns with the project objectives and scope. This is also consistent with the PMI Code of Ethics and Professional Conduct, which states that project managers should respect the legitimate interests of others and seek to resolve conflicts constructively. Changing the project scope, moving to the next town, or sending the minutes of stakeholder engagements are not effective ways of dealing with stakeholder resistance, as they may create more problems, risks, or dissatisfaction for the project and its stakeholders. References:

PMBOK Guide, 7th edition, pages 156-157, 161-162, 166-167

PMI Code of Ethics and Professional Conduct, pages 4-5

PMI-PBA Guide, 2nd edition, pages 75-76, 80-81, 85-86

The agile leader should speak directly with the team member about improvements and commit to an agreed-upon time frame. This is the best option because it shows the agile leader’s respect and empathy for the team member, as well as the willingness to help them overcome their challenges and grow their skills. By speaking directly with the team member, the agile leader can also understand the root cause of the problem, provide constructive feedback, and agree on a realistic and achievable plan for improvement. This option also aligns with the agile values of “individuals and interactions over processes and tools” and "responding to change over following a plan"1.

The other options are not as effective as option D. Option A is not supportive and may demotivate the team member and create resentment. Option B is not appropriate and may embarrass the team member and lower the team morale. Option C is not relevant and may not address the team member’s specific needs and gaps. References: 1: Agile Manifesto, [Manifesto for Agile Software Development]

 Cross-training is a technique that allows team members to share and learn skills from each other. It can enhance team performance, increase flexibility, and reduce risks related to staff turnover or unavailability. It can also improve team cohesion and collaboration. In this scenario, the project manager should allow the engineer and designer to cross-train with each other, as this would benefit both the project and the individuals. The engineer would learn a new skill that is required for the tasks, and the designer would reinforce their existing skill by teaching it. This would also save time and money compared to external training options. Escalating the situation to the engineer’s manager, requesting external training for the engineer, or requesting external training for both the engineer and the designer are not the best choices, as they would not leverage the existing resources and expertise within the team. References: PMBOK Guide, 6th edition, page 339; Professional in Business Analysis (PMI-PBA)® Handbook, page 16.

The project manager should first document the client’s responsibility for the integration with the security subsystem as part of the project scope statement. This will help to define the boundaries of the project and clarify the roles and responsibilities of the project team and the client. It will also help to avoid scope creep and manage expectations. Planning the implementation, recording the issue, and informing the client are actions that can be done later, after the scope is clearly defined and agreed upon. References:

PMP Exam Content Outline, Domain II: Process, Task 1: Execute project with the urgency required to deliver business value.

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 5: Project Scope Management, Section 5.3: Define Scope, Page 154.

 According to the hybrid project management approach, which combines elements of waterfall and agile methodologies, the project manager should facilitate the collaboration and communication among the team members and adjust the scope and schedule as needed12. However, any changes to the product scope should be controlled and evaluated for their impact on the project objectives, risks, quality, and customer satisfaction34. Therefore, the best option for the project manager in this scenario is to follow the proper change control process and evaluate the change for further impact. This way, the project manager can ensure that the change is justified, approved, documented, and communicated to all relevant stakeholders5. The project manager can also assess the potential risks and benefits of the additional feature and take appropriate actions to mitigate or exploit them6.

The other options are not the best ways to avoid this situation in the future. Managing the scope baseline to influence the factors that drive change is a proactive approach to prevent unnecessary or excessive changes, but it does not address the change that has already occurred7. Working with the customer to ensure the feature adds value is a good practice to align the product with the customer needs, but it does not consider the impact of the change on the project constraints or other stakeholders8. Performing frequent reviews with the customer to ensure that the product is working as expected is a useful technique to gather feedback and validate the product quality, but it does not prevent the introduction of new features without proper change control. References: 1: What is the Hybrid Approach in Project Management? | Hygger.io 2: Hybrid Project Management: What is it, Approach & Software - Teamhood 3: [Project Scope Management | Project Management Institute] 4: [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition], p. 131-132 5: [Change Control Process: A Complete Guide - ProjectManager.com] 6: [Project Risk Management | Project Management Institute] 7: [Project Scope Management | Project Management Institute] 8: [Project Stakeholder Management | Project Management Institute] : [Project Quality Management | Project Management Institute] : Project Scope Management | Project Management Institute : A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition : Change Control Process: A Complete Guide - ProjectManager.com : Project Risk Management | Project Management Institute : Project Stakeholder Management | Project Management Institute : Project Quality Management | Project Management Institute

A spike is a time-boxed activity that is used to explore a specific topic or issue, such as a new requirement, a technical challenge, or a risk. A spike can help the project team to gain more knowledge, reduce uncertainty, and plan better. In this case, the project manager should inform the project team of the new privacy law and create a spike for the next iteration to investigate how to comply with it and what impact it will have on the project scope, schedule, cost, and quality. References: PMBOK Guide, 7th edition, section 6.2.3.2; Professional in Business Analysis (PMI-PBA) Guide, 2nd edition, section 5.2.3.2.

The statement of work (SOW) is a document that describes the project scope, deliverables, acceptance criteria, assumptions, and constraints1. It is usually part of the contract between the buyer and the seller2. If the project manager remembers negotiating and agreeing to the deliverable during the tender process, they should look to see if the deliverable is described in the SOW, which would be a contractual obligation for the seller. Requesting a change in the contract, adding the deliverable to the requirements traceability matrix, or terminating the contract are not appropriate actions in this situation. References:

1 PMBOK Guide, 6th edition, page 154

2 PMBOK Guide, 6th edition, page 473