In hybrid project management, when is it most appropriate to use a predictive (waterfall) approach for a portion of the project?

Correct answer: When the scope is well-defined and unlikely to change

Option D is correct because in hybrid project management, the predictive or waterfall approach is most appropriate when the scope, requirements, and deliverables are well-defined and stable, allowing detailed upfront planning and sequential phase execution without the need for iterative adjustments. Option A is incorrect because frequent deliverables and stakeholder feedback cycles are characteristics that suit an agile or iterative approach rather than a predictive one, where deliverables are typically produced at the end of long phases. Option B is incorrect because cross-functional and self-organizing teams are a hallmark of agile frameworks like Scrum, which thrive on flexibility and collaboration, not the structured and role-defined nature of waterfall. Option C is incorrect because unclear and evolving requirements are precisely the conditions under which predictive approaches fail and agile approaches excel, since waterfall depends on stable requirements captured upfront.