Where should you start with your DevOps evolution?

The correct answer is D because DevOps evolution should begin with a value stream. DevOps is concerned with the end-to-end flow of work from idea to customer value, not merely with reorganizing departments, selecting a single application, or avoiding legacy systems. A value stream view allows leaders and teams to understand how work actually moves through the organization, where delays occur, where handoffs create friction, and where feedback is lost.

Starting with a reorganization is risky because structural change without understanding the system of work may simply recreate the same constraints in a new chart. Starting with an application can be too narrow unless it is examined within the broader value stream that delivers and operates it. Avoiding legacy systems is also not a reliable principle; legacy services may be central to business value and therefore important to include.

A value stream approach helps identify constraints, reduce waste, improve flow, and connect technical improvements to business outcomes. It also gives leaders a practical basis for measurement and improvement. Relevant study guide references: Becoming a DevOps Organization; Measuring to Improve; Measuring to Learn; Target Operating Models and Organizational Designs.