The best course of action for a project manager who is experienced in both predictive and adaptive approaches, when dealing with stakeholders familiar mostly with predictive projects, is to first understand the scope complexity and project magnitude. This initial step is crucial as it helps in determining the most suitable approach for the project at hand. A hybrid approach may be beneficial in some cases, but without a clear understanding of the project’s demands and challenges, it’s premature to decide on the methodology. The project manager should assess the project’s needs, evaluate the stakeholders’ familiarity with different methodologies, and consider the potential need for training if an adaptive approach is chosen. This approach aligns with the PMI’s guidance on tailoring the project management approach to the unique aspects of the project and the environment in which it operates.

(Based on the PMI’s principles of tailoring the project management approach to the project’s characteristics and the stakeholders’ expertise.)

 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.

In situations where there is resistance to change, it is crucial to engage and gain support from the project sponsor. The sponsor can play a pivotal role in influencing and persuading the sales agents to commit to the change. This approach aligns with the best practices in change management which emphasize the importance of sponsorship in successful change initiatives12.

To ensure that project risks are reported accurately in the risk register, it is essential to review the risks throughout the project execution. This involves continuous monitoring and updating of the risk register to reflect new risks, changes in risk status, and the effectiveness of risk responses. Regular review allows the project manager to provide stakeholders with the most current information about project risks, which is crucial for informed decision-making and effective communication at the executive level123.

The approach aligns with best practices in risk management, which emphasize the importance of ongoing risk identification, analysis, and response planning as outlined in the PMBOK® Guide and other PMI standards123.

 In Agile project management, particularly within the Scrum framework, the Definition of Done (DoD) is a crucial checklist that ensures all necessary work on the product increment has been completed. By incorporating documentation into the DoD, the project team is required to update documentation consistently as part of their sprint deliverables. This approach ensures that documentation is treated with the same priority as other sprint tasks and is completed alongside the development of value-added features, rather than being postponed or overlooked.

= The importance of including documentation in the DoD is supported by Agile best practices, which emphasize the need for comprehensive and up-to-date documentation as part of the project deliverables12. Additionally, the Business Analysis Body of Knowledge (BABOK® Guide) highlights the significance of maintaining accurate and current documentation throughout the project lifecycle34.

 The project manager should engage with the functional managers to ensure that the team members’ work on the transformation project is recognized in their performance plans. This alignment is crucial for maintaining motivation and ensuring that the team members’ contributions to the project are acknowledged in their annual reviews. It’s important to align individual performance plans with the project’s objectives to ensure that all team members are working towards the same goals and that their efforts are evaluated appropriately.

According to the best practices in project management, when facing significant changes that impact project timelines, the project manager should first assess the situation with the project stakeholders. This involves analyzing the new circumstances, evaluating the potential impact on the project delivery, and exploring alternative solutions or adjustments to the project plan. Once a clear assessment is made, the project manager should then communicate the impact to the customer, providing them with the most accurate and updated information. This approach ensures that the customer is informed of the situation based on a thorough analysis and collaborative effort, rather than a hasty, unilateral decision by the project manager.

When external business influences cause changes in business parameters, the project manager should request an update of the project requirements to reflect these changes. This ensures that the project remains aligned with current business objectives and can deliver value as intended. It is a proactive approach that allows for the project to adapt to changing circumstances, which is a key aspect of effective project management. The PMBOK Guide emphasizes the importance of continuously monitoring and controlling project work to ensure that project objectives are met and that project work aligns with the business needs2.

 When a geographically distributed team faces challenges with verbal communication and collaboration due to new health protocols, it is essential to adapt the communication methods to ensure effective collaboration. Adding collaboration tools to the communications management plan can provide alternative ways to facilitate communication and collaboration. These tools can range from messaging apps, video conferencing, to project management software that supports asynchronous communication, allowing team members to collaborate effectively despite being in different locations or time zones. This approach aligns with the PMBOK® Guide’s emphasis on tailoring communication plans to project needs and the iterative nature of Agile project management, which encourages continuous improvement and adaptation123.

Communications management plan - Lovepmp1; Understanding the iterative process, with examples - Asana2; A Guide to Understanding the Iterative Process | The Workstream - Atlassian3.

Bridging communication gaps in a project team is essential for collaboration and project success. Networking sessions can help team members to get to know each other, build trust, and establish a foundation for effective communication. This aligns with the PMBOK® Guide’s emphasis on team development and stakeholder engagement as key aspects of project management. It also resonates with the PMI-PBA’s focus on collaboration within business analysis teams.

