In short
Agile development builds software in short cycles (sprints) that each deliver working features, with continuous feedback from users. The traditional waterfall approach completes each phase in sequence before starting the next.
Key takeaways
- Agile adapts more easily to changing requirements; waterfall suits stable, well-defined requirements.
- Change management, testing and segregation of duties still apply, often as automated controls in the deployment pipeline.
- Documentation tends to be lighter, which auditors need to plan for.
Where it's tested
ISC: Systems Development & Change Management — study notes, a five-minute revision sheet and practice questions.
Practise: 3 questions
Question 1 of 3 · 0 answered
Which statement best describes an agile development approach compared with waterfall?