64. The reorganization of a company's department results in a key worker being reassigned to a higher priority project. At the same time, a new requirement that will increase the project's value may cause a delay to the release schedule. What should the project manager do next?

Answer: C

Explanation:

Propose to launch the product as it is and then add the new requirement in another iteration.

In this situation, the project manager should propose to launch the product as it currently stands and plan to incorporate the new requirement in a future iteration. This approach allows the team to meet the original release schedule while still addressing the valuable new requirement later.

A) Prioritize the backlog so requirements can be completed without a schedule impact

Prioritizing the backlog may seem beneficial, but it would likely lead to an increased workload and potential delays in the project's timeline. Given that a key worker is reassigned, it may not be feasible to complete all requirements without impacting the schedule.

B) Schedule the new requirement implementation for when the key worker is available again

Scheduling the new requirement for when the key worker is available may delay the project unnecessarily. This option does not address the immediate need to release the product on time and could lead to missed market opportunities.

C) Propose to launch the product as it is and then add the new requirement in another iteration

This option is correct as it allows for the timely release of the product while still planning for future enhancements. By focusing on launching the current product, the project manager can ensure that the team meets deadlines and can later improve the product based on user feedback.

D) Discuss the issues with the product owner to obtain more resources and complete the project

While discussing issues with the product owner is important, obtaining more resources may not be a practical or immediate solution. This approach may also lead to further delays as the project manager waits for additional resources instead of moving forward with the current project status.

Conclusion

The best course of action in this scenario is to propose launching the product as it is and incorporating the new requirement in a subsequent iteration. This strategy ensures that the project stays on schedule while still allowing for the integration of valuable enhancements later. All other options either risk delaying the project or do not effectively utilize the current resources available.