Concept Art Overview
There had been some hiccups in the prioritization and visibility of concept art and therefore I was tasked to create a visual overview to provide more clarity to the art director and allow for easy manipulation of priority.
Since that there seemed to be no desire to do this in Jira, we tried a more manual approach in Confluence Whiteboards, using its connection to Jira tickets to display them on the board.
This provided more clarity to the art director and gave a better impression on what the concept artists were working on and should be working on - retaining an overview on the entire workload without the distractions and unappealing view given in Jira Boards.
Asset Workflow
The introduction of PCG (Procedural Content Generation) required a new implementation within Jira and we had to think about its workflows.
In general, the asset workflow had been repurposed for this new project; many asset types were not applicable or had barely been used in previous project, as well as some extra steps that were hardly related to this project - thus we decided to purge the list of any irrelevancies and rework it to be more simplistic.
In correspondence with my lead, I assisted in the proposal and implementation of the new asset workflow.
About the game:
This poster was made by Salomé Busurashvili
The Process:
Feature Team Management
For this project, I've been responsible for the feature team; a team consisting of different disciplines that together were to produce the gameplay features, AI, and researched the possibilities of a Full Body Avatar - a set that was very closely connected, both internally as well as externally.
Depending on which features were at a certain stage, it should inform the level team enough to create their levels and set up their planning accordingly. Therefore, it was important to prioritize these features and bring them to a good enough quality to unblock the other team, without going into too much detail, and only then - when everything had reached this minimum - could we make the improvements as desired. It was all about finding the balance between creating a feature in a minimum amount of time and getting to a quality that was both stable and informed measurements.
Milestone Delivery Support
I was given the opportunity to shadow another producer to understand the processes behind a milestone delivery, and pick up some of its elements myself with his support.
Herein I was tasked to communicate the lock requirements, which required me to verify the gatekeepers, lock dates and the nature of these locks - also ensuring the Lock was enabled within our software.
Besides some general setup (scheduling delivery beats for management and QA review and setting proper communication channels), I was in charge of storage, build notes and follow-ups within my own team related to the milestone efforts.
I attended and hosted the weekly triage and was also sitting in on the management reviews to keep track of incoming issues and ensuring they were able to play the build.
Responsibilities
-
Feature Team Management
-
Milestone Delivery Management and Communications
-
Create Roadmap
-
Weekly Reports
-
Epic Kick-offs & Reviews
-
Make adjustments to the asset workflow in Jira
-
Update the asset types
-
Add a specific issuetype and workflow for concept art
-
Add a specific issuetype for PCG Assets