GAD 444 Interactive Narrative Journal Collections
***Day 1 (31/01/22)***
Every time I plan a project, I always list some tasks and use them as a guide to develop them. There are four steps to manage those tasks.
One of them is to Plan Ahead, understanding and using them to make it easy to arrange from simple to challenging parts. Another one is to Update them. It’s always important to know the progress and what kind of task that needs to be done on time. Breaking down and doing one at a time is also a good step before things get harder to finish. And last of all, being critical about those tasks is needed to make sure they are necessary for the project. Some of them can be alternatives that don’t need to include.
After listing the tasks, it’s good to place them in Planning Charts and adjust them throughout the development. It’s good for improving time management skills.
Example Gantt Planning Project Chart in Excel image from Microsoft
When organising the task, it’s better to question yourself about the risk of using those techniques. The risk matrix helps you consider the questions that will come up with the task. Problems that will be harder to face in the future is what needs to remind that not all tasks are easy. Moreover, a question that will likely fall into, how likely it would happen and another one that the worse thing could happen if it fails should consider while taking the task. It’s better to understand the risk and plan the ways to prevent them from happening.
Once you consider the risk, the next step is to define the list of tasks that is part of the project. Make sure to include the Risk Matrix on the tasks as well. Break them into shorter steps and arrange them in the group that part of their features.
As you’ve seen in the multiple scales of the priority, some tasks need to consider their necessary features and put them as one at a time. When it comes to the games and a player, it’s better to think about the expectations you find in a game and consider them as an expected feature. Another feature that you, the developer/designer want to remove is something that no one would notice an extra task and, it is considered to be a Desirable feature. They might not be necessary but, those features will improve the work. For instance, thinking about a feature you need to nominate for a prize is one of the unique features that will lead to Mid Top Priority. As long as there’s a priority, you can motivate to work on that required task.