PRODUCTION - WEEK ONE

Monday 4th - Sunday 10th of March

Week One: To start with week one I wanted to begin creating the proposal. I aim to plan, create, and reflect on the proposal. I aim to use the plan and gather feedback to improve and ensure a good proposal. I will take in the fact I am working in a team while creating this plan and proposal. I will create a Trello for future planning and production and a Miro for mood boards and more. These will outline our different team roles and be used to gather research/inspiration.

Tools - Miro & Trello:

To start with the tools my team created a Trello board for the coding side of production. To this Trello, Mitchell and Zak joined and began adding a few tasks. We did not add many as this week is more based on the proposal than the planning. We will add more to this next week and the following weeks.

I then created a miro board for the mood board I will create i sent the link out for the team to join.

Project Proposal - Planning:

For the project proposal, I will follow the given documents. Our teacher sent in a few documents to help us write up the proposal. To ensure the best work possible I went back to an older team chat and found the document from that year. Then I combined them to ensure I got all the needed information from these documents. Because we had this idea thought up before the start of the FEP, I had already written up a small description of the concept. This is a good starting point to continue my development of the proposal.

Here are the documents that I combined:

These documents combined will help make sure the amount of work done is to a distinction level for the proposal. It will help keep me on track with the proposal. For time management I will keep to one topic a day starting with the specialism. If done in time I may do a few in the day as some parts will take longer than others.

Here Is the final document I used as the template:

Project Proposal - Timeline Plan:

For the timeline plan, I want to take some time to think about and plan the time plan. First, I wanted to figure out how long I should spend on the proposal. For the proposal, as I said before, I would like to cover a topic a day in the initial week. This means I will make my proposal my task for the first week from the 4th to the 10th of March.

Next, I wanted to decide on the research phase. To start, I wanted to list the things I need to research so I can pack them into the weeks. For the tasks needing researching I decided on they are Shooting, Throwables, UI, Sounds, Gameplay/level Mechanics, Game Cost and a few more. I will break these up over three weeks to ensure time to do them all.

Then I will move on to production. I split this up over weeks 5 – 9. Here is will go over the mechanics I plan to produce following the systems that I researched. For each of these weeks, I broke it up into creating the basics and then working on refining them.

Lastly, I plan the evaluation weeks when I will create my final reflection. I will do this over the last two weeks and make sure I cover the entirety of the project. I will use my last FMP research and proposal as a base for this year's. This will ensure it is up to distinction standards.

Project Proposal - Final Look:

Here is the page containing the proposal taking into account all the planning I did here and following the template I created:

Proposal!

Reflection:

Proposal Reflection:

To start with the reflection on my proposal, I wanted to go through some feedback I got on my proposal. First, I showed my proposal to a few of my colleagues. This helped gather opinions and find out any issues. They had no issues with the actual work, but a few said it was not the most readable. From this, I worked on making improvements which I am happy with.

Next, for the feedback, I sent my proposal to my tutors. First, my tutor, said that the proposal was great but needed finishing which I did after that day. After I added the weekly planner, I sent it to another tutor to get some more opinions. First, he sent the document back going over many issues with the proposal like spelling and a few overdrawn segments which I fixed.

Lastly, for feedback, he suggested that I reformat the weekly task part of the proposal. Looking back, I went too far on this part, as I could have easily made it more readable and got to the point quicker. Unfortunately, due to my time plan and wanting to move on, I did not make this change, which was nearly impossible to do in time. This is an area I now know to improve on the next time I work on any project in the future.

For the entire proposal, I am greatly happy with the final product and I believe I got a ton of information into it. For the initial parts, I wrote over 3390 words and I believe this covered everything it needed to. I went over the project concept, covering the game modes and the maps. I covered my plans for the research and production as well as determining my speciality.

For the weekly plan and weekly equipment, I am happy with it other than the feedback mentioned above. I also could have maybe gone into more detail on the tools I needed to use but it's hard to tell before I have finished.

Proposal Plan Reflection:

I believe I did a great job planning my proposal and it helped me greatly in writing up the actual proposal. For this, I made sure to go the extra mile by combining current and past guidance to ensure my work was of a high level. I covered every aspect of the proposal in my plan and made sure I knew what I was going to write up. While the proposal is subject to change, this plan will help make sure it is scoped appropriately. I could have gone into more detail on my plan, but my proposal turned out extremely well, so I believe it was enough.

Proposal Plan Reflection:

I am happy with the first usage of the tools. I am glad that I got a lot of the creation out of the way so I can add to them in the later weeks. I could have done more but this week is more based on creating the proposal.

Page updated

Google Sites

Report abuse