<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Product-Development on Rafiul Alam</title>
    <link>https://alamrafiul.com/categories/product-development/</link>
    <description>Recent content in Product-Development on Rafiul Alam</description>
    <image>
      <title>Rafiul Alam</title>
      <url>https://alamrafiul.com/papermod-cover.png</url>
      <link>https://alamrafiul.com/papermod-cover.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 20 Feb 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://alamrafiul.com/categories/product-development/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Basecamp&#39;s Shape Up: The Alternative to Scrum You&#39;ve Been Looking For</title>
      <link>https://alamrafiul.com/blogs/basecamp-shape-up/</link>
      <pubDate>Thu, 20 Feb 2025 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/blogs/basecamp-shape-up/</guid>
      <description>&lt;p&gt;You&amp;rsquo;ve been doing Scrum for years.&lt;/p&gt;
&lt;p&gt;Two-week sprints. Daily standups. Story points. Sprint planning. Retrospectives.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;And it&amp;rsquo;s exhausting.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The sprints feel arbitrary. The planning meetings drag on. The backlog is a graveyard of ideas no one will ever build.&lt;/p&gt;
&lt;p&gt;You&amp;rsquo;re shipping, but it feels like running on a treadmill.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What if there&amp;rsquo;s a better way?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In 2019, Basecamp published &amp;ldquo;Shape Up&amp;rdquo;-their alternative to Scrum.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The core idea:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Work in &lt;strong&gt;6-week cycles&lt;/strong&gt; (not 2-week sprints)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fixed time, variable scope&lt;/strong&gt; (not fixed scope, variable time)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No backlog&lt;/strong&gt; (ideas don&amp;rsquo;t pile up forever)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Betting, not planning&lt;/strong&gt; (leadership commits to ideas worth doing)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Shaping, not speccing&lt;/strong&gt; (rough outlines, not detailed specs)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It&amp;rsquo;s radically different from Scrum.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>The Ikea Effect: Why We Overvalue Things We Build</title>
      <link>https://alamrafiul.com/blogs/ikea-effect/</link>
      <pubDate>Mon, 16 Sep 2024 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/blogs/ikea-effect/</guid>
      <description>&lt;p&gt;I once spent three weeks building a custom CSS framework.&lt;/p&gt;
&lt;p&gt;It had exactly the features I wanted. Perfect naming conventions. Elegant utility classes. Beautiful documentation.&lt;/p&gt;
&lt;p&gt;I showed it to my team. They said, &amp;ldquo;Why not just use Tailwind?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;My response? &amp;ldquo;Because mine is better.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Was it actually better? No. Objectively, Tailwind had:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;More features&lt;/li&gt;
&lt;li&gt;Better documentation&lt;/li&gt;
&lt;li&gt;Larger community&lt;/li&gt;
&lt;li&gt;More battle-testing&lt;/li&gt;
&lt;li&gt;Active maintenance&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;But I couldn&amp;rsquo;t see that. All I could see was MY framework, MY design decisions, MY time invested.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
