{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Data Science Tech Brief By HackerNoon","title":"Data Engineering Teams Need a Different Version of Agile","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/8c8d114a\"></iframe>","width":"100%","height":180,"duration":765,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/data-engineering-teams-need-a-different-version-of-agile.\nThis article explores which Agile practices actually help data engineering teams and which ceremonies often become operational overhead.\nCheck more stories related to data-science at: https://hackernoon.com/c/data-science.\n            You can also check exclusive content about #data-governance, #agile-data-engineering, #data-pipelines, #pipeline-monitoring, #backlog-management, #engineering-management, #pipeline-validation, #data-operations,  and more.\nThis story was written by: @kuladeepsandra. Learn more about this writer by checking @kuladeepsandra's about page,\n            and for more stories, please visit hackernoon.com.\nAgile is useful for data engineering teams when it creates visibility, reduces context switching, and helps teams manage uncertainty. A visible backlog, regular delivery rhythm, and meaningful retrospectives usually help. Story point velocity tracking and status-report standups often become ceremony. The goal is not to “do Agile.” The goal is to create enough structure to prevent shortcuts, surface blockers early, and deliver reliable data work.","thumbnail_url":"https://img.transistorcdn.com/8VxAgS1Ll3FJEERcAdhFdqqXJMnE7OfD2RUvrjauLt0/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMjY4LzE2ODM1/ODI1ODUtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}