<?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>Scope on Shafiq Alibhai</title>
    <link>https://www.shafiq.in/tags/scope/</link>
    <description>Recent content in Scope on Shafiq Alibhai</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <copyright>2009-2026 All rights reserved.</copyright>
    <lastBuildDate>Sat, 17 Jul 2010 09:40:52 +0000</lastBuildDate>
    <atom:link href="https://www.shafiq.in/tags/scope/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Project Scope and Success</title>
      <link>https://www.shafiq.in/blog/project-scope-and-success/</link>
      <pubDate>Sat, 17 Jul 2010 09:40:52 +0000</pubDate>
      <guid>https://www.shafiq.in/blog/project-scope-and-success/</guid>
      <description>&lt;p&gt;In many projects, in order to provide a reasonable probability of success, it will be necessary to reduce the scope by as much as a factor of two.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve learned this the hard way. Every project starts with an ambitious list of features and an optimistic timeline. Reality intervenes quickly &amp;ndash; resources are tighter than expected, technical problems emerge, and deadlines don&amp;rsquo;t move.&lt;/p&gt;
&lt;p&gt;Cutting scope feels like failure. It&amp;rsquo;s the difference between shipping something that works and shipping nothing at all.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
