| 1/2 | 8 | ||||||||||||||||||||
| 3 | 9 | ||||||||||||||||||||
| 7 | |||||||||||||||||||||
| 4/5 | |||||||||||||||||||||
| 6 | |||||||||||||||||||||
1. A development approach that involves repeating a process or set of activities in cycles or iterations.
2. A software development process where a subset of the software is developed and released, with subsequent iterations adding more features and improving quality based on user feedback.
3. Working together with stakeholders, team members, and other parties involved in the software development process to achieve common goals.
4. A development approach where the software product is delivered in small, manageable increments or iterations rather than all at once.
5. A software development approach where the project is divided into smaller parts, with each part delivered and tested in stages, adding new functionality with each iteration.
6. A software development model in which progress is seen as flowing steadily downwards through the phases of conception, initiation, analysis, design, construction, testing, production/implementation, and maintenance.
7. An iterative software development approach that emphasizes risk management through multiple cycles of development
8. A software development methodology that prioritizes flexibility, collaboration, and customer feedback through iterative and incremental development.
9. The ability of a development team or project to adjust to changes in requirements, technology, or other factors during the software development lifecycle.