<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: HD</title>
    <description>The latest articles on DEV Community by HD (@capu).</description>
    <link>https://dev.to/capu</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F44109%2F177b5446-ca58-4e4d-9e95-90f4ac31539a.png</url>
      <title>DEV Community: HD</title>
      <link>https://dev.to/capu</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/capu"/>
    <language>en</language>
    <item>
      <title>How do you improve ticket estimation?</title>
      <dc:creator>HD</dc:creator>
      <pubDate>Sat, 23 May 2020 01:35:28 +0000</pubDate>
      <link>https://dev.to/capu/how-do-you-improve-ticket-estimation-im3</link>
      <guid>https://dev.to/capu/how-do-you-improve-ticket-estimation-im3</guid>
      <description>&lt;p&gt;Hello, as your role being a team lead or a tech lead, some of your tasks are to estimate the features, then its tickets. How do you do it reliably and confidently? what steps you follow?&lt;/p&gt;

</description>
      <category>discuss</category>
    </item>
  </channel>
</rss>