The answer is consistent with the principles found in the PMBOK® Guide and PMI-PBA guidelines, which advocate for activities that foster team building and stakeholder engagement to enhance project outcomes.

In situations where a key customer stakeholder is adding new tasks and pressuring for quick results, it’s important for the project manager to facilitate a collaborative approach. The project manager should encourage the customer to work directly with the product owner to prioritize requests. This ensures that the most important tasks are identified and addressed in a manner that aligns with the project’s goals and capacity. It also helps in managing the customer’s expectations by involving them in the decision-making process, which is a key aspect of stakeholder engagement in project management2. Additionally, this approach is in line with Agile principles, which emphasize customer collaboration over contract negotiation, suggesting that engaging customers in the development process is more beneficial than strictly adhering to contractual terms3. References:

Manage Stakeholder Engagement | Project Management Professional (PMP)1.

Planning effective stakeholder management strategies to do the same thing! - PMI2.

Agile explained: The 4 Agile Manifesto values and 12 principles3.

Gaining stakeholder buy-in for agile practices is crucial for the successful implementation of these methodologies. Organizing a meeting with relevant stakeholders to explain the benefits of agile and how the practices are relevant to the project is an effective way to engage them in the process. This approach allows for direct communication, clarification of potential doubts, and the opportunity to address specific concerns stakeholders may have. It also demonstrates the project manager’s commitment to transparency and collaboration, which are core values of agile methodologies. By involving stakeholders in this manner, they are more likely to understand and support the agile transformation.

The recommendation aligns with insights from the Project Management Institute, which emphasizes the importance of stakeholder engagement and communication in project success12. Furthermore, the Professional in Business Analysis (PMI-PBA) materials highlight the significance of stakeholder involvement in business analysis and the adoption of new practices34.

 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.

 When managing a project with team members from different continents, it’s crucial to understand their preferred methods of communication. This can help ensure that everyone is on the same page and that information is shared effectively across the team. The project manager should connect with each location to understand their communication preferences and then use this information to develop a communication plan for the project12. This approach can help to ensure successful project execution by promoting clear and effective communication across the team34. References: 

https://www.projectmanager.com/blog/project-execution

https://www.microsoft.com/en-us/microsoft-365/business-insights-ideas/resources/the-project-managers-guide-to-planning-a-perfect-project

 Being assigned a mentor offers several benefits for a junior project manager. Firstly, it creates a safe space for the junior project manager to discuss issues and challenges without fear of retribution, which is crucial for learning and development. Secondly, the mentor can share valuable past project documentation and experiences, including early warning indicators of potential problems. This knowledge transfer is essential for the junior project manager to anticipate and mitigate risks effectively.

 In situations where the project scope contains items that are well-defined and others that are complex and not fully understood, it is advisable to use a hybrid approach. The well-defined items can be managed using a predictive approach, which relies on a clear understanding of the scope, allowing for detailed planning and control. For the complex items, an agile approach is more suitable as it allows for iterative development, where the scope can be clarified and adjusted as more information is uncovered through progressive elaboration. This approach aligns with the PMBOK guide’s emphasis on tailoring the project management processes to the needs of the project, which may include varying degrees of uncertainty and complexity12.

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.

 When missing requirements specifications are identified during the design phase, the project manager should meet with the development team to review and assess the requirements. This collaborative approach ensures that all team members are aware of the discrepancies and can contribute to finding a solution. It is also aligned with the PMBOK® Guide’s emphasis on engaging stakeholders and maintaining open communication throughout the project lifecycle. By assessing the requirements with the team, the project manager can ensure that the project remains aligned with its objectives while addressing the gaps in the specifications.

 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

Addressing the issue of tardiness directly with the team member is a proactive approach that aligns with the principles of effective communication and individual respect outlined in the PMBOK® Guide. By speaking with the team member, the project manager can understand any underlying reasons for the lateness and work collaboratively to find a solution. This maintains the integrity of the standup meeting as a key communication tool within Agile methodologies and respects the time of all team members.

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

When faced with a defect and lacking the original engineering team’s expertise, the first step a project manager should take is to check the organizational process assets (OPAs). OPAs can include documentation from previous projects, such as historical information, lessons learned, and knowledge bases, which can provide insights or solutions to the defect. This approach aligns with the PMBOK® Guide’s emphasis on utilizing organizational knowledge repositories to enhance project outcomes.

