PMP Exam Dumps - PMI Project-Management-Professional Questions and Answers

 In a hybrid project management approach, which combines elements of both traditional and agile methodologies, it is essential to address quality issues promptly to minimize their impact on the project timeline and budget. The agile aspect of the hybrid approach emphasizes continuous improvement, team collaboration, and adaptability. Therefore, addressing quality issues during the next sprint planning meeting allows the project team to discuss and implement corrective actions swiftly. This aligns with the agile principle of inspecting and adapting, where the team reflects on how to become more effective and adjusts its behavior accordingly.

PMBOK® Guide - Sixth Edition and Agile Practice Guide

The PMI Guide to Business Analysis

Project Quality Management According to the PMBOK

The project team is in the “Storming” phase of the Tuckman Ladder Model. This phase is characterized by conflict and disagreement, where team members challenge each other, the project, and its leadership. The discomfort among team members and the challenges to the schedule are indicative of this phase. It’s a crucial stage where the team starts to address the project’s tasks, plans, and ideas, leading to various opinions that can cause conflict. The project manager’s role during this phase is to help the team resolve conflicts and disagreements and guide them towards a common understanding and cooperation12.

When new legal requirements emerge during a project, it is essential to assess the impact of these changes on the project deliverables. The project manager should collaborate with relevant stakeholders to understand the implications of noncompliance and determine the necessary actions to align with the new requirements. This may involve updating the project’s risk register to reflect the new risks associated with these legal changes and developing a plan to mitigate them. This approach is in line with the PMBOK® Guide’s principles, which advocate for proactive risk management and stakeholder engagement12345.

Implementing short cycles for inspection and providing feedback is aligned with the principles of servant leadership and agile project management. Servant leadership emphasizes flexibility, empathy, and empowering team members to adapt and thrive1. It involves facilitating the team’s success by ensuring open communication and stakeholder engagement2. In the context of agile project management, short cycles or iterations allow for regular assessment of the project’s progress and early detection of potential issues, which aligns with the PMBOK® Guide’s principle of engaging with stakeholders3. This approach allows the project manager to address the stakeholder’s concerns by demonstrating progress and managing risks proactively.

The Project Management Professional (PMP) certification recognizes the ability of project managers to lead projects in any industry1. One of the key skills validated by the PMP certification is the ability to motivate people and teams through all phases of a successful project1. In the context of a project that is part of a program geared toward a major technology disruption, the role of the project manager is to keep the team engaged and focused on the project’s direction and to set a clear vision for the project and ensure it is visible to all stakeholders. This approach fosters a sense of ownership, encourages learning, and promotes the development of problem-solving skills within the team. References: PMP Certification

 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 assist the product owner by providing a comprehensive overview of what has been completed, the release plan, and actively engage in capturing the stakeholders’ expectations for future involvement. This ensures that stakeholders are well-informed about the project’s progress and understand how they can contribute moving forward. It also helps in managing stakeholders’ expectations and aligning their understanding with the project’s roadmap. References: This answer is verified based on the best practices for stakeholder communication and engagement as outlined in the PMBOK Guide and the standards of practice for stakeholder management12. Additionally, it aligns with the principles of stakeholder engagement in business analysis, which emphasize the importance of clear communication and managing stakeholder expectations34.

 The first step in managing stakeholder disagreement, especially regarding the use of new tools, is to investigate the reasons behind the disagreement. This involves understanding the perspectives and concerns of the stakeholders, which can reveal the underlying issues that need to be addressed. Seeking to understand before being understood is a principle that aligns with the PMBOK® Guide’s emphasis on stakeholder engagement as a key aspect of project management. By identifying the gaps and concerns, the project manager can work towards building consensus and finding a solution that aligns with the project’s objectives and the stakeholders’ needs. References: Overcoming Stakeholder Resistance Through Dialogue1, PMBOK® Guide – Sixth Edition.

 Facilitation is a key skill for agile teams, and the opportunity to facilitate an iteration meeting can provide valuable hands-on experience for a team member looking to improve these skills. According to the PMI, facilitation involves guiding the team through meetings and discussions, ensuring that objectives are met and that every team member has a voice. Allowing the team member to facilitate an upcoming iteration meeting aligns with the principles of empowerment and growth within agile teams. The retrospective review of the facilitated meeting will offer a chance for the team member to receive constructive feedback and further develop their facilitation abilities.

