Rolling wave planning is a project planning technique that allows the project manager to plan and execute the project in short iterations, based on the available information and the level of detail required12. Rolling wave planning is suitable for projects that have a high degree of uncertainty, complexity, or change, such as a component development project13. Rolling wave planning can help the project manager to accelerate the deliverable by enabling the following benefits123:
It reduces the risk of rework and waste by allowing the project manager to adjust the plan as more information becomes available or as the requirements change.
It increases the flexibility and responsiveness of the project team by allowing them to focus on the most important and urgent tasks in each iteration, rather than following a rigid and detailed plan.
It improves the quality and customer satisfaction of the deliverable by allowing the project manager to incorporate feedback and lessons learned from each iteration into the next one, and by delivering incremental value to the customer.
It enhances the collaboration and communication among the project team and stakeholders by involving them in the planning and execution of each iteration, and by providing frequent and transparent updates on the project progress and status.
The other options are not the best techniques to accelerate the deliverable in this scenario. Impact mapping (A) is a strategic planning technique that helps the project manager to align the project deliverables with the organizational goals and the customer needs, by identifying the actors, impacts, and deliverables involved45. However, impact mapping does not address the issue of how to plan and execute the project in a fast and adaptive way, especially when the project has failed to comply with a product functionality. Collective code ownership © is a software development practice that encourages the entire team to share the responsibility and the authority to modify any code file as necessary, to improve the quality, the performance, and the functionality of the software product67. However, collective code ownership does not address the issue of how to plan and execute the project in a fast and adaptive way, especially when the project has a predominantly predictive approach. Scrum of Scrums (D) is a scaling technique that helps multiple Scrum teams to coordinate and collaborate on complex and interdependent projects, by having representatives from each team meet regularly to report on their progress, their impediments, and their dependencies89. However, Scrum of Scrums does not address the issue of how to plan and execute the project in a fast and adaptive way, especially when the project has a predominantly predictive approach. References: https://www.teamgantt.com/waterfall-agile-guide/hybrid-approach
https://www.float.com/resources/hybrid-project-management/
https://en.wikipedia.org/wiki/Rolling-wave_planning
