{"id":48525,"date":"2022-08-09T11:38:54","date_gmt":"2022-08-09T15:38:54","guid":{"rendered":"https:\/\/sdtimes.com\/?p=48525"},"modified":"2022-08-10T10:51:26","modified_gmt":"2022-08-10T14:51:26","slug":"devops-feedback-loop-explained-weak-feedback","status":"publish","type":"post","link":"https:\/\/sdtimes.com\/devops\/devops-feedback-loop-explained-weak-feedback\/","title":{"rendered":"DevOps Feedback Loop Explained: Weak Feedback"},"content":{"rendered":"

Feedback is routinely requested and occasionally considered. Using feedback and doing something with it is nowhere near as routine, unfortunately. Perhaps this has been due to a lack of a practical application based on a focused understanding of feedback loops, and how to leverage them. We\u2019ll look at Feedback Loops, the purposeful design of a system or process to effectively gather and enable data-driven decisions; and behavior based on the feedback collected. We\u2019ll also look at some potential issues and explore various countermeasures to address things like delayed feedback, noisy feedback, cascading feedback, and weak feedback. To do this, in this four-part series<\/a> we\u2019ll follow newly onboarded associate Alice through her experience with this new organization which needs to accelerate organizational value creation and delivery processes.<\/span><\/i><\/p>\n

Our previous stories<\/a><\/span> were devoted to the delayed<\/a>, noisy<\/a> and cascaded<\/a> feedback loops, and today we will shed light on what the weak feedback means.<\/span><\/p>\n

As you might remember from those previous articles, “Alice” joined a company, working on a digital product to accelerate delivery. The engineering team was relatively small, about 50 engineers, with three cross-functional teams of 6 engineers, shared services for data, infrastructure, and user acceptance testing (UAT).\u00a0<\/span><\/p>\n

Alice knows that code quality and maintainability are important attributes of fast digital delivery. The simple and clean code structure shortens the time to implement a new feature. She knew the ropes thanks to the <\/span>great books by Robert Martin<\/span><\/a> explaining the concept of clean code. So she asked the engineering teams whether they were addressing findings from Static Code Analysis (SCA) tools that could find code quality issues. Moreover, the engineering teams assured Alice that SCA is an explicit part of the definition of done for every feature.<\/span><\/p>\n

However, when Alice looked at the SCA report she had a hard time finding a reasonable explanation why there were so many issues. When she observed how engineers followed the definition of done, she found that some of them strictly followed what was prescribed, and some did not. This is what we call weak feedback loops when certain feedback can be skipped or its result ignored.\u00a0<\/span><\/p>\n

The adverse effect of weak feedback are:<\/span><\/p>\n