How to determine the right amount of up front design?
- by Gian
Software developers occasionally are called upon to write fairly complex bits of software under tight deadlines. Often, it seems like the quickest thing to do is to simply start coding, and solve the problems as they arise. However, this approach can come back to bite you—often costing time or money in the long run!
How do we determine the right amount of up front design work? If your work environment actively discourages you from thinking about things up front, how do you handle that?
How can we manage risk if we eschew up-front thinking (by choice or under duress) and figure out the problems as they arise?
Does the amount of up front design depend entirely on the size or complexity of the task, or is it based on something else?
