uk-netmarketing Archive (2011-2015)

Yes,  rather embarrassingly I did.    But  actually it is pretty clever and
 I love the simplicity and effectiveness of it.



It’s said that 80% of requested features are unused.     So 30 to 40% falls
well within that.  And why shouldn’t we aspire to eliminate that feature
bloat?



We achieved a 35% change in scope on a bespoke build project for Esso
recently.   That is 35% of things that we did not build that stakeholders
 thought they needed before we started (and were estimated).    We replaced
that 35% with new features that they found they did need,  but which nobody
had thought of at the start.  That was done during development (iterative
releases).   We’ve got the burn-downs to prove it.



In that case the budget actually remained the same,    but the inherent
value in delivery changed by some 70% in the same delivery timeframe.  I am
not making that up, promise!



If you know that you will know more about project and stakeholder
requirements on day 2 than day 1, why not be responsive and change the
scope, if you can?



One of those things that I look back on and think why on earth did we not
do that earlier…



Regards



anus



*From:* uk-netmarketing-bounces at mm.chinwag.com [mailto:
uk-netmarketing-bounces at mm.chinwag.com] *On Behalf Of *John Braithwaite
*Sent:* 30 November 2011 17:28
*To:* uk-netmarketing
*Subject:* Re: [uk-netmarketing] Sports - Community Website Platform



Hah! Did you just use the phrase 'paradigm shift' without a grinning a
little at the cleverness of it all.