Task Prioritization-On the Board

Initiated by constant guidance of Patrick Kelly during pre-production phase of Final Project, the following model was created that was improved through production phase. This model illustrates how Internal Producers could inform every team member about their tasks. This model includes six lists.  


In progress list, and next task list are the primary level of lists that are needed to be on the board at all times. Below you can see the quick version of those three lists:

Intiated by constant guidance of Patrick Kelly during pre-production phase of Final Project, the following model was created that was improved through production phase. This model illustrates how Internal Producers could inform every team member about their tasks. This model includes six lists.  


In progress list, and next task list are the primary level of lists that are needed to be on the board at all times. Below you can see the quick version of those three lists:

Based on the icons, A’s current task is in progress and he can simply move on to his next not-done task with no problem after he is done with his current task.  S’s current task is in progress as well however, his next task is blocked. Even though this is the information any IP has access on Hansoft to and should be aware of, the blocked icon on S’s next task alerts the IP that arrangements must be made in order to remove the blockage before S finishes his current task. And lastly, M is almost done with her very high priority task but unfortunately she is blocked and cannot finalize it  (due to many possible reasons such as, the needed file being checked out by someone else, or the finalized assets are not done); at this point she can proceed to her high priority task. Once she is done with her high priority task, hopefully the IP has made the required arrangements to remove those blockages and M can finalize her very high priority task.


The secondary level of lists is GP staff feedback/bugs list, and art queue list which could be additions to the primary level lists. Below you can see the quick version of those three lists:

The feedback/bugs list assists team members to have their eyes on required improvements for the game. The art queue list is mainly created for the small adjustment of art assets which are mainly requested by programmers. However, distracting artists by constant art assets request impede their work flow. Therefore, this list requires programmers to write their needed assets on the board without disturbing artists. For both lists, you can simply erase any item that is completed. 


Not In Game list and Stats are the tertiary level of lists. Below you can see the quick version of those three lists:

Not In Game list is typically comes in handy during the last week of each sprint. This list includes every single feature that is listed on MSA yet is not in game. This list alerts team members about the amount of tasks/features that are required to be done before the sprint ends. Stats are simply the number of “not done” and “completed” tasks. Also in the stats, you can find the number of remaining days of each sprint. For each feature, there are two parts to be completed. One is the asset and the other is the integration of that asset into the game.  


This icon represents that what is left of a feature is the integration portion.    

This icon represent that the code portion of a feature is done yet the finalized art asset is yet to be made. 

And finally, this icon indicates that both asset and code for a feature has not been done yet.