<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/f7189a88e7d34c51b32d46c697f06d97&quot; frameborder=&quot;0&quot; width=&quot;1668&quot; height=&quot;1251&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1251</height><width>1668</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1251</thumbnail_height><thumbnail_width>1668</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/f7189a88e7d34c51b32d46c697f06d97-1e55606a61c1488a.gif</thumbnail_url><duration>917.552</duration><title>Writing Technical Tickets for LeanScale Engineering</title><description>In this video, I walk you through how to write effective technical tickets for our engineering team, ensuring they have everything they need to execute tasks efficiently. We cover essential requirements like task titles, descriptions, ownership, priority, and estimated time, all of which are crucial for our project management in teamwork. I emphasize the importance of consistency and clarity in our task writing to reduce questions and improve efficiency. Additionally, I encourage you to over-explain details and provide examples to give engineers the context they need. Please take these best practices into account when creating your next technical tickets.</description></oembed>