Explanation:
In a hybrid project, the project manager needs to balance the different approaches and expectations of the stakeholders and the teams. The customer’s change request may have been approved based on the assumption that the software team can deliver the software in a timely manner using an agile approach. However, the software team leader’s refusal to commit to a delivery date indicates a lack of alignment and collaboration between the teams and the customer. This creates a risk of schedule and scope deviations, as well as potential conflicts and dissatisfaction among the stakeholders. Therefore, the project manager should add this risk to the risk register and monitor it according to the risk management plan. The project manager should also communicate with the software team leader and the customer to clarify the expectations and the rationale behind the change request, and to explore possible ways to mitigate the risk and deliver the software that meets the customer’s needs and the hardware team’s dependencies. The project manager should not escalate the issue to higher management without trying to resolve it first, as this may undermine the trust and autonomy of the teams. The project manager should not impose the delivery dates on the software team leader, as this may violate the agile principles and demotivate the team. The project manager should not ask the software team leader to use a predictive approach, as this may not be feasible or suitable for the software development process and the customer’s requirements.
References: (Professional in Business Analysis Reference Materials source and documents)
- PMBOK® Guide, 6th edition, Section 1.2.4, p. 19
- PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain III: Analysis, Task 5, p. 11
- Business Analysis for Practitioners: A Practice Guide, Section 2.4.2, p. 36
Explanation
According to the PMP Exam Content Outline (2023), one of the tasks under the domain of Planning is to “Develop the procurement management plan based on the project scope, budget, and schedule, in order to ensure that the required project resources will be available” 1. This task involves identifying potential sellers, conducting market research, determining the contract type, and defining the procurement strategy and approach. One of the tools and techniques for this task is “Contract terms and conditions”, which are the legal provisions that govern the rights and obligations of the parties involved in the procurement 2. Penalty clauses are a type of contract terms and conditions that specify the amount of money or other compensation that a party will pay or forfeit in the event of a breach of contract, such as failing to meet the deliverable dates 3. Penalty clauses can be used to motivate the seller to perform according to the contract and to protect the buyer from losses or damages caused by the seller’s poor performance.
According to the PMI-PBA Exam Content Outline (2023), one of the tasks under the domain of Analysis is to “Assess risks that may impact the solution scope or requirements, and document them in the risk register” . This task involves identifying, analyzing, prioritizing, and documenting the risks that may affect the solution or its delivery, and planning the appropriate responses to mitigate or avoid them . One of the tools and techniques for this task is “Risk register”, which is a document that records the details of the identified risks, their causes, impacts, probabilities, priorities, responses, owners, and status . The risk register is a living document that is updated throughout the project as new risks are identified, existing risks are monitored, and risk responses are implemented.
Therefore, the best answer to this question is B. Add penalty clauses to the contract and update the risk register. This answer reflects the project manager’s responsibility to plan the procurement management and the risk management for the project, and to use appropriate tools and techniques to ensure that the project objectives are met. The other answers are not as good because they either do not address the issue of the provider’s poor performance (A and C), or they introduce a new risk by contracting another provider with less experience (D).
Explanation
The project manager should compare the achieved results to the contract requirements before obtaining financial, legal, and administrative approval to close the project and transfer the liability. This is because the project manager needs to ensure that the supplier has fulfilled all the contractual obligations and delivered the agreed scope, quality, and performance standards. The project manager should also verify that the supplier has completed all the required documentation, testing, training, and warranty services. The project manager should also review the lessons learned, feedback, and satisfaction surveys from the supplier and the project team. This will help the project manager evaluate the supplier’s performance, identify any issues or disputes, and resolve them before making the final payment and closing the project. The project manager should also communicate with the supplier and the relevant stakeholders about the project closure and the transfer of liability.
According to the PMBOK Guide, a sprint cycle is a time-boxed iteration of a fixed duration that delivers a potentially releasable product increment. A sprint cycle consists of four events: sprint planning, daily scrum, sprint review, and sprint retrospective. The purpose of a sprint cycle is to create a rhythm of work that allows the team to deliver value to the customer in a predictable and sustainable way.
The PMI Guide to Business Analysis states that one of the roles of a project manager is to manage stakeholder expectations and ensure alignment of project objectives with business needs. The project manager is also responsible for facilitating communication and collaboration among the project team and other stakeholders, as well as resolving conflicts and issues that may arise during the project.
Therefore, if the project sponsor is consistently changing the prioritization of modular work packages, the project manager should set up a meeting with the sponsor to explain the importance of keeping a strict sprint cycle. The project manager should:
Clarify the project scope and objectives, and how they are aligned with the business needs and the sponsor’s vision.
Explain the benefits of a sprint cycle, such as delivering value faster, improving quality, increasing feedback, and reducing risk.
Highlight the challenges and risks of changing the scope frequently, such as disrupting the team’s workflow, reducing their morale and motivation, increasing technical debt, and compromising the quality and usability of the product.
Negotiate with the sponsor to establish a clear and stable prioritization criteria for the work packages, and agree on a process for managing changes and requests.
Involve the project team and the product owner in the prioritization and planning process, and ensure their input and feedback are considered and valued.
Document and communicate the agreed scope, priorities, and changes to all the stakeholders, and monitor and control the project performance and progress.
By setting up a meeting with the sponsor to explain the importance of keeping a strict sprint cycle, the project manager can:
Build trust and rapport with the sponsor, and demonstrate their understanding and respect for the sponsor’s perspective and needs.
Educate the sponsor about the agile principles and practices, and how they can help achieve the project goals and deliver value to the customer.
Influence the sponsor to adopt a more collaborative and flexible approach to the project, and to respect the team’s autonomy and expertise.
Minimize the impact of scope changes on the project schedule, budget, quality, and risk.
Enhance the team’s morale and teamwork, and foster a positive and supportive work environment.
References:
PMBOK Guide. (2017). Sixth edition. Newtown Square, PA: Project Management Institute.
PMI Guide to Business Analysis. (2017). Newtown Square, PA: Project Management Institute.
How to Manage Scope Creep in Agile Projects. (2023). ProjectManager.com.
How to Deal with Constantly Changing Requirements. (2023). Scrum.org.