= The PMBOK® Guide, which serves as a foundational reference for PMP objectives, supports the use of OPAs to address project challenges1. Additionally, the Professional in Business Analysis Reference Materials suggest leveraging existing documentation and knowledge to manage and rectify defects2.

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.

Recognizing and appreciating team members, especially those working remotely, is crucial for maintaining morale and motivation. Engaging directly with the remote team member, showing empathy, and expressing appreciation for their hard work can help address their concerns about recognition. This approach aligns with best practices in remote team management, which emphasize the importance of inclusion, empathy, and advocacy for remote workers. It ensures that all team members feel valued and recognized, which is essential for their satisfaction and the overall success of the project.

(Remote Support: Virtual Team Members Deserve Attention1, How to Recognize and Appreciate Remote Team Members2, Peer Recognition: A Key to Motivate Remote Teams3)

The PMBOK® Guide emphasizes the importance of clear and effective communication in project management. When a project manager notices that a client team member frequently halts progress due to misunderstandings, it is crucial to address the communication gaps. Updating the communications matrix to include this team member ensures that they receive all necessary information and understand their role and the project elements. This action aligns with the best practices for project communication management, which advocate for inclusive and comprehensive communication plans that cater to all project stakeholders12.

 The project manager should review the procurement contract to understand the terms and conditions related to quality and defects. Then, the project manager should engage in negotiations with the supplier to find a solution that is agreeable to both parties. This approach aligns with the PMBOK guide’s emphasis on procurement management, which includes the processes of planning, conducting, controlling, and closing procurements. It is important to manage procurements effectively to ensure that the project can meet its objectives while maintaining good relationships with suppliers.

 In a matrix organization, it is essential for the project manager to collaborate with the project team to resolve resource availability issues. This approach is supported by the PMBOK® Guide, which emphasizes the importance of team engagement and collective problem-solving in project management. By meeting with the project team, the project manager can explore various options, such as adjusting schedules, re-allocating resources, or finding alternative solutions to ensure that the necessary testing support is provided. This method aligns with the principles of stakeholder engagement and resource optimization1.

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.

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 faced with a decline in resource availability, the first action a project manager should take is to refer to the project’s resource management plan. This plan outlines the approach for how resources will be identified, acquired, and managed throughout the project. It provides guidance on how to address resource shortages and includes strategies for alternative solutions. By consulting the resource management plan, the project manager can assess the impact of the declined resources on the project schedule and scope, and determine the best course of action to reallocate resources or adjust project plans accordingly.

The response is based on the principles of resource management as described in the PMBOK guide, which includes processes for planning resource management, estimating activity resources, acquiring resources, developing the team, managing the team, and controlling resources1. Additionally, the importance of the resource management plan is highlighted as it serves as a guideline, roadmap, and reference for project managers to allocate, manage, and control the resources required to complete the project work2.

The PMBOK Guide and PMP objectives emphasize the importance of a proactive approach to project management, which includes focusing on recovery and corrective actions when faced with setbacks. When bad news is shared that impacts the project schedule, it is crucial for the project manager to maintain a positive outlook and lead the team towards finding solutions to get back on track. This involves analyzing the situation, understanding the implications, and working collaboratively with the team to develop a recovery plan. It is not productive to punish team members for sharing bad news, as this can create a negative atmosphere and discourage open communication. Instead, the project manager should encourage transparency and use the information to make informed decisions that steer the project towards success12.

 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 project manager should address the team member’s concerns by using a problem-solving approach, which involves identifying the root cause of the conflict, generating and evaluating alternative solutions, and implementing the best option. The project manager should set up a discussion with the team lead and the team member to facilitate open and honest communication, listen to both sides of the story, and help them reach a mutually acceptable resolution. This is consistent with the principle of leading with empathy and respect, which is part of the PMI Talent Triangle®. References:

PMBOK Guide 7th Edition, page 133

Agile Practice Guide, page 48

PMI Talent Triangle® 1

