Which of the following is a valid difference between Agile and traditional technology teams

Approach to Project Management: Traditional technology teams often use a Waterfall model, where the project is divided into sequential phases, with each phase depending on the deliverables of the previous one. Agile teams, on the other hand, use an iterative approach, where the project is divided into small parts called "sprints". Each sprint is a complete project cycle in itself, including planning, design, coding, testing, and documentation.

Flexibility: Agile teams are more flexible and can adapt to changes more quickly. They can change direction based on customer feedback or market trends. Traditional teams, on the other hand, follow a set plan and changes can be difficult and costly to implement.

Customer Involvement: In Agile teams, customers are involved throughout the development process. They provide feedback and suggestions, which are incorporated in the next sprint. In traditional teams, customers are usually involved only at the beginning (during requirements gathering) and at the end (during product delivery).

Risk Management: Agile methodology helps in mitigating risks as it allows for early detection of issues or challenges, thanks to its iterative nature. In traditional teams, risks are usually identified during the testing phase, which is typically towards the end of the project.

Documentation: Traditional teams often require heavy documentation as each phase needs to be clearly defined and approved before moving on to the next. Agile teams, on the other hand, value working software over comprehensive documentation. They aim to minimize paperwork and focus more on delivering a working product.