= The answer is supported by the PMI’s resources on effective facilitation and the role of a facilitator in an agile team, which emphasize the importance of practical experience and continuous improvement in facilitation skills12.

In Agile project management, when a resource is lost and new requirements are added to the backlog, the project manager should reevaluate the backlog priority with the product owner. This is because the velocity, or the amount of work the team can handle in a given iteration, has been impacted. The project manager and the product owner need to reassess the priorities in the backlog to ensure that the most valuable items are being worked on given the current capacity of the team12. References:

Agile Project Management: What Is It and Why Does It Matter?1

Agile Project Manager Roles and Responsibilities: A Career Guide2

Direct communication with the HR resource is the most effective approach to understand their concerns regarding the project plan. This aligns with conflict resolution strategies that emphasize direct engagement and problem-solving as key methods for addressing disagreements and misunderstandings in project management contexts12. By speaking directly, the project manager can gather firsthand information, clarify any misconceptions, and work collaboratively with the HR resource to address any issues, ensuring that the project plan aligns with HR requirements and constraints.

= This approach is supported by PMI’s guidelines on conflict resolution, which suggest that direct conversation is often the best first step in resolving conflicts, as it allows for immediate clarification and the opportunity to address concerns in a constructive manner123.

After a workshop, it is essential to maintain the momentum and ensure that the action items identified are addressed promptly. The project manager should work with the team to prioritize these actions based on their importance and urgency, assign clear ownership to team members, and set deadlines for completion. This approach ensures that the team remains focused and that progress is monitored, which is critical for the successful delivery of project outcomes.

The project manager is in the middle of the project, which is divided into five iterations. Each user story is worth $50, so the total budget for the project is $50 * 100 = $5000. The actual expenditure so far is $200, and 50 user stories have been delivered. This means that the project has spent less than the budgeted amount for the 50 user stories ($50 * 50 = $2500), so it is under budget. Since the project is in the middle and has delivered half of the user stories, it is on schedule.

The Project Management Professional (PMP)® Certification from PMI1, PMP Examination Content Outline - June 2019 - Project Management Institute2, Professional in Business Analysis Reference Materials3.

The best approach for a project manager to help a new compliance specialist improve is to engage directly with the specialist to understand their perspective and provide targeted feedback. This aligns with the PMBOK® Guide’s emphasis on effective communication and stakeholder engagement as key aspects of project management. By coordinating a one-to-one meeting, the project manager can offer constructive feedback, understand any challenges the specialist is facing, and work together to develop a plan for improvement. This method is also supported by the Professional in Business Analysis (PBA) reference materials, which advocate for direct communication and feedback as tools for professional development.

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

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.

The best approach in this situation is for the project manager to engage directly with the experienced team member to address the behavior. This should be done in a supportive manner, aiming to understand the reasons behind the team member’s actions and to find a constructive way forward. This aligns with conflict resolution strategies that emphasize problem-solving and collaboration, which are considered effective in project management and business analysis contexts. By addressing the issue privately, the project manager can prevent further team disruption and work towards a resolution that maintains team cohesion and productivity.

The answer is verified with the principles of conflict resolution as outlined in the PMBOK® Guide and the Professional in Business Analysis (PMI-PBA) reference materials, which suggest that direct and supportive communication is key to resolving such conflicts123.