The project manager should perform a qualitative risk analysis to assess the probability and impact of the resource availability problem on the project objectives. The project manager should also identify the triggers and warning signs of the risk, and assign a risk rating or priority to the risk. This will help the project manager to determine the appropriate risk response strategy and plan accordingly. Updating the issue log may not be sufficient, as it does not address the uncertainty and potential impact of the risk. Performing a root cause analysis may not be necessary or feasible, as the resource availability problem may be beyond the project manager’s control or influence. Implementing a risk response plan may be premature, as the project manager should first analyze the risk before taking any action. References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 11: Risk, Section 11.3: Assess Risks

Professional in Business Analysis (PMI-PBA)® Handbook, Section 2.3: Domains and Tasks, Domain 5: Evaluation, Task 6: Assess Solution Limitations

Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain 5: Evaluation, Task 6: Assess Solution Limitations

 A self-organizing team is a team that has the authority and autonomy to decide how to perform their work, without being directed or controlled by external factors. A self-organizing team is able to adapt, collaborate, and innovate, and deliver value to the customer and the organization. According to the Professional in Business Analysis Reference Materials1, self-organizing teams are based on trust, collaboration, and empowerment of individuals.

In this scenario, a new team member is added to a self-organizing team, but the new team member is reluctant to speak and take part in team discussions or decisions. This could indicate that the new team member is not comfortable, confident, or familiar with the team culture, dynamics, or expectations. This could affect the team performance, cohesion, and satisfaction.

Therefore, the best two actions that the team should take to engage this new team member are:

Revisit the team’s discussion on team behaviors and norms: This action can help the new team member to understand the team values, principles, and rules that guide the team’s work and interactions. It can also help the team to clarify and align their expectations, roles, and responsibilities, and to address any issues or conflicts that may arise. By revisiting the team behaviors and norms, the team can create a shared vision and a sense of belonging for the new team member, and foster trust and respect among the team members.

Coach the new team member to improve engagement with the team: This action can help the new team member to develop the skills, knowledge, and confidence to participate and contribute to the team’s work and decisions. It can also help the new team member to receive feedback, support, and guidance from the team, and to learn from their experiences and best practices. By coaching the new team member, the team can empower and motivate the new team member, and enhance their performance and satisfaction.

The other options are not the best choices, because:

Report to the project manager about the new team member’s behavior: This action can undermine the autonomy and self-organization of the team, and create a dependency and a hierarchy that may conflict with the team culture and values. It can also damage the trust and relationship between the team and the new team member, and make the new team member feel isolated, judged, or rejected. Instead of reporting to the project manager, the team should try to resolve the issue internally, and involve the project manager only if necessary or requested.

Force the new team member to participate in activities that are considered easy: This action can demotivate and discourage the new team member, and make them feel undervalued, underestimated, or patronized. It can also prevent the new team member from developing their full potential and skills, and from delivering value to the team and the customer. Instead of forcing the new team member, the team should encourage and support the new team member, and assign them tasks that are challenging, meaningful, and aligned with their interests and abilities.

Facilitate an open discussion on all ideas and perspectives: This action can be helpful and beneficial for the team in general, but it may not be enough or appropriate for the new team member, who may not feel ready or willing to share their ideas and perspectives with the team. It may also put pressure or stress on the new team member, and make them feel overwhelmed or intimidated by the team’s expectations or opinions. Instead of facilitating an open discussion, the team should create a safe and supportive environment for the new team member, and respect their pace and preferences.

The project manager should address the issue between the two team members by scheduling a meeting with them and using conflict resolution techniques to find a mutually acceptable solution. This way, the project manager can prevent the issue from escalating and affecting the project performance and team morale. This approach is consistent with the agile principle of fostering collaboration and trust among the team members12. References: 1: PMBOK Guide, 6th Edition, Chapter 9: Project Resource Management 2: Agile Practice Guide, Chapter 2: An Agile Mindset

Organizational process assets (OPAs) are the collective knowledge and documented processes that an organization accumulates and utilizes to enhance its efficiency, performance, and decision-making capabilities. OPAs include policies and procedures, templates, historical data, lessons learned, and best practices. OPAs are important inputs for many project management processes and can help project managers and teams plan, execute, monitor, and control their projects. Therefore, it is essential for new team members to learn about the OPAs that are relevant to their project and role. The project manager should clarify the relevance of reviewing the documentation on the intranet and explain how OPAs can help the team member perform their tasks and contribute to the project success. Creating a training schedule, escalating the inquiry, or asking a senior team member to help are not the best options, as they do not address the root cause of the inquiry, which is the lack of understanding of the value of OPAs. References:

5, pages 38-39

