What is a sign of an organization that has adopted a shift-left concept of code release cycles?

Question

Options

• AA waterfall model to move resources through the development to release phases
• BIncorporation of automation to identify and address software code problems early
• CMaturity of start-up entities with high-iteration to low-volume code commits
• DLarge entities with slower release cadences and geographical dispersed systems

• A
  4% (2)
• B
  94% (47)
• D
  2% (1)

Explanation

Shift-left is the practice of moving testing, security, and quality assurance activities earlier (to the 'left') in the software development lifecycle, rather than treating them as end-stage gates. The defining characteristic is catching problems early through continuous, automated checks - such as static code analysis, automated unit/integration tests, and security scanning integrated directly into CI/CD pipelines. Option A (waterfall model) is the opposite: a sequential, late-stage approach with no feedback loops. Options C and D describe organizational maturity profiles, not shift-left practices. Only B - automation to identify and address code problems early - directly describes the shift-left philosophy.

No community discussion yet for this question.