One of the most complicated aspects of game development is planning. Some would argue that small indie projects don’t need this step; they simply need to work on the project until it’s done. This is far from true.

游戲開發(fā)最復(fù)雜的方面之一就是計(jì)劃。 有人認(rèn)為小型獨(dú)立項(xiàng)目不需要此步驟。 他們只需要在項(xiàng)目上完成就可以了。 這遠(yuǎn)非事實(shí)。

初步計(jì)劃 ( Initial Planning )

The design framework laid at the project’s origin will determine the course for the entire project’s development. It's important to remember at this step that nothing is set in stone, but you should attempt to be as accurate as possible.

項(xiàng)目起源的設(shè)計(jì)框架將決定整個(gè)項(xiàng)目開發(fā)的過程。 重要的是，在此步驟中要記住，沒有什么是一成不變的，但是您應(yīng)該嘗試盡可能地準(zhǔn)確。

功能列表 ( Feature List )

First, analyze the design document and determine the game’s requirements. Then, split out each requirement into a list of features that will be needed to implement the requirement.

首先，分析設(shè)計(jì)文件并確定游戲的要求。 然后，將每個(gè)需求分為實(shí)現(xiàn)需求所需的功能列表。

分解任務(wù) ( Breaking Down the Tasks )

Take each feature and work with your leads in each area (art, animation, programming, sound, level design, etc) to break it down into tasks for each department (a group or person, depending on the size of your team).

利用每個(gè)功能并與您在每個(gè)領(lǐng)域的領(lǐng)導(dǎo)(藝術(shù)， 動(dòng)畫 ， 編程 ，聲音，關(guān)卡設(shè)計(jì)等)合作，將其分解為每個(gè)部門(一個(gè)小組或一個(gè)人，取決于團(tuán)隊(duì)的規(guī)模)的任務(wù)。

分配任務(wù) ( Assigning Tasks )

The lead of each group should then create initial time requirement estimates for each task and assign them to team members. After this is complete, the lead should work with the team to ensure that the estimates are correct and reasonable.

然后，每個(gè)小組的負(fù)責(zé)人應(yīng)為每個(gè)任務(wù)創(chuàng)建初始時(shí)間需求估算，并將其分配給團(tuán)隊(duì)成員。 完成此操作后，主管應(yīng)與團(tuán)隊(duì)合作，以確保估算是正確和合理的。

依存關(guān)系 ( Dependencies )

The project manager then must take all the task estimates and place them into a project management software package, either Microsoft Project or Excel (the two long-time industry standards) or any of the newer choices available for agile project management.

然后，項(xiàng)目經(jīng)理必須獲取所有任務(wù)估計(jì)，并將其放入Microsoft Project或Excel(兩個(gè)長(zhǎng)期行業(yè)標(biāo)準(zhǔn))或用于敏捷項(xiàng)目管理的任何較新選擇的項(xiàng)目管理軟件包中。

Once the tasks are added, the project manager must look at the tasks and match dependencies between teams to ensure that the timing of creating a feature doesn’t have impossible relationships that prevent it from being completed within necessary time frames. For example, to fully implement a racing game, you wouldn't schedule the coding of tire durability before the completion of the physics system. You would have no framework to base the tire code upon.

一旦添加了任務(wù)，項(xiàng)目經(jīng)理就必須查看任務(wù)并匹配團(tuán)隊(duì)之間的依賴關(guān)系，以確保創(chuàng)建功能的時(shí)間不存在無法避免的關(guān)系，從而無法在必要的時(shí)間范圍內(nèi)完成該功能。 例如，要完全實(shí)施賽車游戲，您無需在物理系統(tǒng)完成之前就安排輪胎耐久性的編碼。 您將沒有框架來建立輪胎代碼。

排程 ( Scheduling )

This is where things get particularly complicated, but where the need for project management in the first place becomes more apparent.

這是事情變得特別復(fù)雜的地方，但是首先對(duì)項(xiàng)目管理的需求變得更加明顯。

The project manager assigns estimated start and completion dates for each task. In traditional project planning, you end up with a cascading “waterfall” view, which shows the timeline for completion of the project and the dependencies that link the tasks.

項(xiàng)目經(jīng)理為每個(gè)任務(wù)分配估計(jì)的開始和完成日期。 在傳統(tǒng)的項(xiàng)目計(jì)劃中，您最終會(huì)得到級(jí)聯(lián)的“瀑布”視圖，該視圖顯示了項(xiàng)目完成的時(shí)間表以及鏈接任務(wù)的依存關(guān)系。

It's critical to remember to factor in slippage, employee sick time, unexpected delays on features, etc. This is a time-consuming step, but it will quickly give you an idea of exactly how much time the project will take to complete.

務(wù)必記住要考慮滑點(diǎn)，員工患病時(shí)間，功能意外延遲等因素，這一點(diǎn)很重要。這是一個(gè)耗時(shí)的步驟，但是它將很快為您提供一個(gè)項(xiàng)目需要花費(fèi)多少時(shí)間的想法。

如何處理數(shù)據(jù) ( What to Do With the Data )

By looking at this project plan, you can determine if a feature is going to be costly in time (and, therefore, money) and make decisions about whether the feature is necessary for the game to succeed. You might decide that delaying a feature to update—or even a sequel—makes more sense.

通過查看此項(xiàng)目計(jì)劃，您可以確定某個(gè)功能在時(shí)間上是否會(huì)很昂貴(并因此而產(chǎn)生金錢)，并可以決定該功能是否對(duì)成功游戲至關(guān)重要。 您可能會(huì)認(rèn)為延遲更新功能(甚至續(xù)集)更有意義。

Also, tracking how long you’ve worked on a feature is useful in determining if it's time to either try a new technique to solve the problem or cut the feature for the good of the project.

同樣，跟蹤您對(duì)某個(gè)功能進(jìn)行了長(zhǎng)時(shí)間的工作對(duì)于確定是時(shí)候嘗試一種新技術(shù)來解決問題還是為了該項(xiàng)目的利益而削減該功能很有用。

大事記 ( Milestones )

A frequent use of project planning involves the creation of milestones. Milestones indicate when a certain element of functionality, a time period of working on the project, or a percentage of the tasks has been completed.

項(xiàng)目計(jì)劃的頻繁使用涉及里程碑的創(chuàng)建。 里程碑指示何時(shí)完成某個(gè)功能要素，項(xiàng)目工作的時(shí)間段或任務(wù)的百分比。

For internal project tracking, milestones are useful for planning purposes and for giving the team specific goals to aim for. When working with a publisher, milestones frequently determine how and when the developing studio is paid.

對(duì)于內(nèi)部項(xiàng)目跟蹤，里程碑對(duì)于計(jì)劃目的和為團(tuán)隊(duì)指定特定目標(biāo)很有用。 與發(fā)行商合作時(shí)，里程碑通常會(huì)決定向開發(fā)工作室付款的方式和時(shí)間。

最后說明 ( Final Notes )

Project planning is regarded by many as a nuisance, but you'll almost always find that developers who plan projects well in advance and hit their milestones are the ones who succeed in the long run.

許多人都認(rèn)為項(xiàng)目計(jì)劃是一件令人討厭的事，但是您幾乎總是會(huì)發(fā)現(xiàn)，那些事先計(jì)劃好并達(dá)到里程碑的開發(fā)者是長(zhǎng)期成功的。

翻譯自: https://www.thoughtco.com/planning-a-game-development-project-1393892

總結(jié)

以上是生活随笔為你收集整理的如何计划游戏开发项目的全部?jī)?nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。