{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"What Burndown Charts Miss About Real Software Delivery","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/11d99ade\"></iframe>","width":"100%","height":180,"duration":590,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/what-burndown-charts-miss-about-real-software-delivery.\nBurndown charts may satisfy stakeholders, but they often fail to capture the nonlinear reality of software development.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #software-development, #burndown-charts, #burnup-charts, #engineering-management, #software-delivery, #developer-productivity, #software-metrics, #agile-metrics,  and more.\nThis story was written by: @mdenda. Learn more about this writer by checking @mdenda's about page,\n            and for more stories, please visit hackernoon.com.\nThis article argues that common software-delivery metrics such as burndown charts, velocity tracking, and percentage-complete estimates misrepresent how software is actually built. Because development is exploratory, nonlinear, and shaped by discovery, the author contends that demos, narratives, and shipped outcomes provide a more accurate picture of progress than process metrics designed primarily for reporting and stakeholder communication\n        \n        ","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}