Why does your DevOps process need feedback loops?

What do feedback loops mean in the software development lifecycle?
Feedback loops are the process in which a change or output from one part of the software delivery value stream triggers a resulting action in another part of the value stream. For example, when a defect is logged during testing, it triggers a resulting change to the code in development.
Simply put, feedback loops are essentially an internal review of how the DevOps teams, systems, and users function.
Read more about the various types of feedback loops here.

I want to learn how to accelerate software delivery by understanding feedback loops.

Show me an example!


What are the objectives of the feedback loop?

The three primary objectives of this system are to:
  • Create a loop between the technology (development, testing, ops) and business (customer support, sales) teams in your software delivery value stream
  • Accelerate software delivery without compromising on the quality
  • Bridge the gap between your software function and customers’ expectations