CAS-001 · Question #450
A mature organization with legacy information systems has incorporated numerous new processes and dependencies to manage security as its networks and infrastructure are modernized. The Chief…
The correct answer is A. Agile. The key indicators in the scenario point to Agile: (1) 'frequent releases' - Agile delivers working software in short iterative sprints rather than one large release; (2) 'constant communication with personnel and groups within the organization' - Agile emphasizes continuous…
Question
A mature organization with legacy information systems has incorporated numerous new processes and dependencies to manage security as its networks and infrastructure are modernized. The Chief Information Office has become increasingly frustrated with frequent releases, stating that the organization needs everything to work completely, and the vendor should already have those desires built into the software product. The vendor has been in constant communication with personnel and groups within the organization to understand its business process and capture new software requirements from users. Which of the following methods of software development is this organization's configuration management process using?
Options
- AAgile
- BSDL
- CWaterfall
- DJoint application development
How the community answered
(52 responses)- A71% (37)
- B17% (9)
- C4% (2)
- D8% (4)
Explanation
The key indicators in the scenario point to Agile: (1) 'frequent releases' - Agile delivers working software in short iterative sprints rather than one large release; (2) 'constant communication with personnel and groups within the organization' - Agile emphasizes continuous stakeholder collaboration over rigid contracts; (3) 'capture new software requirements from users' throughout the process - Agile embraces changing requirements even late in development. The CIO's frustration that the vendor should have everything 'built in completely' is a classic organizational tension with Agile's iterative approach. Waterfall (C) would deliver everything in one complete release with requirements locked upfront. SDL (B) is a security-focused process, not a delivery methodology. Joint Application Development (D) is a requirements-gathering technique, not a full SDLC methodology.
Topics
Community Discussion
No community discussion yet for this question.