Problems with Agile Principles in Practice

(1) Customer involvement depends on having a customer who is willing and able to spend time with the development team and can represent all stakeholders — this is often not possible

(2) Individual team members may not have suitable personalities for the intense involvement typical of agile methods

(3) Prioritising changes can be extremely difficult when there are many stakeholders who give different priorities to different changes

(4) Maintaining simplicity requires extra work and delivery pressure may prevent simplification

Explanation

Four practical difficulties: (1) customer availability — customers may not be able to represent all stakeholders or spend enough time; (2) team personality — not all members suit intense agile involvement; (3) change prioritisation — very difficult with many stakeholders; (4) simplicity overhead — requires extra work that delivery pressure may not permit. Lower code quality is not a stated consequence of agile methods.