The correct answer is B because successful DevOps transformation begins by understanding the value stream. DevOps is not primarily a tooling program, a developer-led takeover of operations, or an isolated grassroots movement. It is an organizational evolution focused on improving the flow of value from idea to customer outcome while increasing quality, reliability, feedback, and learning.
A value stream mapping exercise provides the shared visibility required to start that evolution intelligently. It shows how work actually moves through the organization, where delays occur, where handoffs exist, where rework is created, where approvals slow flow, and where constraints limit delivery. Without this view, organizations often automate the wrong process, reorganize around assumptions, or invest in tools that do not address the real bottleneck.
Tools may become important later, and grassroots energy can help sustain change, but neither replaces the need for a clear view of the end-to-end system. Value stream mapping creates the factual baseline for improvement and alignment. Relevant study guide references: Becoming a DevOps Organization; Measuring to Improve; Measuring to Learn; Target Operating Models and Organizational Designs.
==============