6, pages 3-4

1, pages 2-3

2, pages 2-3

 According to the PMBOK Guide, 7th edition, section 13.1.1, “Stakeholder identification is the process of identifying the people, groups, or organizations that could impact or be impacted by a decision, activity, or outcome of the project, and analyzing and documenting relevant information regarding their interests, involvement, interdependencies, influence, and potential impact on project success.” Therefore, the project manager should conduct stakeholder identification and a project objectives review session, as this will help to ensure that the new key stakeholder is properly engaged and informed about the project scope and deliverables. Creating a change request and updating the scope management plan (option A) may not be necessary or appropriate, as the issue may not be related to the scope, but to the stakeholder’s expectations or understanding. Updating the stakeholder list and fixing the deliverables (option C) may not address the root cause of the issue, and may introduce unnecessary changes or rework. Updating the project management plan and lessons learned (option D) may be done later, after the issue is resolved and the stakeholder is satisfied. References:

PMBOK Guide, 7th edition, section 13.1.1

PMI-PBA Exam Practice Test and Study Guide, 2nd edition, page 180, question 14

The project manager should check with the agile teams to see if their understanding of the Agile Manifesto is correct because the Agile Manifesto values working software over comprehensive documentation. This means that agile teams should produce only the essential documentation that adds value to the project and the customer, and avoid unnecessary or excessive documentation that may slow down the delivery process or become outdated. The project manager should respect the agile teams’ autonomy and self-organization, and not impose any documentation requirements that are not aligned with the agile principles and practices. The project manager should also collaborate with the agile teams to understand their documentation needs and preferences, and support them in creating and maintaining the appropriate documentation for the project. References:

PMBOK® Guide, 6th edition, page 25, section 1.2.4

PMI-PBA Guide, 1st edition, page 14, section 1.3.3

[Agile Manifesto]

PMP Questions page 494, question 494

Free PMP Practice Exam Questions, question 2

PMP Project Management Professional Exam Study Guide, page 494, section 9.1

 In a hybrid project, the project manager is responsible for managing the expectations and requirements of all the stakeholders, both internal and external. The project manager also has the authority to approve or reject changes to the project scope, schedule, budget, and quality. Therefore, the team member should inform the stakeholder that the correct procedure for new requirements is to provide it directly to the project manager, who will then evaluate the impact of the change and decide whether to accept or reject it. This way, the team member can avoid being distracted from their work and maintain the productivity of the project. References:

Hybrid Project Management: What is it, Methodology & Software - Teamhood

What Is Stakeholder Management? - ProjectManager

A change request is a formal document that proposes a modification to some aspect of the project, such as the user requirements, the deliverables, the schedule, the budget, or the quality standards123. Change requests can originate from various sources, such as the stakeholders, the project team, the customer, or the environment12. Change requests need to be evaluated and approved before they can be implemented, as they may have significant impacts on the project performance, scope, cost, time, quality, and risk123.

The project scope statement is a document that defines and documents the project objectives, deliverables, requirements, assumptions, constraints, and acceptance criteria12. The project scope statement is the basis for making project decisions and controlling changes12. Therefore, the project manager should evaluate the change request against the project scope statement to determine if the change is necessary, feasible, and beneficial for the project123. The project manager should also consider the impact of the change on the other project components, such as the schedule, the budget, the quality, and the risk123.

The other options are not the best actions for the project manager to take next. Discussing approval of the change request in the next project meeting (A) may delay the decision-making process and cause confusion among the project team and stakeholders. Performing a risk assessment on the required change request (B) is an important step, but it should be done after evaluating the change request against the project scope statement, as the risk assessment may depend on the scope implications of the change. Asking the sponsor for more funds to cover the change request (D) is not appropriate, as the project manager should first determine if the change is justified and aligned with the project scope statement, and then explore alternative ways to accommodate the change within the existing budget or negotiate a trade-off with the sponsor. References: 123

