You should also keep checking and improving the pipeline, he says, making sure nobody in the team will need to wait for other people if they want to see their latest asset or tweak in the game. ?When we want to adjust something and we still have to wait for the programmer to come through, it's actually unbearable, this waiting time,? he says. Whether you have to wait at all ?is a simple standard to determine whether a pipeline is good,? Wang adds.
?Automating the version checking is also very important,? he says. This also helps with the spirit of teamwork, if you can check the progress of the game on your mobile phone at any time. ?A lot of people have wasted 50% of their time waiting,? he cautions.
If you have bosses you need to convince of your product, the tendency is to strive for a lightweight design validation process -- but to play fair, you should convince your higher ups or investors with something playable at least every 2 weeks, instead of ?wasting time writing reports,? says Wang.
?Are they assured of what you will achieve through simple reports?? he asks. ?It's unlikely that they will feel assured. So you should show them the game. Show them progress every 2 weeks, that's the shortest tolerable time. It's much more effective when you're having validation meetings.?
Internally, though, you should also have a reviewable version available every day, and insist on making at least the top two major features truly data-driven. But Wang's biggest piece of advise is you should never believe a feature will be polished, or a graphical element will be good, or the frame rate will be improved later, or during the last last month of development. Do it now.
harrisburg great pacific garbage patch ben affleck and jennifer garner google privacy changes windows 8 preview leap year moratorium
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.