CISA · Question #621
When developing software with incomplete requirements, the MOST appropriate methodology to use is:
The correct answer is C. Agile. Agile is purpose-built for environments where requirements are incomplete, evolving, or poorly understood at project start. It delivers working software in short iterative sprints, gathering continuous feedback from stakeholders and refining requirements incrementally. Extreme…
Question
When developing software with incomplete requirements, the MOST appropriate methodology to use is:
Options
- Aextreme programming.
- Brapid application development.
- CAgile.
- DDevSecOps.
How the community answered
(24 responses)- A4% (1)
- B4% (1)
- C83% (20)
- D8% (2)
Explanation
Agile is purpose-built for environments where requirements are incomplete, evolving, or poorly understood at project start. It delivers working software in short iterative sprints, gathering continuous feedback from stakeholders and refining requirements incrementally. Extreme Programming (A) is a specific agile variant focused on engineering practices but is narrower in scope. Rapid Application Development (B) accelerates delivery but still typically requires reasonably complete requirements upfront. DevSecOps (D) integrates security into the development pipeline but is a cultural and operational practice, not a methodology for managing incomplete requirements. Agile's iterative, feedback-driven nature makes it the best fit when requirements cannot be fully defined in advance.
Topics
Community Discussion
No community discussion yet for this question.