I do not know their plan is not bitter.
Recently, we invited a brother taking the time to give us a pure share some of his experience in game design, after listening to really admire and worship. Then add their own recent deep and bitter planning and design of communication, they have their own perception a little bit small. In order to respect the original sharer of knowledge, not posted PPT pure brother, and I also feel a little just to make records.
Game production itself belongs to the category of software engineering:
Determined from the design aspects of the story line, long game design, design and other value emphasis on the direction of game production, which I think we did not do a good job, although the development process in real time have maintained in the general direction, but sometimes some people proposed some specific issues within the team is like a little doubt whether the focus should be this or that direction. I said in this direction is not without meaning direction, for example in terms of is this: There are now a lot of games to survive, but its design focus is different, biased strategies to survive - this is my war, partial value to survival -overland (how Gou how to play), partial sandbox class survival - famine.
For game design although I do not have much experience did not dare to find fault, but this is also very important from an engineering point of view: moving troops and horses, design first. Lord set a good direction, the program can be targeted. This relates to how to complete the prototype design verification in limited time, and that the main direction is very critical. Planning students had to design a prototype must play based on this general direction within the framework of intelligence, design gameplay, and then handed over to the students coded verification program. This must also be very critical, and everyone is working every day of production costs.
Another point I would like to record it, is the question of copywriting. Now it has been a popular piece: first mention demand scan code before I throw you a direct TM planning case, also scan code? . No matter how kind piece, and now we have the existence of the status quo: Oral mention demand 
. Detailed planning of the case is the fulcrum of the transfer of all the work, one is designed to be the case and detailed records of copywriting, is the basis for iterative play, no one can think clearly a one-time problem or the entire design; the second is to facilitate the transfer of Fine Arts, the program's support for the work are quite large. Limited capacity of the human brain, dictating the basic needs of the next day gave forget, and had to keep asking what the demand is, to talk about the efficiency of it. The third is the key to acceptance, acceptance of the program is the first time the progress of the acceptance, and the second is to complete quality inspection. Schedule to say, directly quantified. The key to rely on the quality and acceptance of the copy: demand reduction copy Coding degree; QA acceptance basis, had to use copy quantified. Oral demand basically relying on the feeling of acceptance, easy to muddle through: program not want to write, or do not think about the plan.
Sometimes I also think overall, it is actually a science. When I communicate with colleagues in the project, we found that concerns every one of us is not the same always miss certain aspects of their own sort of time will keep communication and planning. I had planned to have a copy combing drawing flowcharts and UML habits can help me better understand the intent of the planning, implementation sort out their own ideas. As long as I look at my painting to drawing technical director, he always pointed out my problems at some point, when I negligence can to ensure that this one is no problem, he can do everything, it I admire, and this is where I need to learn. Many times the need butt has a lot of work, planning and design, and each docking convergence of their designs with existing systems, self-consistency, this time more need this ability. I have to say, before I also underestimated the overall management skills in this area, especially in large projects. This accumulation of experience, in fact, workflow and methodology summary of all the processes together a lot more than looks or very bloated, but it does ensure the accuracy of the work to a certain extent, and improve the quality of work. Like the production of mobile phones are now mentioning the word yield, quality of work go up, ahead of schedule again is a waste costs. Have to admit, integrated management skills are also a must master knowledge.