Question

I’ve never written functional specs, I prefer to jump into the code and design things as I go. So far its worked fine, but for a recent personal project I’m writing out some specs which describe all the features of the product, and how it should ‘work’ without going into details of how it will be implemented, and I’m finding it very valuable.

What are your thoughts, do you write specs or do you just start coding and plan as you go, and which practice is better?

Answer 1

If you’re driving from your home to the nearest grocery store, you probably don’t need a map. But…

If you’re driving to a place you’ve never been before in another state, you probably do.

If you’re driving around at random for the fun of driving, you probably don’t need a map. But…

If you’re trying to get somewhere in the most effective fashion (minimize distance, minimize time, make three specific stops along the way, etc.) you probably do.

If you’re driving by yourself and can take as long as you like, stopping any time you see something interesting or to reconsider your destination or route, you may not need a map. But…

If you’re driving as part of a convoy, and all need to make food and overnight lodging stops together, and need to arrive together, you probably do.

If you think I’m not talking about programming, you probably don’t need a functional spec, story cards, narrative, CRCs, etc. But…

If you think I am, you might want to consider at least one of the above.

😉