Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C CMPT306
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Karsten Schmidt (kes845)
  • CMPT306
  • Milestones
  • Milestone 1 & 2: Planning Milestone
Expired
Milestone Oct 22, 2022–Oct 28, 2022

Milestone 1 & 2: Planning Milestone
Milestone ID: 521

It is expected that work towards Milestone 2 will be made in parallel with this deliverable. The planning milestone is all about planning your project. At this stage of the project you should have a very clear vision as to what the team is intending to develop. The assignment should contain a short document detailing what the game is, and what the intended user experience is going to be.

The assignment should contain an exhaustive asset list. An asset list is a full list of assets required to complete the project. Each item on the asset list should be allocated with an estimated number of hours to acquire or develop the asset, as well as a tentative team member assignment. While the asset list is a living document, it is important to have a very clear plan of what you are building and understand the full scope of what you need to incorporate into your game to make it happen.

As an example of atomized scope, a character with articulating limbs that is capable of moving in the scene will typically comprise of (at least): a movement script, a character model, a rig, a walk animation, a run animation, an idle animation, sound effects for walking, sound effects for running, a particle system for dust, a collision detection system.

Using the estimated number of hours in your asset list, you should create a burndown chart to show how time you have (and optionally what has already been completed).

  1. A document detailing the game (ideally with screenshots or mock-ups showing what it could look like), and the intended user experience of the game.

  2. A document listing all of the assets that your game needs (scripts, art assets, sound assets, etc.), as well as the expected hours it will take to source or develop those assets.

  3. A burn down chart showing the ideal work remaining time, and actual work remaining time.

  4. A bullet point summary of what has been worked on and who has worked on it.

  • Issues 10
  • Merge requests 0
  • Participants 4
  • Labels 3
10% complete
10%
Start date
Oct 22, 2022
Oct 22
-
Oct 28 2022
Due date
Oct 28, 2022 (Past due)
10
Issues 10 New issue
Open: 9 Closed: 1
0
Merge requests 0
Open: 0 Closed: 0 Merged: 0
0
Releases
None
Reference: kes845/CMPT306%"Milestone 1 & 2: Planning Milestone"