Agile methodologies emphasize customer collaboration over contract negotiation and responding to change over following a plan. Regular demonstrations of product features allow for continuous customer feedback, which is integral to agile projects. This practice ensures that the product evolves according to the customer’s needs and maintains quality throughout development123.

The project manager should use a hybrid model to combine predictive and adaptive life cycles. This approach allows for the initial planning and structure of the predictive approach while also incorporating the flexibility of the adaptive approach to respond to changes and new information. The hybrid approach is beneficial in scenarios where the project has clear phases but also requires adaptability to changing requirements and inputs from stakeholders.

The project manager should set clear expectations with the new team member and explain the differences between the agile and predictive approaches, as well as the benefits and challenges of working in a hybrid environment. The project manager should also encourage the new team member to share their agile experience and best practices with the existing team members, and foster a collaborative and learning culture among the team. Training the new team member in the predictive approach (A) is not enough, as it does not address the potential gaps and conflicts that may arise from working in a hybrid environment. Acknowledging that hiring the new employee is a risk (B) is not helpful, as it may create a negative impression and undermine the trust and respect among the team members. Meeting with all team members and explaining the new employee’s position (D) is also not sufficient, as it does not clarify the expectations and roles of the new team member, nor does it leverage their agile experience. References: PMBOK Guide, 7th edition, page 91; Agile Practice Guide, page 14.

In today’s global and digital work environment, teams often work remotely and are spread across different geographical locations. The Project Management Professional (PMP) guidelines suggest that in such situations, the project manager should leverage technology to facilitate communication and collaboration. Setting up a weekly video conference can help monitor the progress of the team member’s work and ensure that they are still able to contribute effectively to the project, despite their relocation. This approach also maintains the continuity and dynamics of the existing team. References: A Guide to the Project Management Body of Knowledge (PMBOK Guide) from www.pmi.org. Specifically, the section on Project Communications Management, which discusses the use of communication technology to manage remote teams.

 Leadership roles require strong communication skills, as they are essential for effectively leading teams and projects. The project manager should support the team member’s interest in leadership by recommending training to improve their communication skills. This not only aids the individual’s career development but also benefits the organization by preparing a technically skilled employee for future leadership roles. Effective communication is a core skill for leaders, and enhancing this skill can lead to better team alignment, stakeholder engagement, and project success123.

To answer this question, we need to calculate the earned value (EV), the planned value (PV), and the actual cost (AC) of the project based on the given information. Then, we can compare them to determine the project status in terms of schedule and cost performance.

The earned value (EV) is the monetary value of the work completed so far. It can be calculated by multiplying the percent complete of the project by the budget at completion (BAC), which is the total approved budget for the project. The BAC can be obtained by adding the approved work package cost estimates, the contingency reserves, and the management reserves. In this case, the BAC is:

BAC=9500+500+(10%×500)=10550

The EV is then:

EV=50%×10550=5275

The planned value (PV) is the monetary value of the work that was planned to be completed by a certain date. It can be calculated by multiplying the planned percent of the project by the BAC. In this case, the PV is:

PV=40%×10550=4220

The actual cost (AC) is the monetary value of the work actually performed. It is given as:

AC=4500

To determine the project status, we can use the cost variance (CV) and the schedule variance (SV) formulas. The CV is the difference between the EV and the AC, and it indicates whether the project is under budget or over budget. A positive CV means the project is under budget, while a negative CV means the project is over budget. The CV is:

CV=EV−AC=5275−4500=775

The SV is the difference between the EV and the PV, and it indicates whether the project is ahead of schedule or behind schedule. A positive SV means the project is ahead of schedule, while a negative SV means the project is behind schedule. The SV is:

SV=EV−PV=5275−4220=1055

From the CV and SV values, we can conclude that the project is under budget and ahead of schedule. To find the percentage of deviation from the planned cost and schedule, we can use the cost performance index (CPI) and the schedule performance index (SPI) formulas. The CPI is the ratio of the EV to the AC, and it measures the cost efficiency of the project. A CPI greater than 1 means the project is under budget, while a CPI less than 1 means the project is over budget. The CPI is:

