So I have a program I'm worked on back in 2011 and all through 2012, but the last release was in December of 2011. I've been actively working on it, but feature creep lured its ugly head and now it is filled with tons on unfinished features.

The bad part is that as I implement a feature, a new one creeps in. What can I do to avoid feature creep in the future so I can actually get a release out in over a year?

The project is based around iOS and used to have releases around each iOS version update, but the last one was back with 5.1 (2011). I would like to be able to get that steady release cycle back, but it has proven too difficult.

  • 8
    Could you be more specific in your question wrt where the features come from? Who is responsible for the feature creep? You? The Business Analysts? The President of the company? The demands of the users? It's hard to give advice on how to manage the feature creep without knowing what the source is. Also, because I like Dilbert: search.dilbert.com/comic/Feature%20Creep ;) Feb 4, 2013 at 17:08
  • 1
    Are you a sole developer on this project? Large team projects find it indispensable to have milestones to make delivery schedules manageable, but those of us who fly solo can also benefit from methodologies like feature-driven development.
    – hardmath
    Feb 4, 2013 at 17:08
  • @FrustratedWithFormsDesigner I'm the sole developer
    – Cole Tobin
    Feb 4, 2013 at 17:11
  • @ColeJohnson Ok so you are the sole developer: Is there anyone else on the team? A manager? Someone who writes requirements/specs? Anybody else? Feb 4, 2013 at 17:11
  • 4
    Shipping is a feature too... Sometimes it helps to just bear that in mind when contemplating (yet) another feature. Feb 4, 2013 at 19:10

4 Answers 4


In my experience, it's easiest if you can have a development and release cadence that doesn't get in the way of what you want to get done. Here's how I've done it:

  1. Write the features down, and give them a rating that reflects how much you want to work on it and how much you think it will benefit the user (it may be possible to engage actual users for this). Then write them in that order.
  2. Before you check in/push a feature, make sure you have a stable, deployable build (strongly consider a CI system to facilitate that).

This way, you can just push a release after each feature if you want... or wait for a rollup that offers the value that you want a release to have.


  • A feature can never be given a higher priority than the one you're working on (or it can, but it can't interrupt the one you're working on). It can come next but never now. That means that when you go from now to next, you'll have the opportunity to cut a release build if you want.
  • Very helpful! I like the somewhat strictness of it.
    – Cole Tobin
    Feb 4, 2013 at 17:22
  • I would add: Don't start a new feature before you finish a new one. Otherwise you end up with a code base of loose ends that can't do anything.
    – Tyanna
    Feb 5, 2013 at 0:37
  • @Tyanna: That's what I meant by "a feature can never be given a higher priority than the one you're working on... it can't interrupt the one you're working on..." Feb 5, 2013 at 16:45

The answer is trite and frequently impossible: refuse to add additional features.

In more depth, the answer really comes down to what makes a new feature fall into the feature creep bin? If we assume that features that creep are those that are added to a project despite the fact that their functionality is only tangential to the intended use of the project and that the creeping features are useful, not superfluous, the answer is to move them to separate, but related tools. Use the Unix philosophy of building orthogonal tools and gluing them together.

From a project management standpoint, the answer is comparable. Decide how much time you are willing to devote to the next release and set a deadline. Estimate the features and cut enough to make the deadline. If there are stakeholders involved other than yourself, make them choose what matters most to them.

A good overview on Scheduling can be found on Joel on Software:


  • 9
    Since he's completely solo on the project, he may need to outsource the job of slapping the feature requester.
    – Philip
    Feb 4, 2013 at 17:24

One of the most important lessons in development is knowing when its time to stop.

What typically happens is a developer adds a features. That in turn inspires more ideas. So more features get added. That is, as you said, one of the ways a project becomes vaporware. The developer never sees the project as 'finished', so it never gets released.

The habit you want to get into is to stop thinking in terms of a release/version as a 'finished' project. Rather, look at development as a long-term process. Think of releases as milestones along the path to what you one day hope the program will be. Thus, a release/version is just a snapshot of where you are in the longer term process... a snapshot thats been well rounded out and tested.

What you can do, on the practical side, is sit down and spec out your next release. It doesn't have to be terribly thorough. Write down the 3-5 new major pieces of functionality you believe are essential for the next release. (actual number of features may vary depending on the type of app, not counting bug fixes or minor gui changes) Work on those. If you come up with other ideas, thats fine... just make notes and implement them in the following release. When you get those 3-5 items done, your release is ready for beta.

When I start a new application, I typically think about the final 'vision' for the app. That, to me, is what I want in version 3 of the app. With that benchmark, I have an idea of what will make solid version 1 - just the basics.


Each release does not have to be the finished 'vision' of the project. Just a milestone towards that vision.


Use a version control system in which it is cheap to create a branch for some idea, and keep it out of your release path. For instance in git, you can "creep up" some idea, and then git stash it away. Later you can review these stashes and cherry pick them in whatever order seems interesting.

For larger features, make a real branch (so you can do multiple commits). Case in point: when I wanted to add generational support to the garbage collector, I made a branch. Stashes capture the distracting little stuff very well. Big features can start as stashes, then turn into branches, and then finally merge when they are ready.

With stashes and branches, you can take stock of your ideas, prioritize them and establish a scope for the releases of your solo project, just like a managed team project.

Look, when you get an idea, it has to go somewhere, and the best somewhere is code: the repo. Creeping features is better than forgetting good ideas. But of course, if you creep all your features into the same mainline, it will keep delaying release, unless you cut untidy releases full of half-done stuff that users have to be warned not to use.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.