What is a common characteristic of Agile projects?

Frequent delivery of working software is a hallmark of Agile projects. This principle is rooted in the Agile Manifesto, which emphasizes delivering functional software in short cycles, enabling teams to respond to changing requirements and customer feedback effectively. Agile methodologies, such as Scrum, often involve iterations or sprints during which a usable product increment is developed, reviewed, and adjusted based on stakeholder input. This approach not only enhances customer satisfaction by providing ongoing value but also allows teams to identify and address issues early in the development process, fostering a more dynamic and adaptive workflow.

The other options present characteristics that contradict Agile principles. Fixed scope and requirements are contrary to Agile's adaptable nature, as Agile processes are designed to accommodate changes throughout the project lifecycle. Rigid team structures do not align with Agile's emphasis on collaborative and cross-functional teams that adapt fluidly to changing project needs. Extended development phases also conflict with Agile, which typically favors shorter iterations to ensure timely delivery and continuous improvement.