Do you plan your projects or work loosely?
I know there's quite a few topics similar to this already (I've been going through them for the last week or so), however none of them have provided me with the insight I am looking for, which comes down to finding the medium between too little and too much planning.
Though I'm a pretty organized person, I didn't do a lick of planning for anything, software of otherwise. However, once I started programming seriously and getting involved in bigger projects, I found that some planning, even if just a little, is needed to stay on track. This is where my conflict started.
Currently I'm at a point where I'm just focusing on making a minimum viable product and building on that. This is basically what I was doing initially, but I think where I went wrong in this approach was eventually veering off into systems that didn't exactly matter, or in other cases getting caught up on small snags. I didn't have a guide at that point though; I was just going in and doing whatever I felt like.
I'm now using a mission statement (core description) with an outline of the game's features as my guideline (based on this post). I attempted to break down my features into further sub-systems, but I felt it was too simplistic to do justice, so I decided to stop at the top level features and leave the remaining details to my mind.
So, I'd like to know how the rest of you go about getting things done. Do you have a planning process in order to get things done, or do you wing it? Do you favor the mission statement approach, or would you rather do extensive outlining? ... So on and so forth. This can deal with any software, not just games.
Looking forward to hearing from some of you.
Mar 14 2016, 3:21 pm