<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by dharmapurikar on Medium]]></title>
        <description><![CDATA[Stories by dharmapurikar on Medium]]></description>
        <link>https://medium.com/@dharmapurikar?source=rss-263829045798------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*nL_HLCwIuz50S3qhxnwGng.jpeg</url>
            <title>Stories by dharmapurikar on Medium</title>
            <link>https://medium.com/@dharmapurikar?source=rss-263829045798------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:23:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dharmapurikar/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Attention Crisis]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@dharmapurikar/the-attention-crisis-de1d1fd9b445?source=rss-263829045798------2"><img src="https://cdn-images-1.medium.com/max/1024/1*zgRAuHltEpSPP483ddk6Qw.jpeg" width="1024"></a></p><p class="medium-feed-snippet">Balancing Innovation with Cognitive Health</p><p class="medium-feed-link"><a href="https://medium.com/@dharmapurikar/the-attention-crisis-de1d1fd9b445?source=rss-263829045798------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@dharmapurikar/the-attention-crisis-de1d1fd9b445?source=rss-263829045798------2</link>
            <guid isPermaLink="false">https://medium.com/p/de1d1fd9b445</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[technology-trends]]></category>
            <dc:creator><![CDATA[dharmapurikar]]></dc:creator>
            <pubDate>Wed, 04 Sep 2024 05:06:59 GMT</pubDate>
            <atom:updated>2024-09-04T05:06:59.747Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Breaking the Burnout Cycle]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@dharmapurikar/breaking-the-burnout-cycle-b90a0bcea3d6?source=rss-263829045798------2"><img src="https://cdn-images-1.medium.com/max/2048/1*Ioqy1FQDCn6NU_87dig1aQ.jpeg" width="2048"></a></p><p class="medium-feed-snippet">The Silent Struggle of the Overachieving Manager</p><p class="medium-feed-link"><a href="https://medium.com/@dharmapurikar/breaking-the-burnout-cycle-b90a0bcea3d6?source=rss-263829045798------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@dharmapurikar/breaking-the-burnout-cycle-b90a0bcea3d6?source=rss-263829045798------2</link>
            <guid isPermaLink="false">https://medium.com/p/b90a0bcea3d6</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[balanced-life]]></category>
            <category><![CDATA[knowledge-work]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[dharmapurikar]]></dc:creator>
            <pubDate>Sat, 31 Aug 2024 12:37:56 GMT</pubDate>
            <atom:updated>2025-03-26T21:36:28.144Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Cycle Time: Is it a real productivity indicator?]]></title>
            <link>https://medium.com/@dharmapurikar/cycle-time-is-it-a-real-productivity-indicator-90192749a0d8?source=rss-263829045798------2</link>
            <guid isPermaLink="false">https://medium.com/p/90192749a0d8</guid>
            <category><![CDATA[developer-productivity]]></category>
            <category><![CDATA[engineering-leadership]]></category>
            <category><![CDATA[engineering-metrics]]></category>
            <dc:creator><![CDATA[dharmapurikar]]></dc:creator>
            <pubDate>Sun, 04 Aug 2024 06:57:13 GMT</pubDate>
            <atom:updated>2024-08-04T06:57:13.412Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p>I was in a meeting with an engineering leader when the topic of cycle time came up. He was keen on understanding how we could quantify the team’s speed and present an interesting case for faster time-to-market to the upper management.</p><p>“What’s the ideal cycle time?” he asked.</p><p>I explained while cycle time is a valuable metric, it’s not a standalone indicator of productivity. It’s essential to consider other factors like the complexity of the work and the overall business impact.</p><p>He countered by emphasizing the importance of demonstrating progress to leadership. “We need to show them we’re moving fast,” he said. “Cycle time seems like the perfect metric for that.”</p><p>The conversation made me realize that there’s a broader need to clarify the role of cycle time in software development and how it fits into a holistic performance measurement strategy. This blog post results from that conversation, and I hope to shed light on the topic for a wider audience.</p><p>Many people often tout cycle time as a silver bullet for measuring development efficiency, the duration from code commit to deployment. While it is a valuable metric, it’s essential to understand its limitations and use it with other indicators.</p><h3>Understanding Cycle Time</h3><p>Cycle time is a measure of how long it takes a piece of work to move through a system. In software development, it’s the time from when a story is ready for development until it’s deployed to production. Unlike outcome metrics, which measure the results of a process, cycle time is an <em>activity metric</em>, focusing on the efficiency of the process itself. While there are few variations of cycle time I have seen around, this should give you a better idea.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xRYugxuqguySZC5Mr-8hzg.png" /></figure><h3>Activity vs. Outcome Metrics</h3><p>It’s crucial to distinguish between activity and outcome metrics. While activity metrics, like cycle time, provide insights into how a team is working, they don’t correlate with the value delivered. Outcome metrics measure the impact of the work on the business.</p><h3>The Challenge of Defining “Good” Cycle Time</h3><p>Often, the goal is to reduce cycle time. However, “low” is relative. What’s considered a good cycle time for a small, experimental feature might be unacceptable for a critical business function. The ideal cycle time depends on factors like the complexity of the work, the team’s size, and the industry.</p><h3>Cycle Time: A Necessary But Insufficient Metric</h3><p>While cycle time can be a valuable indicator of process efficiency, it shouldn’t be the sole metric. It’s possible to reduce cycle time without improving the quality or business impact of the work. Therefore, it’s essential to complement cycle time with outcome metrics and other engineering metrics.</p><h3>Common Mistakes and Recommended Approaches</h3><p>One common pitfall is focusing solely on reducing cycle time, leading to teams breaking down work into smaller, less meaningful pieces. To prevent this, rigorously apply INVEST principles (Independent, Negotiable, Valuable, Estimable, Small, Testable) to user stories.</p><p>Additionally, consider including lead time in your considerations, as it measures the total time from when a work item is requested until the customer receives it. By tracking both cycle time and lead time, you can identify bottlenecks in the entire delivery pipeline.</p><h3>Educating Your Team About Cycle Time</h3><p>To foster a culture of continuous improvement, engage your team in a conversation about cycle time. Here are some questions to ask:</p><ul><li><strong>Why is cycle time important to you?</strong> (Expected responses: faster time-to-market, increased responsiveness to customer needs, improved developer morale)</li><li><strong>How does poor cycle time affect your work?</strong> (Expected responses: increased stress, context switching, lower job satisfaction)</li><li><strong>How do you believe shorter cycle times can contribute to the overall business goals?</strong> (Expected responses: increased revenue, improved customer satisfaction, competitive advantage)</li></ul><h3>Closing Thoughts</h3><p>Cycle time is a valuable tool for understanding and improving software development processes. However, it’s essential to use it with other metrics and focus on delivering business value. By combining cycle time with outcome metrics and involving the team, you can create a culture of continuous improvement and achieve better results.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90192749a0d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>