skip to content rich footer

stevenclark.com.au

subscibe to the StevenClark.com.au rss feed

Scope Creep: Just an Extra Widget, Please?

How many times have you sat in a meeting and wondered why they are still adding extra features even though the project is running late and over budget? A change here and a tweak there. A little restructuring of the information architecture. Some design decisions that require serious backend attention by the team.

Similarly, we’ve probably all had the client who asks for that little extra widget, a page they hadn’t considered or something that came to mind on the trip over which might take only an hour (but possibly most of a day). And you concede because you’re a nice person, and you do it several times. The budget goes south and your children starve in the streets.

My suggestion is that once you make an agreement on a date, a deliverable and a payment you enforce it rigidly. Make that clear to the client or stakeholder from the very beginning. Make it clear you’ll take new features on board, but that new features can only be worked on after the agreed contract work ends and payment is received.  If the bar keeps moving you’ll never bring their work in on time and under budget.

You may have noticed the moment you show an interface to the client everyone has an opinion and a list of things that would be ‘great to have’ and ‘must be removed’. My point - get signoff. Get paid. Focus on getting things done.

Articles are licenced under a Creative Commons Licence but copyright of images is retained by © Steven Clark 2007 - 2008

Leave a Reply

NOTE: fields marked with an asterisk * are required.





skip to top of page

Currently Reading

Information and Data Modelling (Second Edition) by David Benyon (Cover)With an eye toward implementing another web interface database solution from the ground up I'm casually revisiting David Benyon's Information and Data Modelling (Second Edition). Its critical to have a solid understanding of conceptual data modelling and knowing how to identify various things like fan traps and three way traps very early in the process. To that end, while its fine to have a basic understanding of third normal form and general ideas about relations (that which relational databases rely on), its also a great idea to spend time exploring the theory and case studies that lead to a higher understanding.

Often people I deal with just snuff their nose and say they can design a database - but often its a very naive approach. Having read this book about four years ago its time for a quick refresher over my holiday period. No, I doubt few will envy me.