<?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 Charles Rodriguez on Medium]]></title>
        <description><![CDATA[Stories by Charles Rodriguez on Medium]]></description>
        <link>https://medium.com/@crodriguezx?source=rss-22629934460f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WFsqUBlo3ZlcL0R9CpdLAQ.jpeg</url>
            <title>Stories by Charles Rodriguez on Medium</title>
            <link>https://medium.com/@crodriguezx?source=rss-22629934460f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:05:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@crodriguezx/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 Fallacy of Efficiency]]></title>
            <link>https://medium.com/203-solutions/the-fallacy-of-efficiency-8f05fba476f1?source=rss-22629934460f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f05fba476f1</guid>
            <category><![CDATA[story-points]]></category>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[efficiency]]></category>
            <dc:creator><![CDATA[Charles Rodriguez]]></dc:creator>
            <pubDate>Mon, 28 Aug 2017 12:31:01 GMT</pubDate>
            <atom:updated>2017-08-28T12:31:01.219Z</atom:updated>
            <content:encoded><![CDATA[<p>The Fallacy of Efficiency</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/0*Ztfb3h0iuZ_a-h_h." /></figure><p>My colleague, Richard Khor, and I took on ‘efficiency’ during one of our <a href="https://www.youtube.com/watch?v=eqZ0S8jWs9s&amp;t=16s">weekly talks</a> in June. Since the video was posted, I’ve had some more time to reflect on the topic. Specifically, I have seen many threads about story points and the various metrics extrapolated from them. Perhaps I’m taking too much of a binary approach, but using story points for purposes other than their intent- forecasting and prioritization- is an exercise in futility. You’re looking in the wrong place!</p><p>If you’re unfamiliar with this routine, someone will usually ask one or a combination of the following questions:</p><ul><li>How can I get more points from the team(s)?</li><li>How do I know I’m getting the maximum amount of points from the team?</li><li>This team used to deliver <em>x</em> points, but now they’re only delivering <em>y</em>, how do we get them back on track?</li></ul><p><em>* In the spirit of the article, I’d love to hear what some of you have encountered</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*pQFiOMQG-f2TTYjc." /></figure><p>Beware of these questions, especially when they come packaged with a desire for efficiency. Early into my career as a scrum master/coach, these inquiries would make my blood boil. Over time I’ve realized that it’s not the fault of the person asking. They don’t know they’re looking in the wrong place!</p><p><strong>Where to Look</strong></p><p>I’ll admit that I’m not a fan of story points. They imply an absolute measure to the untrained eye. In business school, managers are taught to look at metrics, graphs, and trends (oh my!). It’s not their fault that they immediately start looking at story points to derive performance. Coaches and Scrum Masters have the daunting task of shifting that focus. When faced with the, ‘How do I know we’re most efficient?’ follow it up by asking, ‘How do you define efficiency?’ Sometimes the best tool a coach can use is the Socratic Method.</p><p>If the response is focusing on more points, restrain yourself from the age old retort: ‘Placing an emphasis on points will likely result in teams bloating their estimates or embracing the overcommit, under deliver mantra”. Saying it does feel great, but it doesn’t solve the problem. If it’s a misunderstanding of what story points are, take some time to walk them through the concepts. Mike Cohn’s post, ‘<a href="https://www.mountaingoatsoftware.com/blog/what-are-story-points">What Are Story Points?</a>’, is a good starting point.</p><p>You want them to focus on the value the team is delivering, not the quantity of points. The emphasis in the prior statement is on ‘deliver’. Start very broadly by looking at all the items of work a team delivers. Are they bugs, features, technical debt, etc? The quantity and composition of what the team is producing will tell you quite a bit. Here’s an example of just a few observations:</p><ul><li>High feature ratio- the team is expanding the product; are these features deliverable to the client/customer and what value have they provided?</li><li>High bug ratio- the team is in ‘firefighting’ mode; is code quality weak or is the code base too fragile?</li><li>High tech debt ratio- the team is trying to improve the platform; are these improvements adding value to the client?</li></ul><p>There are only a few several insights to gain from looking at the work delivered by a team. From this analysis, more questions arise. This is OK! We’re now engaging in a more valuable conversation about what the team is producing rather than measuring story points. This is the first step in steering the conversation toward delivery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*dTVU83w-nA7a8zYx." /></figure><p>If your shop has established a portfolio or roadmap, this is the level you want to measure. These are the features that are delivered to your client/customer. If not, check out Richard Khor’s video on the <a href="https://www.youtube.com/watch?v=zdNSYoMnUCo">Agile Donut</a>. Here he discusses how to establish a rolling roadmap and PSI plan. These artifacts provide visibility and transparency on what the teams are delivering. This is where the true value is; if they’re concerned with how much is delivered, measure here!</p><p><strong>Wrap Up</strong></p><p>It’s time to step off my soapbox. This is a heated topic that agile/lean communities face at some point. I haven’t quite figured out the best way to approach it, but I wanted to share my experiences with the community in an effort to draw out suggestions. Feel free to share share your experiences in the comments section!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f05fba476f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/203-solutions/the-fallacy-of-efficiency-8f05fba476f1">The Fallacy of Efficiency</a> was originally published in <a href="https://medium.com/203-solutions">203 Solutions</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>