In defence of cutting scope
Scope cutters can get a bad rap. We’ve all experienced situations where a team, under the pressure of a looming deadline, is forced to remove functionality from their upcoming delivery and the result is an unworkable feature that does not meet user needs. So, it’s understandable that when the scope of a feature is cut during the development cycle, this is often met with cynicism and disappointment.
It doesn’t always have to go this way, though. When trimming scope, teams should keep in mind the intended outcomes of their initiative, which should’ve been explicitly set before execution began. If the particular reduction they’re tempted to ratify significantly reduces the likelihood of achieving intended outcomes, teams are probably better off simply taking more time to finish their work.
This goes the other way, too! Teams should be encouraged to safely reduce scope, even when they’re not pressed for time, in cases where desired outcomes are not at risk. Less complexity will lead to shorter cycle times and make delivery more straight forward. And, by getting a slimmer implementation out into the wild first, teams may realise they never needed the heftier scope to begin with. Over multiple iterations, this will lead to more frequent delivery of value and greater ROI.
Privacy and terms
I will only use your email address to send you this newsletter or to reach out to you directly, and you can unsubscribe at any time. I will not share, sell, or rent your email address to any third party, though I do store it the software I use to dispatch emails.
The information provided on this blog is for informational purposes only and should not be considered investment advice. The content on this blog is not a substitute for professional financial advice. The views and opinions expressed on this blog are solely those of the author and do not necessarily reflect the views of other organizations. The author makes no representations as to the accuracy, completeness, currentness, suitability, or validity of any information on this blog and will not be liable for any errors, omissions, or delays in this information or any losses, injuries, or damages arising from its use. The author may hold positions in the companies or products discussed on this blog. Always conduct your own research and consult a financial advisor before making any investment decisions.