To stay ahead of its competition, an organization's leadership team is focused on ensuring that product innovations reach customers quickly. A team is discussing how it can leverage value stream…

Question

Options

• AReducing the time spent assessing and approving changes
• BDesigning a continuous integration/continuous delivery pipeline
• CReducing the time it takes to provide environments for projects
• DMinimizing handoffs between specialists within a development team

• A
  7% (2)
• B
  86% (24)
• C
  4% (1)
• D
  4% (1)

Explanation

Designing a CI/CD pipeline (B) addresses the entire end-to-end value stream because it automates and integrates every stage from code commit through testing, deployment, and delivery to customers - removing bottlenecks across the full flow rather than optimizing one isolated step.

• A is wrong because reducing change approval time targets only the governance/release gate stage, improving just one handoff point without affecting development, testing, or deployment flows.
• C is wrong because faster environment provisioning helps project setup speed but only impacts one phase of the pipeline, leaving the rest of the value stream untouched.
• D is wrong because minimizing handoffs within a development team narrows the scope to internal team dynamics - valuable, but it doesn't span the full end-to-end stream from idea to customer.

Memory tip: Think "end-to-end = CI/CD." The keyword entire value stream is your signal to pick the answer that spans all stages - CI/CD pipelines are the structural backbone connecting every stage from code to customer, making them the only choice that's holistically transformative rather than locally optimized.

No community discussion yet for this question.