> ... most of the stuff I did back at university ... I would place that kind of programming in a different class. Small, "one-shot" problems probably don't ne

> ... most of the stuff I did back at university ... I would place that kind of programming in a different class. Small, "one-shot" problems probably don't need a lot of planning. That's the experimental / exploratory class of problems where you're not interested in the correctness of the process but results. AKA risk reduction. For the other classes where there is "The Process" of validation, testing and approvals, a little planning up front saves some churn on the back end. I have the same concern about iterative development. Seems like a lot of teams jump right into a coding sprint/iteration/cycle w/o a plan.