The correct answer is D - Features should be prioritized and then teams should be organized around those priorities. In agile scaling and reorganization, forming feature teams allows for the creation of cross- functional, end-to-end value delivery units. This reduces dependencies and promotes customer-focused outcomes.
From the PMI Agile Practice Guide:
"Teams are best organized around delivering customer value. When scaling or merging efforts, restructuring around features or customer priorities improves flow, minimizes handoffs, and supports agility at scale." (PMI Agile Practice Guide, Section 5.5 - Agile Scaling Considerations) Mike Griffiths notes:
"Agile scaling favors organizing teams around features and capabilities rather than components. Feature teams are cross-functional and able to deliver end-to-end slices of functionality with minimal dependencies." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 - Scaling Agile and Team Formation) Incorrect options:
* A can lead to chaos without structure.
* B reinforces siloed, component-based teams which increase integration risk.
* C recreates functional silos rather than cross-functional teams.