The correct answer is B because a value stream map is a strong technique for creating a shared view of why change is needed. Before a DevOps transformation can gain momentum, stakeholders must understand the current system of work: how demand enters, how work flows, where it waits, where it is handed off, where rework occurs, and where customer value is delayed. A value stream map makes these issues visible to everyone involved.

This shared visibility is important because transformation often fails when different teams hold different mental models of the problem. Development may see operations as a blocker, operations may see development as careless, and leadership may see only high-level delivery metrics. Value stream mapping helps replace assumptions and blame with a common evidence base. It allows stakeholders to see that many problems are systemic rather than caused by individual teams.

Kanban can help manage and visualize work, but the question asks about creating a shared vision of the need to change. Reengineering is broader and more disruptive. A change score card may track change but does not create the same end-to-end understanding. Relevant study guide references: Articulating and Socializing Vision; Measuring to Learn; Measuring to Improve; Becoming a DevOps Organization.