CPI=ACEV​=45005275​=1.17

The SPI is the ratio of the EV to the PV, and it measures the schedule efficiency of the project. A SPI greater than 1 means the project is ahead of schedule, while a SPI less than 1 means the project is behind schedule. The SPI is:

SPI=PVEV​=42205275​=1.25

From the CPI and SPI values, we can calculate the percentage of deviation from the planned cost and schedule by subtracting 1 and multiplying by 100. The percentage of deviation from the planned cost is:

(CPI−1)×100=(1.17−1)×100=17%

The percentage of deviation from the planned schedule is:

(SPI−1)×100=(1.25−1)×100=25%

Therefore, the project cost is 17% lower than planned, and the project schedule is 25% ahead of planned. Among the given options, the closest one is B. The project cost is 10% lower than planned.

The best course of action for the project manager in this situation is to review the stakeholder’s communication requirements. This aligns with the principles of stakeholder engagement and communication management in project management. By reviewing the communication requirements, the project manager can ensure that the information needs of the stakeholder are being met without causing undue disruption to the team’s work. This may involve adjusting the communication plan to provide the stakeholder with the necessary updates in a manner that is less intrusive to the team member’s workflow.

= The answer is verified by the principles found in the PMBOK® Guide, which emphasizes the importance of managing stakeholder expectations through effective communication strategies1. Additionally, the Professional in Business Analysis Reference Materials supports the approach of tailoring communication to meet the needs of stakeholders2.

Comprehensive and Detailed Explanation:

The PMO typically maintains standard templates and documentation requirements, especially for steering committees. Engaging the PMO ensures alignment with organizational standards and expectations.

A may result in inconsistent or outdated artifacts.

C may provide insight but not ensure consistency.

D may waste time if templates already exist.

The kick-off meeting is a critical step in the project management process, as it aligns the project team with the project’s objectives and establishes a common understanding among stakeholders. In the context of a multinational company launching a digital transformation project, it is practical to use digital or virtual tools for the kick-off meeting. This approach not only minimizes geographic boundaries, enabling participation from all regions and business lines, but also aligns with the digital nature of the project itself. It is a cost-effective solution that can foster collaboration and communication without the need for travel, which is especially relevant given the global scope of the project.

 When facing the potential departure of a key team member during the last iteration of a hybrid project, it is important for the project manager to engage directly with the individual to understand their concerns and reasons for wanting to leave. This aligns with the PMI’s guidance on stakeholder engagement and team dynamics. By having a meeting with the team member, the project manager can explore the underlying issues and work on possible solutions or contingencies that may persuade the team member to stay or ensure a smooth transition if their departure is inevitable1.

 The project manager should meet with the stakeholders to recommend the use of a time and materials (T&M) contract to address the problem, as this type of contract is more suitable for agile projects that have changing requirements and priorities. A T&M contract allows the buyer to pay the seller based on the actual hours of work and the cost of materials, rather than a fixed price. This can provide more flexibility and adaptability for the project, and reduce the risk of budget overrun. The other options are not as effective or appropriate as recommending a T&M contract. Sending a detailed status report may inform the stakeholders of the issue, but it does not propose a solution. Submitting a change request may increase the funding, but it does not address the root cause of the problem, which is the mismatch between the contract type and the project approach. Waiting until the next gate review meeting may delay the resolution of the problem, and increase the likelihood of further deviation from the EAC. References:

PMBOK Guide, 7th edition, page 163

PMI-PBA Exam Content Outline, 2018, page 10

PMP question 391

 The project manager should have conducted a thorough assessment of the team members’ competencies and skills in relation to the training content before enrolling them. This would involve analyzing the training material to ensure it aligns with the team members’ current skills and the tasks they are expected to perform. By doing so, the project manager could have ensured the training was appropriate and beneficial for the team members, thereby preventing the situation where the training felt too difficult and misaligned with their tasks2.

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.

