As this is a solo project, I can organize things any way that suits me - I do not require slack, FaceTime and other communication software. This may change during later stages of development If I do have assistance from a computer science student or music student. If another member is to join the project, I will accommodate them appropriately and updating the timetable to fit them in.

Tools I will use:

1. Google Docs

Google Docs is a very simple text editing platform. However, it can be used for multiple purposes. I intend to use Google Docs for the following:

• Testing
  • During the whole semester there will be various iterations of testing and formal write-ups will be written with accompanying evaluations.
• Design
  • Digital records of any art and design work, will be uploaded to the Google Drive.
• Version Control
  • Any updates that are made to the project, both within the paperwork/ design and the Unity project, should be written up in order to maintain clear logs of any changes.
• Extensive Planning documentation
  • This will include a variety of text documents which go through requirements, scope analysis and what is possible to be achieved within the time constraints I have.
  • Additionally, It will include any design or thought processes that occur that assist development.
    • The benefits of using Google Docs versus word, means that documentation will be stored on the cloud - a more safe and consistent storage location that can be accessed easily from other networks and pcs. Additionally, it is easy to keep everything in one place when it is through the game’s Google account.
• Timetable documentation
  • After we are given our schedules for semester 2, I will be able to create a formal document in which I can organize my time for the semester’s duration.

Organisation of Google Drive

• Project N.U.W

  • Admin

    • Will include any scope analysis, pipelines and processes, spending and other project admin

  • Requirements

    • Sound
    • 3D assets + World Art
    • Unity

  • Design

    • Level Design
    • Art Design

  • Development

    • Development Logs

  • Testing

    • Testing Logs

  • Timetable

    • Time Table documents

    A typical week would like this for me:

    “Time to work” has been created to show periods of time when I am not at my part-time job or within lectures that are timetabled. I will however have to cook at least 1 meal during this section of time, which will result in most likely a 1-hour break.

    • Monday (9:00 - 18:00 - Time to work)
      • Planning + Listening requirements and documenting
    • Tuesday (16:00 - 18:00 - Time to work)
      • Attending Lecture + Planning touch ups
    • Wednesday (12:00 - 20:00 - Time to work)
      • Finishing Planning and beginning with Designing solutions
    • Thursday (16:00 - 20:00 - Time to work)
      • Attending Lecture + Continuing with Designs
    • Friday (14:00 - 20:00 - Time to work)
      • Attending Lecture + Finishing Designs and begin creating
    • Saturday (9:00 - 18:00 - Time to work)
      • Create + put into unity project and document
    • Sunday (12:00 - 20:00 - Time to work)
      • Create + put into unity project and document

    9+2+8+4+6+9+8= 46 Hours total (theoretical Time to work)

    As I will need to cook and complete other life activities, It is likely that I will have closer to 38 hours a week to work on the project. Personally, I feel this is not enough and will mean I have to most likely adjust my scope.

    I have created a rough calendar which I can follow through semester 2. Within the first couple of days, I intend to create a more detailed plan with specific requirements that I expect to achieve. The reason for not making the detailed plan now is because during the two-week break I will try to learn and best prepare myself for next semester. Depending on how well I prepare myself, I can adjust my scope. Preparation will include looking for resources, learning more about coding in C# and further research. I have also gathered a lot of videos on level design that I intend to watch in order to then implement within my game.

    Within my calendar weekly breakdown, I have 11 weeks of intense work and week 12 is a “safety” net which I can make use of if I fall behind at any point.

    A look at the calendar for semester 2 with a rough plan:

    Plan Draft For Semester