According to the PMBOK® Guide, when a project manager faces a change request that affects the project scope, schedule, cost, or quality, they should first evaluate the impact of the change and then follow the change control process. The change control process involves reviewing the change request, analyzing the options, obtaining approval, and updating the project management plan and other documents. One of the options that the project manager can consider is to negotiate with the team and other stakeholders to find a feasible solution that can accommodate the change request without compromising the project objectives. This option requires effective communication, collaboration, and conflict resolution skills from the project manager and the team. Asking the team to accelerate the iterations and avoid interruptions (option A) is not a realistic or sustainable strategy, as it may lead to burnout, quality issues, and scope creep. Verifying team performance and asking for improvement during daily standup meetings (option C) is not a direct or proactive way to address the change request, as it may imply that the team is not performing well or that the project manager is micromanaging them. Recommending that the project sponsor increases the budget to bring new resources (option D) is not a viable option, as it may not be approved or feasible, and it may also introduce new risks and challenges to the project. References: PMBOK® Guide, 6th edition, pages 112-113, 135-136, 161-162.

According to the PMBOK Guide, 7th edition, one of the principles of project management is to support team performance. This means that the project manager should foster a collaborative project team environment, build team competencies, and address and remove impediments, obstacles, and blockers for the team. In this scenario, the project manager should provide appropriate training to the team members who lack the necessary skills or knowledge to perform their tasks, rather than emphasizing deadlines, updating the schedule, or accepting the risk. Providing training will help the team improve their performance, deliver value, and meet the expectations of the steering committee and other stakeholders. References: PMBOK Guide, 7th edition, page 9, Principle 8: Support team performance.

The project manager should have established ground rules for the team at the beginning of the project, which would include guidelines for communication, decision making, conflict resolution, and stakeholder engagement. Ground rules help the team to work effectively and collaboratively, and to avoid misunderstandings and disagreements. Providing copies of the stakeholder engagement plan (A) is not enough, as it does not specify how the team should interact with the stakeholders. Defining the roles and responsibilities of the team members (B) is also important, but it does not address the issue of who should attend the meeting with the local council authority. Updating the communications management plan © is not relevant, as it does not prevent the conflict from occurring in the first place. References: PMBOK Guide, 7th edition, page 91; Agile Practice Guide, page 14.

According to the PMBOK Guide, the project manager should develop the project management plan by integrating the subsidiary plans and baselines from the different knowledge areas. The project management plan defines how the project will be executed, monitored, controlled, and closed. However, before developing the project management plan, the project manager should first establish the project’s business value and scope, which are the key inputs for the project charter. The business case and scope document are two essential documents that provide the justification and description of the project, its objectives, deliverables, assumptions, constraints, and success criteria. By developing these documents first, the project manager can align the project with the organizational strategy, secure the project authorization, and guide the subsequent planning processes. References: PMBOK Guide, 6th edition, page 89-90, section 4.1 Develop Project Charter; page 95-96, section 4.2 Develop Project Management Plan.

When using an agile approach, the project manager should use a contract type that allows for flexibility and adaptation to changing requirements and priorities. A fixed-price contract with increments based on user stories is a suitable option, as it aligns the payment with the delivery of value to the customer. The other options are not appropriate for an agile project, as they either do not provide enough flexibility (A and B) or do not link the payment to the value delivered (D). References: PMBOK Guide, 6th edition, page 374; Agile Practice Guide, page 97.

 A change log is a document that contains the list of changes that are made during the project. It tracks the progress of each change based on its review, approval, implementation, and closure. A change log is a useful tool for communicating the status of change requests to the stakeholders, as it shows the impact and outcome of each change. A risk log, a backlog, and an issue log are different documents that serve different purposes. A risk log records the identified risks, their probability, impact, and response strategies. A backlog is a list of features or tasks that need to be completed in an agile project. An issue log records the issues that arise during the project, their causes, effects, and resolution. References:

Change Log - Project Management Knowledge

Change Log Template - Project Management Docs

Risks, issues, and changes–help, I’m drowning in logs!

The project manager should arrange a meeting with the functional managers of the two teams and try to reach an agreement that will resolve the conflict and enable the teams to complete their tasks. This is the best option because it addresses the issue directly, involves the parties who have the authority and responsibility to make decisions, and seeks a collaborative and constructive solution. The project manager should act as a facilitator and mediator in the meeting, and help the functional managers to identify the sources of the conflict, the interests and needs of each party, and the possible options for agreement. The project manager should also ensure that the meeting is conducted in a respectful and professional manner, and that the outcome is documented and communicated to the relevant stakeholders. References:

People in Projects, Chapter 13, Section 5: Project Manager/Functional Manager Conflict

A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Chapter 13, Section 4.2.3: Conflict Management

7 Big Project Management Conflicts & Ways to Solve Them All, Section 2: Conflicting Interests of Stakeholders