volume_mute
Five Principles of Agile Methods
publish date: 2026/06/04 20:56:20.059872 UTC
volume_muteThe five principles of agile methods are: Customer involvement, Incremental delivery, People not process, Embrace change, and Maintain simplicity. Match each principle to its correct description.
To complete the line match
- Click on an item in the first group
- Click on the match in the second group
To delete a match, double click on a line
Principle
Customer involvement
People not process
Embrace change
Maintain simplicity
Description
Customers should be closely involved throughout the development process to provide and prioritise new requirements and to evaluate iterations
The skills of the development team should be recognised and exploited — team members should be left to develop their own ways of working without prescriptive processes
Expect the system requirements to change and design the system so that it can accommodate these changes
Focus on simplicity in both the software being developed and the development process — actively work to eliminate complexity from the system
Correct Answer
(1) Customer involvement,Customers should be closely involved throughout the development process to provide and prioritise new requirements and to evaluate iterations
(2) People not process,The skills of the development team should be recognised and exploited — team members should be left to develop their own ways of working without prescriptive processes
(3) Embrace change,Expect the system requirements to change and design the system so that it can accommodate these changes
(4) Maintain simplicity,Focus on simplicity in both the software being developed and the development process — actively work to eliminate complexity from the system
Explanation
Customer involvement: provide and prioritise requirements, evaluate iterations. People not process: recognise team skills, let members develop their own working methods. Embrace change: expect and design for requirements change. Maintain simplicity: actively eliminate complexity from both software and process.
Reference
Software Engineering, Ian Sommerville, 9th edition