In a hybrid project, the customer decided on a major change for the project design. This change was approved and the impact on schedule and budget is known.
The software team leader, who is supposed to develop the software, refuses to commit to delivery dates claiming that they work using an agile approach and cannot commit to a final delivery date. The hardware team depends on this software to develop their part of the product.
What should the project manager do?
In a hybrid project where different teams follow different methodologies, managing risks associated with potential delays becomes a priority. Adding the issue to the risk register and monitoring it according to the risk management plan is a systematic approach to proactively track and address the software team's potential challenges in meeting delivery dates. This ensures that the impacts are identified and mitigated in a controlled manner, while also respecting the agile methodology used by the software team.
A is not the answer. FIrst of all the question says that the impact on schedule and budget is known, which means it has already been recorded in the risk register. Second, adding it to the risk register does not help the hardware team in any way. Adding to the risk register is not a solution for the hardware team and does not guarantee a timely delivery. With changing the development approach, the software lead will need to commit a date and then you can add it to the risk register to monitor it closely to ensure the software is delivered without any delay. The correct answer is D
Hybrid project. Software is Agile, Hardware is Predictive. So the best answer is add to risk register. Since hardware is predictive, we know how long it takes for development. If Software team can't be delivered in-time for the the Hardware, then it become a risk.
Why can't the answer be D? Can someone explain? @guyver0523 - Does this question come in the exam and have you passed?
Gonna go with A. Nowhere in this question does it say that scope is known, which is what you would need for a predictive approach (which are also pretty rare in software development). There's also the fact that it sounds like the PM plan has been approved, as well as schedules, so the dev has their orders already, the only option you have here is to monitor it as a risk.
I choose A. Even PM asks the software team leader to use a predictive approach, it's not a small change. It needs to get an approval from CCB.
I choose C. The change was approved and the impact on schedule and budget is already known, which would have been used to determine the delivery date. The software team leader can continue to use agile, but they need to prioritize it to meet the deadline.
Before major change for the project design, project used hybrid approach. However, after approving major change, might project scope becomes clear (impact on schedule and budget is known) and hardware team depend on software so need to change the Hybrid to Predictive approach.
A is correct
I change my answer. I will go with A
Go with A
Will go with A as well
Option C, which involves facilitating a conversation and finding a compromise, is likely a better approach in this situation to ensure collaboration and address the dependencies while still respecting the team's chosen methodology. Here they can continue with Agile approach, but only constraint is the time imposed on them. This is necessary as there is a dependency.
Never impose C not correct A. Add this risk to the risk register and monitor it according to the risk management plan
A. Add this risk to the risk register and monitor it according to the risk management plan. In a hybrid project where different teams or components are using different methodologies (in this case, agile for software development), it's essential to acknowledge and manage the potential risks associated with these differences. By adding this risk to the risk register and monitoring it according to the risk management plan, the project manager can proactively track and address the software team's potential challenges in meeting delivery dates. This allows for a more systematic approach to risk management and can help identify potential solutions or mitigations if needed.
The change is known and approved, yet the development team is refusing to comply. The only correct response is to escalate this issue. Simply adding it as a risk item is useless as its not a potential risk anymore, its already an issue now.
Answer should be option A. Option D can never be a PM mindset of a servant leader.