Coding is not just math and number. It is about explaining and transferring. There is reason why it is called a programing language. Computers and machines have a certain way of thinking and understanding. You must translate your way of thinking so the computer can understand. In other words, if you are clueless then the computer is too.
The “get-er-done” or “everyone know their responsibility” mentality does not work with multi-layer and multi-dependent projects. If one action effect ten different things, than it is needed to make sure the information that sent is correct, the channel of communication is working, the interpretation of information is constant, and the execution with said information is correct. Making a video game is project. Project management is important is a requirement for almost all jobs.
There are four (five depending on who you asked) phases in project cycle.
What is the project? What is its purpose? What needs to be done? Are there any limitations? Who is available to work on the project?
These and many more questions will be asked and need to be answered. You need to convince stockholders, the team, or even yourself on the project. An idea guy fails at this point. They think a spark is enough to fuel the whole project. Those embers can die quickly if not properly nature and protected.
Everything detail is not needed to be mentioned. You need to know and design part is needed.
For example, you want to cook cheeseburgers for you and some friends. So, what is needed, cheese, beef, and bread. So, is that all? It technically meets the requirements of a cheeseburger. But you can add lettuce, tomato, or onions. What type of cheese? Fresh ground beef or pre-made frozen patties? The parties could be veggie patties. The bread can be sliced white bread or an actual burger bun. Any of these can make a cheeseburger that is why we needed a requirements and scope to limit out what is not wanted.
The Planning and Definition phrase can go hand in hand. Rescoping, redoing requirements, and more. The planning phrases set milestones and goals to reach to complete the project. The planning is the list of work that needs to be done. It is not the actual work in detail.
With the cheeseburger example, you do not need to write a detail document on how to flip and cook the burger.
The planning would like this. I want everyone to have two burgers eat (6 people in total), so at least 12 patties. I want to cook it out on my grill. Make sure the grill is clean and has enough fuel to cook. I need to know how to clean the grill. I need to know that the grill is needed and cleaning might be requirement.
Another critical point about planning is thinking about risks and problems that might happen in the future. For example, with the grill, I have a habit of taking off my grill. Then the grill needing cleaning is low risk and might not be needed. If the last time I used my grill was like five years ago, then there a risk that the grill desperately needs deep cleaning.
The execution is not just doing the work. You need to self-reflect and adjust the project.
Is this task/object meeting our standard and requirements? Are we going out of scope? Are we behind or ahead schedule?
In the middle of it, it is easy to lose yourself in the work and lose the end goal. You can lower your standard, take short cuts, and not communicate to finish the work. That is why the “get-er-done” mentality is detrimental to project.
It is not just submitting and forgetting. The closure phase makes all in the project complete. At this point, reflection on the project as a whole is done.
What can be done better? What specifically did not work? What did work? Where did we have failures?
At this point, the transfer of documentation is done.