Comprehensive and Detailed Explanation:

When multiple stakeholders have differing expectations, it is best to bring them together in collaborative sessions such as requirements workshops or facilitated discussions. This ensures alignment on goals and scope and helps define a clear MVP to minimize future change requests.

* A is rigid and may create resistance.

* B risks alienating less-influential stakeholders.

* D lacks the collaborative element required in complex stakeholder environments.

* C promotes inclusion and consensus-building, key for stakeholder alignment.

The project manager is responsible for ensuring that the project remains aligned with its expected benefits and strategic objectives. If the benefits management plan contains questionable or outdated forecasted values, the correct course of action is to confirm that information with the sponsor and key stakeholders. This ensures alignment before execution continues.

Option B is premature and drastic.

Option C disregards the risk of misalignment with business value.

Option D assumes changes before confirming whether the original forecast is incorrect.

 The project manager should propose a governance model that empowers the teams while providing the necessary oversight to the executive leadership team (Option B). This approach is based on the principle that in an Agile transformation, the focus shifts from controlling to empowering teams1. The governance model should be designed in a way that it provides the necessary oversight to the executive leadership team without stifling the agility of the teams1.

Ensuring that the executive leadership team approves all scope that is being proposed by the multiple agile teams to avoid misalignment (Option A) may not be practical or efficient as it could slow down the agile process1. Proposing a multilayered gate system based on risks and financial expenditures, involving the executive leadership team as needed (Option C) may add unnecessary complexity and could potentially slow down the agile process1. Assuring the executive leadership team that the current governance model will not be affected by the agile approach (Option D) may not be accurate as an Agile transformation often requires changes in the governance model1.

For a multiyear ERP solution project where the business sponsor wants to see value demonstration throughout the project while maintaining the integrity of the final product, the project manager should establish a delivery model that allows for incremental delivery of value. This can be achieved by organizing the project into multiple subsets based on business functions, and delivering each subset as a component of the final product. This approach aligns with the principles of agile and iterative development, which are part of the PMBOK® Guide’s practices. It allows for early and continuous delivery of valuable software components, enabling the business to realize benefits incrementally, which is crucial for long-term projects such as ERP implementations12.

In the context of a project involving new technology and an approach unfamiliar to the team, it is crucial for the project manager to facilitate the identification of a Minimum Viable Product (MVP). This strategy allows the team to focus on creating a product with enough features to satisfy early adopters and provide feedback for future product development. The MVP concept is a core component of agile methodologies, which are part of the PMI’s approach to project management as outlined in the PMBOK® Guide and the Agile Practice Guide. By validating assumptions early on, the project manager can help the team build confidence in their work and address the customer’s concerns regarding market reception by demonstrating a tangible iteration of the product.

The PMBOK® Guide and the Agile Practice Guide, as referenced in the Professional in Business Analysis Reference Materials12.

When an unexpected change or constraint arises during execution, the project manager should first assess the impact. The development team is closest to the technical implications, and their analysis will guide decisions about alternatives, scheduling, or risk.

Per the PMBOK® Guide – Seventh Edition (Risk and Delivery Performance Domains), impact analysis is a key first step before escalating, updating risk logs, or brainstorming new paths forward.

Option A is premature before understanding the scope of impact.

Option C is about risk documentation, but this situation already materialized.

Option D is part of response planning, not the first action.

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.

The acceptance criteria are the measurable and verifiable standards that must be met for the project deliverables to be accepted by the client. They are part of the project scope statement and the project contract, and they should be agreed upon by both parties before the project execution. If the acceptance criteria are not properly defined in the contract, it can lead to disputes and conflicts at the closing phase of the project, as the client may have different expectations and quality standards than the project manager. The other options are not as relevant or effective as defining the acceptance criteria in the contract. The client requirements are the needs and expectations of the client, but they are not the same as the acceptance criteria, which are more specific and measurable. The Manage Quality process is a process that ensures the quality standards are met and the quality activities are performed, but it does not define the acceptance criteria. The project manager should review the standard industry defect rate, but that is not enough to avoid the situation, as the client may have a different defect rate as their acceptance criterion. References:

