SY0-501 · Question #392
A software development manager is taking over an existing software development project. The team currently suffers from poor communication due to a long delay between requirements documentation and fe
The correct answer is B. Waterfall. The team's long delay between requirements and delivery, along with poor communication, are hallmark characteristics of the Waterfall methodology, which follows a rigid sequential process.
Question
A software development manager is taking over an existing software development project. The team currently suffers from poor communication due to a long delay between requirements documentation and feature delivery. This gap is resulting in an above average number of security-related bugs making it into production. Which of the following development methodologies is the team MOST likely using now?
Options
- AAgile
- BWaterfall
- CScrum
- DSpiral
How the community answered
(24 responses)- A4% (1)
- B83% (20)
- C4% (1)
- D8% (2)
Why each option
The team's long delay between requirements and delivery, along with poor communication, are hallmark characteristics of the Waterfall methodology, which follows a rigid sequential process.
Agile emphasizes iterative development with short cycles and continuous stakeholder collaboration, which reduces the gap between requirements and delivery rather than creating a long delay.
Waterfall is a linear, sequential development methodology where each phase (requirements, design, implementation, testing, deployment) must be completed before the next begins. This creates a significant time gap between when requirements are documented and when features are delivered, limiting feedback loops and making it difficult to catch security issues early, resulting in more bugs reaching production.
Scrum is an Agile framework that uses short sprints (typically 2-4 weeks) with frequent reviews and retrospectives, promoting rapid delivery and continuous communication that would minimize the described gap.
Spiral is a risk-driven iterative model that revisits planning and risk analysis in each cycle, which inherently addresses security concerns more proactively than the described scenario suggests.
Concept tested: Software development methodology characteristics and security implications
Source: https://csrc.nist.gov/publications/detail/sp/800-64/rev-2/final
Topics
Community Discussion
No community discussion yet for this question.