<?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 Justice Ogbonna on Medium]]></title>
        <description><![CDATA[Stories by Justice Ogbonna on Medium]]></description>
        <link>https://medium.com/@justiceo?source=rss-891216074693------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vJWK6SOjSgeAy9CtgsJZYA.png</url>
            <title>Stories by Justice Ogbonna on Medium</title>
            <link>https://medium.com/@justiceo?source=rss-891216074693------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:39:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@justiceo/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[Balancing the Trifecta in Software Development: Cost, Time, and Quality]]></title>
            <link>https://medium.com/@justiceo/balancing-the-trifecta-in-software-development-cost-time-and-quality-0e14cdfc9a40?source=rss-891216074693------2</link>
            <guid isPermaLink="false">https://medium.com/p/0e14cdfc9a40</guid>
            <dc:creator><![CDATA[Justice Ogbonna]]></dc:creator>
            <pubDate>Sun, 10 Dec 2023 08:55:13 GMT</pubDate>
            <atom:updated>2023-12-10T10:25:00.425Z</atom:updated>
            <content:encoded><![CDATA[<h3>My Strategy for Navigating the Trilemma of Cost, Time, and Quality</h3><p>This is a century-old problem that we encounter in everyday life beyond software development.</p><p>We want it faster: For $5 extra (<em>cost</em>) Amazon Prime can get you that product 2 days earlier; and if you don’t mind ordering a different product (<em>quality/scope</em>), you could even get same day shipping!</p><p>We are also on a budget: As a fresh grad moving to NYC, you cannot be in a rush (<em>time</em>) when looking for an apartment you can afford, unless you would settle for a 10th-floor walkup with no windows (<em>quality</em>).</p><p>And of course, we want the best: If you are trying to get VIP seats at a Drake concert, you better be ready to cough up some serious bread (<em>cost</em>) to snatch it up immediately (<em>time</em>) the show is announced.</p><p>You get the dilemma: we want to eat our cake and have it. It’s no different in software development, and you can read more about the competing forces of cost, time, and quality (and sometimes scope) here:</p><ul><li><a href="https://www.pmi.org/learning/library/triple-constraint-erroneous-useless-value-8024">The Triple Constraint</a> by Project Management Institute</li><li><a href="https://www.cio.com/article/244994/how-pmos-can-balance-time-cost-and-quality.html">How PMOs can balance time, cost and quality</a> by CIO</li></ul><h3>Escaping The Dilemma</h3><p>But how do we actually go about balancing these constraints? I would like to share a strategy that has worked for some of my projects:</p><ol><li>Determine the invariant constraint and spell out its success criteria.</li><li>Choose the constraint you can satisfy and to what extent.</li><li>Accept the third constraint that cannot be satisfied and progressively improve it.</li></ol><p><strong>The Invariant</strong></p><p>This is the project constraint that I cannot change. It could be determined by the nature of the project, e.g. for an airplane engine, the invariant would be the FAA test that the engine would need to pass in order to be used in service. It could also be determined by own economic situation, e.g. a side-project would be perennially starved of time so long as I have a full-time job.</p><p><strong>The Choice</strong></p><p>Past the invariant, I’m left with two constraints and there is usually one where I can move the needle significantly. This choice should be based on what resources you have, as opposed to what you think the project needs. Going back to the side-project example where I had accepted time as an invariant, I am now faced with a choice between cost and quality. If I can afford to pay someone to expedite the development process, I should satisfy the cost constraint. However, if I am the best at delivering such a project in high quality, I should satisfy the quality constraint.</p><p><strong>The Acceptance</strong></p><p>This last constraint — that is left after deciding on the invariant and choosing a constraint to satisfy — is the constraint is optimize for and plan around. It should be your north star! For example, if quality is the constraint you have to accept, then you should plan to launch a low quality product and over time, make your way to a high-quality product. If it was cost, you should plan to spend a lot of money (like way more than you’re comfortable with) upfront with the ultimate goal of bringing the cost down to 0 over time. If it was time, then don’t bother sticking a launch date to version 1, it’ll arrive whenever it is ready.</p><p>The interesting quality of the 3rd constraint is that it can help determine if the project is viable or not at the onset. If I truly cannot accept the last constraint, e.g. the case of a project launch being years away, then the project is unlikely to succeed.</p><p>And there you have it, my strategy for balancing cost, time and quality. I’d like to know if you found this practical and what strategies you have employed to resolving these three forces.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0e14cdfc9a40" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>