PMBOK Guide, 7th edition, page 107

PMI-PBA Exam Content Outline, 2018, page 8

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.

Conflict resolution is a critical skill in project management. The PMBOK Guide suggests that conflicts should be addressed using a problem-solving approach, which involves direct confrontation and working collaboratively to identify a solution that satisfies all parties1. This aligns with the Professional in Business Analysis (PMI-PBA) guidelines, which recommend discussion and negotiation among conflicting parties to reach an agreeable solution3. Ignoring the problem or delaying action (options A and C) can lead to a decrease in team morale and productivity, while escalating the issue to HR (option D) should be a last resort after other methods have failed. References: PMBOK Guide, 7th edition; PMI-PBA Handbook; Adaptive US Blog on Conflict Resolution Techniques for Business Analysts123.

 When a project is experiencing roadblocks, especially when similar issues have occurred in past projects, it is crucial to review and improve the processes being used. The PMBOK Guide emphasizes the importance of monitoring and controlling project work to meet performance objectives, and this includes making necessary changes to project processes to enhance efficiency and effectiveness1. In this scenario, since the team is following the processes exactly, it indicates that the processes themselves may be contributing to the delays. Therefore, the project manager should analyze the current processes, identify non-value-adding activities, and seek to eliminate or improve them to overcome the roadblocks and get the project back on track. This approach aligns with the principles of process improvement and value addition, which are central to both Project Management and Business Analysis practices2.

In the context of an agile project, it is essential to foster a collaborative environment where knowledge sharing and coaching are integral to the team’s success. When a lack of knowledge in a specific framework is identified as the root cause for decreased productivity, the project manager should encourage team members to share their expertise and provide coaching to those who need it. This approach aligns with the principles of agile methodologies, which emphasize team collaboration, continuous learning, and adaptability. By promoting knowledge sharing and coaching, the project manager can address the knowledge gap directly and efficiently, without the need for external training or adding new team members, which could disrupt the team’s dynamics and may not address the root cause effectively.

The answer is verified by the principles found within the PMBOK® Guide’s sections on Project Resource Management and Agile Practices, as well as the Professional in Business Analysis Reference Materials, which emphasize the importance of team development, knowledge transfer, and continuous improvement within project teams.

Comprehensive and Detailed Explanation:

Significant estimation discrepancies often indicate a lack of clarity. The story may be ambiguous or too broad. In agile practices, the team should ask the product owner to refine the story so it can be better understood and estimated with greater accuracy.

A (averaging) is not an agile practice.

C may be helpful but not sufficient in real time.

D is arbitrary and ignores team consensus.

B supports agile practices like backlog refinement.

Comprehensive and Detailed Explanation:

The project manager must educate stakeholders on the value of reserves for unknown risks. It’s essential to obtain buy-in, especially when the sponsor disagrees. Open communication and justification based on risk management principles are part of best practices.

* A is too confrontational.

* C bypasses the sponsor, which is inappropriate.

* D gives in without resolving the risk concern.

* B is the balanced, PMI-aligned approach.

During the initiation phase of a project, the project manager and the team define the project idea, including project goals, scope, and resources1. If a potential risk, such as low construction productivity, is identified during a lessons learned sharing session, it should be added to the risk register1. The risk register is a document where all details of the identified risks are recorded. The project manager should then develop a mitigation strategy for site execution. This strategy could include various actions to address the risk, such as improving processes, providing additional training, or hiring additional resources. The goal is to reduce the impact of the risk on the project’s objectives. References: Asana Resources | Project management, 4 Phases of the Project Management Lifecycle Explained | Coursera