Believe it or not, programmers can have writers' block. Well, its not called writers' block, but we can have it. But if we don't call it that, it that what it really is? I leave that philosophical quandary for another day. The point, that I am laboriously trying to get to, is writing software is not unlike other processes most everyone (including non-programmers, cue audible audience gasp here) has experienced to some degree. Take for example a typical essay assignment. The steps would be similar to:

1. Determine subject material
2. Research
3. Compose a Draft
4. Revise and Edit
5. Repeat 3 and 4 until you have something somewhat presentable

Software composition is inherently similar, only differing in the fine details of 3-5. How so? The methodology consists of how the developers approach the revision process. Waterfall, iterative, so on and so forth.

At this point, I imagine you're wondering what my catchy 80's reference of a title has to do with this post. Wonder no more. During the development process there are obstacles even experienced programmers have to overcome. (Another word for obstacle is hurdle; there goes the light bulb). What should my next project consist of? What is its scope? (Scope creep is often referred to as the Devil). 1 How do I achieve the stated goals for this piece of software/application? The questions go on and on. They provide a framework for a possible solution to the "problem". 2



Prior planning prevents poor performance! 3







Disclaimers:

1 I do not have any empirical evidence linking scope creep to the Lord of Darkness. If you have some, feel free to share.

2 Problem is in double quotes due to its subjective nature, feel free to use this post as a mad lib in a party you're throwing tonight.

3 How cool are alliterations? (Don't know what that is? Don't you wish you were paying attention in English class?)


Originally posted HERE