{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/cc329956f1e14d5595937beb33e1c8e6\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/cc329956f1e14d5595937beb33e1c8e6-bdd24a92f00b81aa.gif","duration":232.016,"title":"Introducing Rovo Race Engineer: Enhancing Software Release Management","description":"Good morning everyone, my name is Shyam Sharma, and I'm excited to present my submission for Code Digest 2025: the Rovo Race Engineer. This tool draws parallels between Formula 1 racing and software releases, emphasizing that races—and releases—are often lost due to overlooked risks rather than speed. By analyzing Jira data, Rovo identifies the top three race-critical risks for a release, providing actionable insights to help teams prioritize effectively. I've shared the architecture and key components of the project, including the index.js file and manifest.yml, which connect the app to Jira. I encourage you to review the architecture diagram and consider how Rovo can enhance our release strategies."}